Hyprland 0.53.1 SIGSEGV on wake from idle with external monitor connected #12884
Replies: 6 comments 6 replies
|
I've experienced the same issue today (I upgraded my system yesterday, updating from hyprland 0.52.2 to 0.53.0) Steps to reproduce crash:
I've crashed hyprland 4 times now, where one was accidental. I've noticed that the one time i triggered the crash by accident, my system was still responsive. The other 3 times when I was testing the issue, my system became unresponsive after crashing (also couldn't switch to other TTYs). |
|
After accidentally triggering the bug again this morning, I can tell you that the issues is still present in hyprland 0.53.1. @jinnko you can update the title to 0.53.1 as the crash presists in this version hyprctl version: hyprlandCrashReport1152339.txtHyprland Crash ReportI tried so hard, and got so far... Hyprland received signal 12(SEGV) System info: GPU: os-release: Libraries: Backtrace: Log tail: |
|
can someone get a debug stacktrace? |
|
I tried fixing Hyprland display issues for 12 hours yesterday. Hyprland in general seems to bug out like crazy when the display turns off. Windows go invisible and the Hyprlock background turns black. I have an LG Ultragear on Display Port. The problem is simple to reproduce - turn off the monitor off... then on. I would love to know HOW to dig into the reasons. If exhausted my options from the wiki. I'm new to Hyprland and absolutely am a DIY individual, but this issue drove me into a wall. |
|
I'm experiencing consistent Hyprland crashes whenever my monitors wake from DPMS sleep. This happens every time hypridle triggers System info
LibrariesReproduction
This happens 100% of the time. The crash is immediate on wake. Important: The trigger is the monitor waking up, not just DPMS. I also have a laptop connected to the same monitor via HDMI (with auto-input-switch disabled on the monitor). When the laptop goes to sleep and the monitor turns off, waking the laptop back up — even when the monitor is displaying the laptop's HDMI input and the DP port isn't even the active input — is enough to crash Hyprland on the desktop. The mere act of the monitor powering on causes the DP link state change that triggers the crash. What happensLooking at the Hyprland log tail in the crash report, the sequence is:
This is the classic DisplayPort behavior where the link drops during DPMS sleep (unlike HDMI which stays connected). Aquamarine treats it as a real unplug. Crash sequence (repeats every time)First crash — SIGABRT during surface commit: Second crash — SIGSEGV on safe-mode restart during DRM teardown: Hyprland restarts with Aquamarine log tail at crash timehypridle configgeneral {
lock_cmd = pidof hyprlock || hyprlock
before_sleep_cmd = loginctl lock-session
after_sleep_cmd = hyprctl dispatch dpms on
}
listener {
timeout = 300
on-timeout = loginctl lock-session
}
listener {
timeout = 330
on-timeout = hyprctl dispatch dpms off
on-resume = hyprctl dispatch dpms on && brightnessctl -r
}Crash reportsFull crash reports attached. All 3 from today show the identical backtrace. WorkaroundRemoving the DPMS off listener from hypridle prevents the crash entirely — keeping the monitors awake avoids the DP link loss that happens when the monitor enters sleep mode. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Since upgrading to 0.53.0 I've been getting these crashes for the last couple of days. Reports in the discussion also demonstrate this issue persists on 0.53.1.
It seems to be when connected to the external monitor and hyprlock activated idle, causing the DPMS to turn off the screens. I believe the actual crash happens on resuming from idle (not sleep or suspend).
hyprland-crash-config.txt
coredumpctl info
hyprlandCrashReport2092.txt
All reactions