home.social

#elogind — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #elogind, aggregated by home.social.

fetched live
  1. Figured out how to get around KDE, elogind and music player daemon (mpd) just dying when you connect to it.

    1. Log into console as user
    2. Run mpd &
    3. Log out

    mpd stays up and running and works in KDE. You just have to start mpd outside of the "KDE session".

    #KDE #mpd #elogind

  2. Figured out how to get around KDE, elogind and music player daemon (mpd) just dying when you connect to it.

    1. Log into console as user
    2. Run mpd &
    3. Log out

    mpd stays up and running and works in KDE. You just have to start mpd outside of the "KDE session".

    #KDE #mpd #elogind

  3. So much for '#SystemD is not a monolith' guilt tripping. It's modular in theory alone. is the next critical software to introduce a hard dependency on systemd, after . Those of us using , , etc are looking at a situation similar to .

    What's common among them? A corporate ecosystem that only they can maintain. Meanwhile, those who question this are treated with contempt!

    osnews.com/story/145071/flatpa

  4. So much for '#SystemD is not a monolith' guilt tripping. It's modular in theory alone. #Flatpak is the next critical software to introduce a hard dependency on systemd, after #Gnome. Those of us using #Runit, #OpenRC, #GNUShepherd etc are looking at a situation similar to #elogind.

    What's common among them? A corporate #OpenSource ecosystem that only they can maintain. Meanwhile, those who question this are treated with contempt!

    osnews.com/story/145071/flatpa

    #gentoo #void #guix #alpine #linux

  5. Solving the mystery of niri and swayidle—elogind

    Based on the debug output from swayidle, I started researching what the heck org.freedesktop.login1.Manager was doing. When using sway, this was not used on my non-systemd system, and swayidle works as expected.

    With sway, the way it is working, from a casual user’s perspective:

    1. swayidle intercepts for an “idle state” message.
    2. swayidle runs the script that I have configured—swaylock-plugin locks and the background is rotated continually.

    Using niri on my non-systemd system, there does seem to be this extra piece in the mix—logind. Or in my case elogind.

    1. swayidle intercepts a PrepareForSleep signal...

    nokoto.org/user/3/posts/964

  6. Solving the mystery of niri and swayidle—elogind

    Based on the debug output from swayidle, I started researching what the heck org.freedesktop.login1.Manager was doing. When using sway, this was not used on my non-systemd system, and swayidle works as expected.

    With sway, the way it is working, from a casual user’s perspective:

    1. swayidle intercepts for an “idle state” message.
    2. swayidle runs the script that I have configured—swaylock-plugin locks and the background is rotated continually.

    Using niri on my non-systemd system, there does seem to be this extra piece in the mix—logind. Or in my case elogind.

    1. swayidle intercepts a PrepareForSleep signal...

    nokoto.org/user/3/posts/964

  7. @developing_agent @mcc @ariadne

    That's because systemd-logind, which is massively coupled to everything and not very cohesive, and is also never packaged as an individual thing, is and was one of the root causes of the problem.

    Even just separately packaging it would have avoided much of the original Debian Hoo-Hah in 2013, as I pointed out back then.

    jdebp.info/FGA/debian-systemd-

    @ska #elogind #DebianHooHah

  8. @developing_agent @mcc @ariadne

    That's because systemd-logind, which is massively coupled to everything and not very cohesive, and is also never packaged as an individual thing, is and was one of the root causes of the problem.

    Even just separately packaging it would have avoided much of the original Debian Hoo-Hah in 2013, as I pointed out back then.

    jdebp.info/FGA/debian-systemd-

    @ska #elogind #DebianHooHah

  9. This slow rolling / refactor is hitting little things left and right, first the redo of the ps data handler, which morphed into the program version refactor, which then morphed into the just completed Display Manager refactor, which expanded to add the previously incorrectly ID'ed login/seat managers, like , , . Now inxi shows dm if detected dm, but if not, shows login: [manager] item instead. This covers situations like sway, labwc etc, started by seatd.

    \1

  10. antiX 22 ist da!

    Das Federgewicht unter den Distributionen wechselt mit Version 22 zu seatd und consolekit und liefert somit ein systemd- und elogind-freies Betriebssystem aus.

    #AntiX #systemd #Elogind #Debian

    gnulinux.ch/antix-22-ist-da

  11. antiX 22 ist da!

    Das Federgewicht unter den Distributionen wechselt mit Version 22 zu seatd und consolekit und liefert somit ein systemd- und elogind-freies Betriebssystem aus.

    #AntiX #systemd #Elogind #Debian

    gnulinux.ch/antix-22-ist-da

  12. Here is a simple guide for setting up a lock screen for WM users in Gentoo or other distros without Systemd.

    youtu.be/ymMK1QALl78

  13. Switched from #elogind to #seatd on my #Artix installation.

    Looking good so far!

  14. @sir: Indeed. Feels like a valid statement for quite some situations, even situations, not everyone will agree with, like this one:

    For me, a software which causes so much #pain that other started writing alternatives, is #systemd.

    Without systemd, nobody would have had to write or #fork #eudev, #elogind, docker-systemctl-replacement, #opentmpfiles (by #OpenRC), etc.

    Nobody would have ever created #Devuan and we wouldn't need an externally hosted (!) #debian-init-diversity mailing list, etc.