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
Exiting sway puts computer to sleep if laptop lid is closed #7269
Comments
This is probably systemd's doing. |
Not sure if this helps or not, but exiting other wayland desktops like Plasma don't put the computer to sleep, they just go back to the tty. |
I think @emersion is correct: this is controlled in I also see this behaviour but consider it a feature because why would I not want my laptop to suspend if its only input and display are inaccessible due to laptop being closed? |
Maybe related: https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/3497 |
Thanks, setting it to ignore fixed my issue. It is still a little annoying though that KDE didn't need this to keep from going to sleep.
I guess I forgot to mention this in the initial post, but I keep my laptop lid closed all the time, and I have it hooked up to an external keyboard, monitor, and mouse. It has other inputs, which was why this was frustrating. |
Closing, please follow the wlroots issue linked above if you're interested in not turning outputs off on exit. |
Please fill out the following:
swaymsg -t get_version
orsway -v
I used the latest git.
sway version 1.8-dev-76232927 (Nov 16 2022, branch 'master')
sway -d 2> ~/sway.log
from a TTY and upload it to a pastebin, such as gist.github.com.https://gist.github.com/Davester47/33e6ba6e5bd189592d764530c8b12c27
These messages also appeared in the tty after closing sway.
I used the default.
I noticed this issue because I use an external monitor and keep my laptop closed most of the time. Exiting sway with the lid closed puts the computer to sleep, but it exits to the tty like normal if the lid is open.
After waking it from sleep, the computer goes to the tty like normal except for the error messages from dmesg I included above.
The text was updated successfully, but these errors were encountered: