If your using Skype I don't see why you wouldn't also be willing to use Chrome.

Its just the faff of having to load yet another browser onto a laptop that will only be used with one application! I only installed skype for linux because I was traveling and might have needed to contact family. That was OK, but it broke (slightly) the latest Plasma update. I already had Eric's Chromium installed, and thought that his script above would be a quick work-around. It does load and login, but can't make or receive calls.

The ideal solution would be a skype for linux installation that actually works without breaking Plasma, but not at the cost of installing systemd.....!

I can live without it, but I thought I'd warn others before they waste their time on it.

--
Pete

2 members found this post helpful.

In fact, from what I read and what I heard, there's no need for systemd, but for elogind, which is that systemd-logind chopped off from systemd, just like is eudev.

But elogind is a (better) replacement for ConsoleKit2, and they both does not go along. So, unless the maintainers decides to switch to elogind and to remove ConsoleKit2, nothing can be done as simple users.

Thanks for the explanation!

--
Pete

I am not having the described problem.

I use skypeforlinux (I also use Eric's Skype Web), it's my own build, not the SBo build. I also use the "Mocked systemd dbus interface for skype 8.30+" from https://github.com/maelnor/skype-dbus-mock

My build is similar but fits my build environment and use the rpm for the source, not the deb. There are a few other differences but nothing that affects installation. Primarily version checking, downloading, use stable or unstable version

I am currently using version 8.53.0.85 stable on Slackware64-current with latest ktown.

2 members found this post helpful.