So, no more working Skype for Slackware 15? The older versions crash because the new GLIBC, the newer ones needs systemd-logind

User Name

Remember Me?

Password

SlackwareThis Forum is for the discussion of Slackware Linux.

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

Yes, Skype and elogind is working great for me as well. I am still concerned that simply having it installed may cause problems. So far I have not seem any obvious problems. Odd that you mention the power buttons. Yesterday when testing I only saw "New seat seat0.", today this is what I get.

I don't use Skype on my laptop, no elogind installed. Closing the lid works fine, in my case Plasma5 is configured on Power Management to execute "Hibernate". I've also used "Suspend" it works as well.

Yes, Skype and elogind is working great for me as well. I am still concerned that simply having it installed may cause problems. So far I have not seem any obvious problems. Odd that you mention the power buttons. Yesterday when testing I only saw "New seat seat0.", today this is what I get.

I don't use Skype on my laptop, no elogind installed. Closing the lid works fine, in my case Plasma5 is configured on Power Management to execute "Hibernate". I've also used "Suspend" it works as well.

I do not think is something odd. After all, the ConsoleKit and (e)logind are supposed to do a similar job. Well, probably there the original is (e)logind and the emulation of it is the ConsoleKit.

That's why I supposed from beginning that activating both on a system, will result in a "war of attrition" over resources and system, with possible unexpected results.

Certainly, this elogind is not our old PulseAudio pal, to start it when we need it.

BTW, this what I get starting the elogind from "rc.local", then system-wide

Oh, I said that we must use (e)logind for our future Wayland adventures with Plasma5?

IF you ever want to have on Slackware a future Plasma5 properly working (also) on Wayland, even if Plasma5 will not be adopted, you should jump on "elogind adoption" bandwagon, even if you do not use Skype or other proprietary software possibly requiring it.

There's no middle road, because ConsoleKit2 and elogind cannot coexists.

Oh, I said that we must use (e)logind for our future Wayland adventures with Plasma5?

IF you ever want to have on Slackware a future Plasma5 properly working (also) on Wayland, even if Plasma5 will not be adopted, you should jump on "elogind adoption" bandwagon, even if you do not use Skype or other proprietary software possibly requiring it.

There's no middle road, because ConsoleKit2 and elogind cannot coexists.

I hate to disappoint. We will not need Elogind... Consolekit2 works too.

Which is correct insofar as /etc/login.defs says that user assignable UID's and GID's begin at 1000. Actually it lies, because as slackware-current is configured user group IDs begin at 100. But that doesn't matter either.

The name "login1" of this D-Bus service is the choice of systemd-logind. It has nothing to do with the API definitions. The ConsoleKit2 project has chosen the alternative name "consolekit" in order not to cause a clash on the bus when both (e)logind and ConsoleKit2 are installed.

A variation of my first patch (dealing with redefinition of statx struct) has been accepted upstream and will be part of next release (elogind-239 I guess). The updated patch (applies OK to 238.1) is attached.

I opened a separate issue about the hard coding of /run/dbus/system_bus_socket (currently fixed by second patch, or by setting a symlink at /run/dbus -> /var/run/dbus).

That's all folks. I contacted everyone of my contacts and it appears that my granddaughter and I remain the only ones that care to Skype each other these days. I am old and like the computer. She is young and prefers a smart phone (the world is changing). She just told me to not worry and just message her with text. The app that came with my phone will work nicely for that so as soon as I send this reply I am taking Skype off my system. Microsoft can play games without me anymore

Last edited by Gordie; 09-26-2018 at 12:12 AM.
Reason: Added that I have communicated with my contacts

Which is correct insofar as /etc/login.defs says that user assignable UID's and GID's begin at 1000. Actually it lies, because as slackware-current is configured user group IDs begin at 100. But that doesn't matter either.

ALL phones come with an app for sending / receiving text messages. No downloads needed. My granddaughter says that Skype and personal computers are old school and everyone uses their phone these days. Times are a changing