hyprlock: [Bug] Crash after waking up from suspend
Whenever my system wakes up from suspend and Hyprlock was active, I am placed on a red screen with no other way to regain access to Hyprland apart from opening tty and running pkill. I confirmed that the issue wasnt related to hypridle, as I ran a new Hyprland session with 2 exec-once in the config, one running hyprlock and one suspending the system after a few seconds. I discovered this in the tty at the end of the output. I am using the git version of Hyprland
[CRITICAL] [core] Disconnected from pollfd id 0: x: 1920, y: 1080] and pixel [Vector2D: x: 1920, y: 1080]
About this issue
- Original URL
- State: closed
- Created 4 months ago
- Reactions: 6
- Comments: 23 (7 by maintainers)
Commits related to this issue
- core: restart on a critical signal or SIGHUP ref #76 — committed to hyprwm/hyprlock by vaxerski 4 months ago
committed the patch
The patch seems to have fixed the issue, thanks!
patch.txt try this, it attempts to restart hyprlock on unexpected death.
As I woke up today I found my monitors in red. I hopped on my computer from another computer to look at the logs and there was no new entries when I f.ex moved my mouse or typed on the keyboard. The last line in the logs was something mentioning
wl_display@1.delete_id.As @frisodubach mention
This seem to be related and I am able to reproduce the issue by running hyprlock then disconnect and reconnect one of my monitors. The result is a frozen hyprlock and red monitors, I unfortunately have to sigterm Hyprland as well. I tried running
hyprctl exitbut getHYPRLAND_INSTANCE_SIGNATURE not set! (is hyprland running?)I’ve now started running hyprland from TTY and piping everything into a log file, I should be able to get better logs soon.