-
Notifications
You must be signed in to change notification settings - Fork 202
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
Red screen & unable to unlock when changing screen #282
Comments
This means that swaylock hit a protocol error, stemming from this check: https://gitlab.freedesktop.org/wlroots/wlroots/-/blob/master/types/wlr_session_lock_v1.c#L145 If you can reproduce with swaylock 1.7.2 (or master), run swaylock manually with |
I am facing the exact same issue and started debugging, but then I realized that I'm in fact using I see that there is another discussion for swaylock-effects: mortie#97 |
Note: this error can be caused by |
Yes, it is really hard for me to reproduce and I am not even sure if 1.7.2 might have fixed it, can't remember if the last red screen was before or after the upgrade |
Ok, I just had this today again, so it is indeed still an issue. Sadly I had no time for investigation so I have to wait until the next time this happens |
With sporadic bugs like this, I'd recommend always recording output with WAYLAND_DEBUG=1, and when you do get a crash, just attach the logs for the run leading up to the
(In the script, the |
This happens fairly frequently to me, and I captured logs with Btw: you can unlock the session by switching to a different TTY and starting swaylock there (with appropriate |
Be very careful with this as such log also includes key codes of keypresses made during the execution of the application. |
This is with ext-session-lock (swaylock 1.7) and sway 1.8. If I lock my laptop, suspend it by closing it, then connect it to my docking station with two external monitors and resuming it, I get greeted by completely red screens on both monitors and no way to unlock except rebooting the machine.
I can see this in the logs:
Not sure if that is related, but shortly after, waybar dumps core.
The text was updated successfully, but these errors were encountered: