Ah, my /var/run directory is a symlink to /run, so I didn't have that problem. It is a requirement of systemd that /var/run should be a symlink to /run, so this is presumably something that elogind has implicitly assumed also. Most other distributions seem to make that symlink also.

The compilation error seems to have arrived with glibc-2.28, which is why I didn't get that problem before. I can reproduce it now.

1 members found this post helpful.

Attached is a second patch which has elogind use /var/run/dbus/system_bus_socket (as used by Slackware) instead of /run/dbus/system_bus_socket. If used, the additional symlink in /run to /var/run/dbus mentioned previously is not required.

Don't bother with the patch if /var/run is already a symlink to /run (as per systemd requirements).

chris

Attached Files

rundir.diff.txt (976 Bytes, 13 views)

5 members found this post helpful.

You might want to submit this upstream (to elogind): it is one thing for systemd to require /var/run to be a symlink to /run, it is another to assume in the logind/elogind code that the same file is in two different places at the same time. It is a bug which is masked by systemd's requirements, and appears to have first arisen with logind/elogind-237. So presumably elogind-236 is not affected.

3 members found this post helpful.

I managed to put together the patches published by @chris.willing for elogind-238.1 (many thanks!) and shameless borrowing the w41l's build for elogind from there https://github.com/w41l/kde-elogind/elogind adapted by me to the current meson build.

The resulted SlackBuild is attached to this post, and generates a elogind-238.1 package, which apparently works correctly and is able to bring up the support needed by skypeforlinux_8.31.76.88, which is able to work on GLIBC 2.28, as shown in the attached screenshot.

BUT, like I said in a previous post, installing Elogind along with ConsoleKit2 you obtain two distinct systems which try to handle the user login sessions, and very possibly to step on each other shoes.

Not fully tested, but looks like the Eric's Plasma5 5.13.5 still manage to execute the power and logout actions even with both of those systems installed.

However, I strongly believe that this story clearly demonstrate that the ConsoleKit2 should be gone and it replaced by at least Elogind.

Why I say that ConsoleKit should be gone?

Because it is clear for me that it is obsolete. Software evolved, and needs features which aren't offered by ConsoleKit. And I guess there are many other applications which suffer by that lack, not only Skype.

However, in this weekend, which I spent experimenting around Skype and DBUS services for users login sessions I observed that the other few distributions proud to be "systemd-free" in fact they use at least three barbarian chopped chunks of systemd: eudev, elogind and systemd-timedated1 (which probably replaces ntp and/or ntpdate).

Yep, the "systemd-free" thing looks like have the sense for them as not using it as init system.

That make to ask myself: IF we must use huge chunks of systemd to satisfy the requirements of the today software, why we should stay ourselves as minions of Gentoo and at their caprices, when we can just use our own machete at build time to chop off the init system part from that systemd, which apparently is what its hatters hate?

That's why I said "at least Elogind"

Anyways, I believe that in a way or other we should kiss goodbye to ConsoleKit2, if we want Slackware to be compatible with the today Linux software.

PS. To have a imagine about what is adapting Plasma5 to elogind you can take a look there: https://github.com/w41l/kde-elogind

However, it is very possible that this implementation to be not actual, because it is about Plasma5 5.10.4, and the today Plasma5 5.13.5 may have a much better support for elogind.

Attached Thumbnails

 

Attached Files

elogind.tar.xz.txt (13.7 KB, 17 views)

I built elogind version 238.1 and ran in the the "missing.h:1387:8: error: redefinition of ‘struct statx_timestamp’" problem as well. Thanks for the patch @chris.willing

I figured out the /run/ vice /var/run/ on my own and created a patch.

I patched the /usr/share/skypeforlinix/skypeforlinux to run elogind before starting skype and then kill it after quitting skype.

Skypeforlinux version 8.31.76.88 is working quite well as far as I can tell. I don't plan on leaving Skype running unless I am using it or expecting a call because of conflict concerns between ConsoleKit2 and Elogind. Perhaps there is a way to configure it to only handle what Skype needs.

This is the build part of my SlackBuild:
The -Dpam, -Dselinux are not really needed, they are disabled if not found. The meson configure is not needed, but it comes in handy for figuring out options.

During 'meson setup' I do get one warning. Since it's a warning not to worried about it. Though I am puzzled a bit.
The patch for skypeforlinux is attached.

Attached Thumbnails

 

Attached Files

skypeforlinux.diff.txt (497 Bytes, 19 views)

3 members found this post helpful.

Or, I don't know, just talk on the phone.

3 members found this post helpful.

But then "they" can't record and archive your video conversation for future purposes.....

As someone is interested by "your" video conversation...

To imagine that someone will bother to record the "nothing" discussed by a "nothing" with another "nothing" is utterly paranoia.

1 members found this post helpful.

Well, Skype done a great job, specially 20 years ago, when was usual to pay 1 EUR per minute to talk on mobile from Italy or France to Romania, for example. You know, mobile roaming.

Maybe is nothing for you, who lives in Las Vegas, USA - BUT for the Romanian people working in another countries from Europe, was a very expensive price this mobile roaming.

So, they discovered a way to talk much cheaper: over Internet, using Skype. From computers. And 20 years ago was only Skype for this job.

That's why millions of Romanians working around Europe used Skype to talk with their relatives from home. And that's why Skype is traditionally known and used by millions of Romanians.

BUT, I seen it used by many others, not only by Romanians.

2 members found this post helpful.

I just started using Discord, it will most likely replace Skype for me on Slackware!!

1 members found this post helpful.

I said already in a previous post that "replacing" Skype (or any communication software) depends also on the choices used by the people you talk with.

1 members found this post helpful.

15 years ago (actually less, as it took a few years to become popular)

Sure the old im boring, have nothing to hide etc... Not going to hijack the thread, i'm not DV after all, but those words have been spoken by many people before realizing that government(s)/companies do not care if you are boring or have nothing to hide....I would think you would know that being from Eastern Europe. [/sigh]

1 members found this post helpful.

@abga

Anyway, today even a granpa from a little village hidden between mountains knows about Skype.

The Romanians learned long time ago a simple rule: never talk important things over phone.

And probably initially that rule was about ancient analog land lines since 1944, after Churchill chosen Greece and Romania was given as friendly "gift" to Stalin.

Yeah, I talk right on about Winston Churchill, who preferred to keep Greece in the British and American spheres of influence.

https://en.wikipedia.org/wiki/Percentages_agreement

Attached Thumbnails

 

5 members found this post helpful.