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

chrisretusn · 09-25-2018, 10:16 AM

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.

Code:

New seat seat0.
Watching system buttons on /dev/input/event2 (Power Button)
Watching system buttons on /dev/input/event1 (Power Button)
Watching system buttons on /dev/input/event0 (AT Translated Set 2 keyboard)

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.

Darth Vader · 09-25-2018, 10:31 AM

Quote:

Originally Posted by chrisretusn

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.

Code:

New seat seat0.
Watching system buttons on /dev/input/event2 (Power Button)
Watching system buttons on /dev/input/event1 (Power Button)
Watching system buttons on /dev/input/event0 (AT Translated Set 2 keyboard)

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

Code:

Starting up elogind: /usr/libexec/elogind/elogind &
New seat seat0.
Watching system buttons on /dev/input/event5 (Power Button)
Watching system buttons on /dev/input/event4 (Power Button)
Watching system buttons on /dev/input/event1 (USB USB Keyboard)
Watching system buttons on /dev/input/event2 (USB USB Keyboard Consumer Control)
Watching system buttons on /dev/input/event3 (USB USB Keyboard System Control)

Darth Vader · 09-25-2018, 10:43 AM

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.

Alien Bob · 09-25-2018, 12:05 PM

Quote:

Originally Posted by Darth Vader

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.

chrisVV · 09-25-2018, 01:55 PM

Quote:

Originally Posted by chrisretusn

Just before the warning messages.

Code:

Message: maximum system UID is 999
Message: maximum system GID is 999

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.

Alien Bob · 09-25-2018, 01:59 PM

Quote:

Originally Posted by Darth Vader

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.

Both implement the same login1 D-Bus API. There's no "emulation". Stick to the facts.

chrisVV · 09-25-2018, 02:08 PM

Quote:

Originally Posted by Alien Bob

Both implement the same login1 D-Bus API. There's no "emulation". Stick to the facts.

There is no emulation and they don't both implement the same login1 D-Bus API.

Darth Vader · 09-25-2018, 02:43 PM

Quote:

Originally Posted by Alien Bob

Both implement the same login1 D-Bus API. There's no "emulation". Stick to the facts.

I said "probably" with a reason...

---------------------------------------------------------------

Anyways, I will stick to facts.

According with "login1 D-Bus API", like this page claims: https://www.freedesktop.org/wiki/Sof...ystemd/logind/

Guess which one - Elogind or ConsoleKit2? responds me to this command:

Code:

gdbus introspect --system --dest org.freedesktop.login1 --object-path /org/freedesktop/login1

To note that I do that in a system where both are up and running.

Alien Bob · 09-25-2018, 03:02 PM

Quote:

Originally Posted by Darth Vader

I said "probably" with a reason...

---------------------------------------------------------------

Anyways, I will stick to facts.

According with "login1 D-Bus API", like this page claims: https://www.freedesktop.org/wiki/Sof...ystemd/logind/

Guess which one - Elogind or ConsoleKit2? responds me to this command:

Code:

gdbus introspect --system --dest org.freedesktop.login1 --object-path /org/freedesktop/login1

To note that I do that in a system where both are up and running.

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.

They both implement this API: https://www.freedesktop.org/wiki/Sof...ystemd/logind/
ConsoleKit does not have a 100% API coverage, that is not required either, but they implement enough to make the KDE Plasma / Wayland work: https://consolekit2.github.io/Consol...dbus-reference

chris.willing · 09-25-2018, 06:20 PM

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).

chris

Gordie · 09-25-2018, 09:43 PM

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

solarfields · 09-26-2018, 12:40 AM

Gordie,

there's Viber and it seems to works just fine.

FlinchX · 09-26-2018, 02:56 AM

Quote:

Originally Posted by abga

use Signal instead

As soon as it will stop implying / requiring that I must have a phone. As far as I know, it's impossible to just download a desktop version of Signal and start using it.

chrisretusn · 09-26-2018, 06:40 AM

Quote:

Originally Posted by chrisVV

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.

Thanks, I took a look at /etc/login.def

Code:

#
# Min/max values for automatic uid selection in useradd
#
UID_MIN			 1000
UID_MAX			60000
# System accounts
SYS_UID_MIN		  101
SYS_UID_MAX		  999

#
# Min/max values for automatic gid selection in groupadd
#
GID_MIN			 1000
GID_MAX			60000
# System accounts
SYS_GID_MIN		  101
SYS_GID_MAX		  999

Gordie · 09-26-2018, 07:10 AM

Quote:

Originally Posted by solarfields

Gordie,

there's Viber and it seems to works just fine.

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