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.

Yet another system(d)evil thread........

Complain to Microsoft. They're the ones who made skype logind/pulseaudio dependent when it doesn't need to be.

2 members found this post helpful.

Why someone should complain to Microsoft? They does not ship fake systemd-logind servers with skypeforlinux, from what I know. The SBo guys did that.

Also, I believe that considering that's their (Microsoft) software, it's their rights to decide which software support it needs, even it is about dotNET.

However, that Plasma5's new preference toward logind made my to raise an eyebrow. This is a brand new thing for the Plasma 5.17.x or whatever component of now KDE software...

What's next? Deprecating the ConsoleKit2 support, then removing it on the next Plasma6?

At least, with the official shipped KDE4, there are no conflicts with skypeforlinux or its fake servers, as built from SBo.

Just get rid of that Skype package and use Skype Web.

Here's how you can create (as root) a nice menu entry that uses Chromium browser to create an independent browser session (not using your regular profile) without borders to make it look like a real app:

11 members found this post helpful.

To me the decision of the KDE dvelopers makes sense. If you find both login1 and ConsoleKit2 services on your DBus, and you know that ConsoleKit2 does not provide a complete emulation of the login1 service, then you pick that login1 service as your default. If a login1 service (provided by systemd or by elogind for instance) is not discovered then KDE Plasma5 happily uses ConsoleKit2.

Instead of whining that KDE Plasma5 is broken after you install a fake systemd-login1 service which basically does nothing, you should create an enhancement request in the KDE bug tracker to make the order of ConsoleKit2 versus logind1 preference configurable in some systemsettings dialog window.

8 members found this post helpful.

Oh you mean the same company whose CEO referred to Linux as "that virus!"... or the company that forced an upgrade version when they bought out Skype to a version that would no longer run on Linux but missed the workaround of merely changing only the version ID number of the older software that did still run on Linux? That company?

1 members found this post helpful.

I do not said that Microsoft is a pure white and crystal clear company...

However, I will say it again: I am truly certain that Microsoft did NOT put fake systemd-logind servers on their skyperforlinux tarball.

BUT, that SBo guy did it in his skypeforlinux package.

https://www.slackbuilds.org/reposito...skypeforlinux/

Mr. Mario Preksavec put also somewhere a warning that his package installs on our systems a thing which may take over some important DBUS things like the login control?

I do not seen something like this.

Wow. This is some impressive reaching.

Fact is, Microsoft requires the login1 implementation for skype when it is obviously not needed (since this can be bypassed with the fake login1 service). This broke skype on Slackware and any other distros not using systemd. A workaround was found to fix that problem with no known side-effects at the time (and it worked well for over a year). Now you're installing software that isn't officially supported by the skype package (a -current system running ktown using SlackBuilds from SBo for 14.2) and we have the first known bug report of this issue... and you are saying that Mario Preksavec should've had a warning for the package for a problem we didn't even know existed until a little over 12 hours ago? To reiterate, this "solution" has existed for about a year and around 12 hours ago is our first known problem with it when running a version of Plasma5 released within the last few weeks.

Get over yourself! Maybe you could try and find a solution rather than just pointing fingers. One potential solution was already suggested by Eric and make the suggestion to KDE developers to allow choosing login1 or consolekit2.

There is no point in attacking people for trying to fix things on Slackware. When a problem is found, it is better to try and find a solution than to tell everyone how they're wrong.

8 members found this post helpful.

Gentoo does the same exact thing by pulling in system(d)evil "parts" and not the devil itself;
https://wiki.gentoo.org/wiki/Gentoo_Without_systemd

I think that there should be a rule that anytime system(d)evil is mentioned in the Slackware forum, the thread should be deleted and the OP banned for a day. If you want system(d)evil there are a thousand Debian/RedHat/etc distros out there to satisfy your demonic lust. Why must we be constantly bombarded with this follow the herd nonsense?

3 members found this post helpful.

Thats not the only problem , i see after install plasma5 under slackware-14.2 , some breakage of "stock" slackware packages...

upgrading poppler, makes ghostscripts-plugins break , gpgme ..same ..

i think , problem is under pkgname , maybe need poppler-qt5 ... cause only "poppler", upgrade the stock lib , and break stock libs and apps.

touch stock libs are never good idea.

As work around, i suggest , rename your package with poppler-qt5 ...and disable qt4 bind in config to ensure no overwrite or remove original poppler qt4 of slack 14.2

I see in my system a lot of stock 14.2 packages break , i format partition and install again 14.2 under kde4 ...safe choice.

He has a note stating, "The phonon and poppler packages were extended so that they now support Qt5 as well as Qt4." You may want to verify everything was installed properly and if it's still broken, bring it up on his blog (that's where he prefers bug reports for his packages).

He got a brand new release on 14.2, which is several years old. It is likely impossible to do this without touching stock libs.

I encounter plasma, disordered ... all plasma apps , have separate folders under /usr/share/plasma-app-name/* i like how kde4 is configured ALL under /usr/share/kde/*

Thanks to the OP who has solved the problem of why my laptop wouldn't shutdown properly after the update, when my desktops would! I forgot I'd installed skypeforlinux before traveling recently....!

Also thanks to Eric for suggesting an alternative way of using skype from linux!



--
Pete

I spoke too soon! Skype for web doesn't work in Chromium - only Chrome!

--
Pete