Finally Worked Skype with new elogind without systemd and pam here.

Just need to install elogind before start skypeforlinux.

Source:
elogind.SlackBuild - https://pastebin.com/WMV5rTQr
doinst.sh - https://pastebin.com/iNn8vREx
elogind-238.1-docs.patch - https://pastebin.com/Vdd9n76u
rc.elogind - https://pastebin.com/zXqXn4Dt

It seems Mario found another solutions

But that will/may break stuff when apps suddenly find login1, like my first implementation of nologind.


In the long-run I think wrapping everything is the way to go.

I really appreciate the work you've done and what you've been doing. Thanks a lot for the attention, but I ended up solving slackbuild and rc.elogind and now it does not lock anymore my skype and it works normally the power manager.

1 members found this post helpful.

That's great.

I'm currently looking into Cinnamon (source) and checking what they need.

1 members found this post helpful.

Just in case some else is using it besides me, I also updated my latest-skype.sh script to use maelnor's nice skype-dbus-mock trick.

2 members found this post helpful.

I have been using this solution for while. It worked, easy to implement and avoid elogind. I think I ran in to a program that broke due to this solution. Steam Client. I could be wrong though.

I am using Steam Client with Steam Beta Update enabled. I have Steam Play enabled with Proton 3.16-4 Beta selected. I noticed that a Nov 3 update continuously tried to update it self because it failed. This was not one after the other, but after a time, Steam tried to install the update again. I started Stean via Konsole, I have since discovered /tmp/dumps/<user>_stdout.txt which logs the stdout. In that log I noticed the following:
This may have nothing to do with the Steam Client failing, but it gave me the idea to remove the skypeforlinux package I built with the 'skype-dbus-mock' trick. I did this while steam was still running. On removal of skypeforlinux Steam was aborted. To be on the safe side I rebooted (login at runlevel 3). Steam is set to run on startup of Plamsa 5, Steam noted it had aborted, fixed it self then tried to install the Nov 3 update after a restart of Steam. It was successfully installed.

Now those code lines above are still in the <user>_stdout.txt file, but the update installed. To test this I restored a nightly backup of Steam and tested again, it installed. I also reinstalled skypeforlinux and the update failed to install. I have since removed skypeforlinux and Steam is running fine, in fact on a Nov 5 update now.

I am fairly convinced that the 'skype-dbus-mock' trick installed with skypeforlinux was the problem with Steam, though not sure why. The two things that lead me to believe this are the fact the Steam aborted when I removed skypeforlinux and updates to Steam are installing again.

As a side note, related to elogind, I had been using that before switching to the 'skype-dbus-mock' trick. elogind seems to be a bit invasive. I noted the following during boot:
I didn't pay much attention to it while elogind was installed. After removing elogind though it became annoying. To get rid of those to messages have to rebuild initrd.gz. Once that was done, those messages were gone.

At this point I am putting skypeforlinux on hold for my system. I have Skype on my smarter that me phone, so I can use that for now. may get a bit adventurous and to try olear's fix, but a bit hesitant because I don't really know for sure what broke Steam.

1 members found this post helpful.

Hmm… I don't use Steam myself. I would be interested to hear if other Steam users have hit the same issue. I have been using Skype in my browser since this whole fiasco started and it has been fine but once the slackbuild started using skype-dbus-mock, I figured I might as well update my script to use it. If skype-dbus-mock and other work arounds just cause further issues, maybe I'll just drop maintenance of my script altogether and stick with using the browser.

I am also interested in if other Steam users are seeing this issue when using the skype-dbus-mock trick with Skype. One of the reasons I posted. It could be something specific to that Nov 3 update to Steam.

I liked having Skype on my desktop. I am wary of both elogind and the skype-dbus-mock trick and the effect it might have on the system. I forgot about the web version of Skype. That is definitely an option.

I have been thinking of giving olear's nologind a try but I am not sure what Steam is looking for. I could try it and see what happens.

I did find were the elogind related failed to execute comes from. There are four rules installed by elogind in /lib/udev/rules.d/. There are added to the source tree when mkinitrd is run. The specific rules files that causes the error noted in my earlier post is /boot/initrd-tree/lib/udev/rules.d/70-uaccess.rules.

I am thinking, a dangerous thing <grin>.
I am wondering if elogind can be installed, configured to provide only the functions Skype is looking for.

As a refresher: this post of mine in the thread contains a .desktop file you can create if you have Chrome or Chromium installed and which will give you a menu item starting Skype Web in the browser such a way that it looks almost exactly like the application. No logind required.

2 members found this post helpful.

Thanks for this, ruario.

I'm still on Skype 8.29. Is there a reason to upgrade beyond this at present? It still seems to work fine. I know at some point MS will force adoption of a later version, but until then I'll stick with this one.

I'm also concerned about the issues with Steam. I know not everyone is experiencing issues, so will hold fire with upgrading Skype for now.

Re Skype web, I've found it not to provide as good call quality as the downloadable client. Also it's had problems connecting in the past, but Skype is generally quite rubbish these days, Facebook calling is much better.

I'm a Firefox user, but I installed your Chromium package sometime ago. I decided to try it out, nice! Not quite like the Skype Client though but close enough. I even wrote a small SlackBuild to create a packages for it for the desktop file. So I don't forget this modification.

Probably not. It works (for now). Using a web browser, is also great though. AlienBob's tip is a nice one. Alternatively, Vivaldi users can also put Skype in a web panel (that is what I was doing).

I really only updated my script because the mock solution appeared to work and I figured some people might want the 'normal' package for reasons that don't immediately spring to mind (it is always nice to have options).

But if the workarounds just cause breakage, I might just abandon maintenance of my script, rather than encourage people to use something that potentially screws them over—by actively maintaining it, I am effectively encouraging them.

3 members found this post helpful.

Flatpak is still working very well (in a sandbox). Currently running 8.33 without an issue:

https://flathub.org/apps/details/com.skype.Client

You'd need flatpak though

Kr
Mel

3 members found this post helpful.

It's working here, Skype and Steam are running ok. I'm running Xfce in -current and just updated Steam and played few minutes of HL2E2.
I don't use camera or microphone in Skype, can't tell if those works.

1 members found this post helpful.