We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
254
Debian
6.5.0-2-amd64
None
systemd-logind
Adding a sleep inhibitor as user like
systemd-inhibit --what=sleep --mode=block bash
and then issuing suspend:
suspend
busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager SuspendWithFlags t 1
in the same session should prevent suspend as there is an inhibitor set.
The above does not prevent suspend for me.
(systemctl suspend does inhibit suspend but that's because it checks for inhibitors first.)
systemctl suspend
See above under "expected behaviour".
No response
The text was updated successfully, but these errors were encountered:
suspend-manager: Inhibit via gnome-session rather than systemd
b7dc856
The systemd inhibitor would ensure we don't suspend when e.g. another session is active. What we're interested about here is the user's session though so use gnome-session to prevent suspend instead. We use a sync DBus call here which should be fine and not block and we can't do much without gnome-session running anyway. For the systemd bits see systemd/systemd#29818 Signed-off-by: Guido Günther <agx@sigxcpu.org> Closes: https://gitlab.gnome.org/World/Phosh/phosh/-/issues/1001 Part-of: <https://gitlab.gnome.org/World/Phosh/phosh/-/merge_requests/1339>
No branches or pull requests
systemd version the issue has been seen with
254
Used distribution
Debian
Linux kernel version used
6.5.0-2-amd64
CPU architectures issue was seen on
None
Component
systemd-logind
Expected behaviour you didn't see
Adding a sleep inhibitor as user like
and then issuing
suspend
:in the same session should prevent suspend as there is an inhibitor set.
Unexpected behaviour you saw
The above does not prevent suspend for me.
(
systemctl suspend
does inhibit suspend but that's because it checks for inhibitors first.)Steps to reproduce the problem
See above under "expected behaviour".
Additional program output to the terminal or log subsystem illustrating the issue
No response
The text was updated successfully, but these errors were encountered: