-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop logind integration #117
Comments
Curious what this would mean... Would everything enabled by HAVE_SYSTEMD no longer exist? |
Yes, HAVE_SYSTEMD and HAVE_ELOGIND. |
Thank you. Just considering what features will not be sticking around. I am assuming I am less certain how to handle locking the screen after, say, laptop lid close, if I am right that Thanks for all the work you all are doing on this project. Such a useful tool! |
before-sleep only has value when you are trying to have both sway/swayidle and logind handle idle actions like suspending. Just remove the actions from /etc/systemd/logind.conf and use swayidle and sway bindsym/bindswitch to trigger suspend. For idle actions, there is no point in having sway tell swayidle, which the tells logind, which then runs actions when swayidle is meant to run them directly. For button actions, it makes no sense to have logind waste resources by eavesdropping in all input devices when sway bindsyms can do the trick. For direct loginctl suspend calls, just start swaylock first. |
Would this allow swayidle to work even without dbus? |
swayidle can already work without dbus if you compile it with logind support disabled. |
I see. Indeed it works even now (from void repo), even though it prints
2022-03-16 16:27:47 - [Line 471] Failed to open D-Bus connection: No such file or directory
2022-03-16 16:27:47 - [Line 520] Failed to add D-Bus signal match : property changed: Invalid argument
2022-03-16 16:27:47 - [Line 278] Failed to parse get BlockInhibited property: Invalid argument
|
What are the alternatives guys? I have void Linux and I can't use swayidle functionalities like |
|
Not a Void linux alternative because still systemd-based, but I think systemd-lock-handler could replace |
hmm, when swayidle tells logind that the system is idle, IIUC logind will lock all the sessions (for the lock action) of all users. it's a bit more complicated than that, but i'm not sure swayidle alone can reproduce that feature... inherently, locking, hibernating etc is a system action, so logind is the passage from user demands to system actions and i'm not sure how to properly work around that. |
Swayidle will likely end up dropping logind support, and they themselves describe it as unstable. For this reason, move to the suggested alternative: systemd-lock-handler, and just have swayidle run the command to trigger the logind session lock event, picked up by systemd-lock-handler. See <swaywm/swayidle#117> for reference.
So there will be no support for |
It's hard to maintain, it's the source of many bugs, and it duplicates functionality with Wayland-native interfaces which provide the same functionality.
The text was updated successfully, but these errors were encountered: