Repository navigation
session lock screen dies when removing external monitor while locked #16679
Replies: 2 comments
|
Same here with AMD, but only after upgrading to 0.57 |
0 replies
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hyprland version
v0.56.2
Is this a regression?
Don't know
What's the bug?
I usually have an external monitor attached to my notebook and the notebook lcd disabled. when the lock screen (I use DMS/quickshell) is displayed and I disconnect the monitor, I very often get the 'oopsie daisy your lock screen died' error shown on the notebook and the session is stuck until I recover it from a TTY. Hyprland log shows
onGetLockSurface: monitor is gone for output resourceand quickshell logswl_display#1: error 0: invalid object NI've had Claude Code diagnose this, it reproduced the issue and came up with a patch. I'll post it upon request since I honestly don't have the bandwidth to 'fully understand' what's going on there. The gist of it is that
onGetLockSurfacein src/protocols/SessionLock.cpp returns too early, leading to a missing resource which then leads to failing communication between lock screen and hyprland.Reproduction steps
Result is the 'your lockscreen died' screen on the Notebook LCD in most cases, but sometimes it works as expected and the lock screen is shown.
Relevant part of my
hyprland.lua:Attachments
systeminfo.txt
dms-journal.log
hyprland-excerpt.log
I acknowledge that:
I have searched all (open and closed) discussions and issues and my problem is not there.
I have read the Code of Conduct and agree to follow it.
I wrote this request with my own hands, my own keyboard, and in my own words.
All reactions