-
Notifications
You must be signed in to change notification settings - Fork 36
Sway: Unlocking physlock after lid is closed (suspend/sleep) causes blank screen #112
Comments
|
Honestly, it's beginning to look like the answer is none. The current state of session lockers is embarrassing.
You can follow the discussion here, but it doesn't look to be moving forward: swaywm/wlroots#2706 |
Reading the relevant topic at Freedesktop/Wayland and swaywm/wlroots#2706 makes me think that exiting to TTY suddenly does not look as bad. |
Try hikari's screen locker. |
Is it provided in a separate package? If so, I can't seem to find it. |
No, it's part of the compositor. Logo+Shift+Backspace is the keybinding in the default configuration. |
Well, then it's more of a "switch to another WM". |
Ok, well that was just a suggestion. I'm happy if you fix sway with physlock or update swaylock to use the lockscreen protocol.
BTW, these are either bugs in the compositor or layer shell protocol, not the screen locker. |
This is being discussed here: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/100 |
#96 is similar to my issue, but in my case I am using Sway, not LightDM.
swayidle
is used to trigger the lock before suspend like so:When the lid is closed, suspend is triggered according to
/etc/systemd/logind.conf
which defines:When closing the lid, suspend is indeed triggered, and when waking form suspend,
physlock
shows a password prompt. But when the correct password is entered, the screen switches to a blank black screen. The only way to fix this is to switch to a different TTY, login, and kill Sway.Just to clarify, the blank screen does not occur when using
physlock
during "regular" usage, i.e. without sleep/suspend triggers.If I manually lock, then close the lid and suspend, the blank screen doesn't happen. But in that case, when I wake from suspend, then unlock, then proceed to lock again, this is the output:
And
ps aux | grep physlock
returns a list of ~60physlock
processes for theroot
user.The text was updated successfully, but these errors were encountered: