The October Plasma5 prefers {systemd-,e}logind against ConsoleKit2, so SBo's skypeforlinux will broke the shutdown/reboot feature of Plasma5
by LuckyCyborg from LinuxQuestions.org on (#4SV6T)
Maybe looks strange, but it is just like the title says.
The reason is that the package skypeforlinux from SBo packs a fake systemd-logind server, to make the skypeforlinux binary happy.
And I spent an entire night to debug the strange issue from this October's Plasma5, where instead of the expected shutdown or reboot from main menu, you get a blank screen with only the mouse active. From what screen, using CTRL+ALT+BACKSPACE (kill X server) you will go well back to SDDM screen, from where you can reboot/shutdown just fine. Probably another Plasma5 features are affected, but I am not aware about them.
So, I think there's a moral of this story:
while could be noble reasons behind the refusal of a particular init system, the stubbornness of (still) looking for alternate solutions to {systemd-,e}logind started to introduce subtle but nasty conflicts between softwares shipped by the major players of Slackware community.
As bottom line, I think that is ironic that I needed to make an Android-x86 installation on a flashdrive, just to ensure that I have a functional Skype, which is the communication software of choice on my extended family, people who no one uses Linux, anyway.
The reason is that the package skypeforlinux from SBo packs a fake systemd-logind server, to make the skypeforlinux binary happy.
And I spent an entire night to debug the strange issue from this October's Plasma5, where instead of the expected shutdown or reboot from main menu, you get a blank screen with only the mouse active. From what screen, using CTRL+ALT+BACKSPACE (kill X server) you will go well back to SDDM screen, from where you can reboot/shutdown just fine. Probably another Plasma5 features are affected, but I am not aware about them.
So, I think there's a moral of this story:
while could be noble reasons behind the refusal of a particular init system, the stubbornness of (still) looking for alternate solutions to {systemd-,e}logind started to introduce subtle but nasty conflicts between softwares shipped by the major players of Slackware community.
As bottom line, I think that is ironic that I needed to make an Android-x86 installation on a flashdrive, just to ensure that I have a functional Skype, which is the communication software of choice on my extended family, people who no one uses Linux, anyway.