Created attachment 547078 [details, diff] skypeforlinux-logind.patch The last skype version needs logind to start. If not installed, skype segfault. Here is my proposal.
I confirm the bug. I installed sys-auth/elogind (actually, without starting the service) and, only after that, I could start skype. Otherwise I had segfault.
I have installed elogind, skype starts but after a few seconds it crashes anyway :-(
I can confirm that installing (don't even need to manually/auto start) elogind is enough to allow skypeforlinux to start for me. Before: Sep 18 11:50:26 kut kernel: skypeforlinux[17562]: segfault at 18 ip 00007fb6435cde0e sp 00007ffd9894b1a0 error 4 in libdbus-1.so.3.14.14[7fb6435b4000+43000] After: Sep 18 13:27:02 kut dbus[2829]: [system] Activating service name='org.freedesktop.login1' (using servicehelper) Sep 18 13:27:02 kut kernel: [13948]: New seat seat0. Sep 18 13:27:02 kut dbus[2829]: [system] Successfully activated service 'org.freedesktop.login1' Versions: net-im/skypeforlinux-8.30.0.50 sys-auth/elogind-238.1
I can confirm this issue. However it is mandatory to have +policykit USE flag enabled for elogind, to prevent the crash. sys-auth/elogind[policykit]
(In reply to Balint SZENTE from comment #4) > I can confirm this issue. However it is mandatory to have +policykit USE > flag enabled for elogind, to prevent the crash. > > sys-auth/elogind[policykit] Confirmed as working. Thanks!
I cannot even build elogind: meson_options.txt:85:0: ERROR: Option name debug is reserved.
Which version of dev-util/meson are you using? I am using the stable 0.46.1 version and i am not having this problem. Cf. : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909455
Just so your aware of the conflict, net-misc/teamviewer fails when sys-auth/elogind is installed and not actually using systemd. (I use OpenRC) So I have to uninstall sys-auth/elogind to use Teamviewer, and install sys-auth/elogind to use Skype. D'oh!
(In reply to George L. Emigh from comment #8) > Just so your aware of the conflict, net-misc/teamviewer fails when > sys-auth/elogind is installed and not actually using systemd. (I use OpenRC) > > So I have to uninstall sys-auth/elogind to use Teamviewer, and install > sys-auth/elogind to use Skype. > > D'oh! This is why systemd really sucks and is against every good practice of the * nix world :( (OpenRC forever)
Downgrading to version 8.29.0.41 is a a gimmick if you don't want syslogd's garbage on your installation ;)
Except that, at least in the past, Microsoft has stopped accepting connections from Skype clients older than a certain version... So enjoy your 8.29.0.41 while it lasts... :\ And indeed, this is one of the many deleterious effects of systemd in Linux. I keep my fingers crossed that people will continue trying to come up with ways to remove or at least isolate systemd poison for those of us who do not wish to use it, but clearly it is not a given, especially with closed-source programs like this.
Just want to confirm that installing elogind did the trick for me too, no need to actually start it. Well, skype starts it on startup.
Last version working without elogind is 8.29.0.50.
(In reply to Fabio Rossi from comment #2) > I have installed elogind, skype starts but after a few seconds it crashes > anyway :-( solved my problem by adding CGROUPS support to the kernel which is required by elogind. Latest version is now 8.31.0.92 and shows the same behaviour
Please get this done before November 1, 2018 as support for the older version will be discontinued and I really need this for work.
Yeah.. this patch looks fine to me.. for those interested in more info on this see https://www.linuxquestions.org/questions/slackware-14/so-no-more-working-skype-for-slackware-15-the-older-versions-crash-because-the-new-glibc-the-newer-ones-needs-systemd-logind-4175638990/page7.html
*** Bug 668752 has been marked as a duplicate of this bug. ***
(In reply to George L. Emigh from comment #8) > Just so your aware of the conflict, net-misc/teamviewer fails when > sys-auth/elogind is installed and not actually using systemd. (I use OpenRC) > > So I have to uninstall sys-auth/elogind to use Teamviewer, and install > sys-auth/elogind to use Skype. > > D'oh! Take a look at bug 668752. Would using skype-dbus-mock instead of elogind fix your problem with teamviewer?
(In reply to Matthew Schultz from comment #18) > > Take a look at bug 668752. Would using skype-dbus-mock instead of elogind > fix your problem with teamviewer? Since the bug is marked WONTFIX, I'm watching to see what happens with bug https://bugs.gentoo.org/669538 and will try it when it hits portage.
(In reply to Matthew Schultz from comment #18) > Take a look at bug 668752. Would using skype-dbus-mock instead of elogind > fix your problem with teamviewer? I went ahead and downloaded and installed it and unmerged elogind. Yes, skype-dbus-mock allows both Teamviewer and Skype to both startup and run at the same time. It should be in portage and a dependency for skype on OpenRC.
I also agree, skypeforlinux works again using net-im/skype-dbus-mock from bug 669538
I found this because my laptop was double suspending on button press, and it was suspending on lid (which i normally disable). Turned out it was elogind (even though i never started it). Please try and solve this upstream and do not pull in systemd magic that messes with peoples systems. I personally do not even remember when i last used skype, and since this RDEP breaks my whole system i decided to uninstall for now ....
Please update that ebuild to have a "systemd" and "elogind" USE-flag and require one of the two. This way people will have to knowingly pull in the RDEP and will be warned about the side-effects.
Now that skype is working for me again without elogind thanks to skype-dbus-mock, how do I get rid of the elogind dependency in skypeforlinux? Btw, elogind messed with my system as well, preventing shutdown/reboot from KDE because of missing /run/initctl. We should not depend on this crappy stuff at all.
Same for me, as reported in #681212. I just wanted to cross-reference bug reports so people experiencing unnecessary data loss when suspending their systems can find the discussion threads easily.
