Frozen image after dpms on #10231
Replies: 9 comments 5 replies
-
|
I was able to find logs possibly related to the issue. Log[LOG] [AQ] drm: Disabling output DP-2
[LOG] [AQ] drm: Disabling output HDMI-A-1
[LOG] Hyprctl: dispatcher dpms : off
[LOG] [CWLCompositorResource] New wl_surface with id 17 at 5f0c81a5fa80
[LOG] CWLSurface 5f0c819afa40 called init()
[LOG] LayerSurface 5f0c813e81b0 (namespace notifications layer 3) created on monitor DP-2
[LOG] [CLayerShellProtocol] New wlr_layer_surface 5f0c813e81b0
[LOG] LayerSurface 5f0c813e81b0 mapped
[LOG] [AQ] drm: Modesetting DP-2 with [email protected]
[LOG] [AQ] drm: Modesetting HDMI-A-1 with [email protected]
[LOG] LayerSurface 5f0c813e81b0 destroyed
[LOG] Forcing an unmap of a LS that did a straight destroy!
[LOG] LayerSurface 5f0c813e81b0 unmapped
[LOG] Framebuffer created, status 36053
[LOG] CWLSurface 5f0c819afa40 called destroy()
[LOG] [AQ] drm: Modesetting DP-2 with [email protected]
[ERR] [AQ] drm: Cannot commit when a page-flip is awaiting
[ERR] Couldn't commit output DP-2
[LOG] [AQ] drm: Modesetting HDMI-A-1 with [email protected]
[ERR] [AQ] drm: Cannot commit when a page-flip is awaiting
[ERR] Couldn't commit output HDMI-A-1
[LOG] Hyprctl: dispatcher dpms : on -> Couldn't commit output {}
[LOG] [AQ] drm: Modesetting DP-2 with [email protected]
[LOG] [AQ] drm: Modesetting HDMI-A-1 with [email protected]
[LOG] [CLinuxDMABUFParamsResource] Creating a dmabuf, with id 45: size [Vector2D: x: 1876, y: 983], fmt XR24, planes 2
[LOG] [CLinuxDMABUFParamsResource] | plane 0: mod 144115188621556484 fd 139 stride 7680 offset 0
[LOG] [CLinuxDMABUFParamsResource] | plane 1: mod 144115188621556484 fd 180 stride 2048 offset 7864320
[LOG] Cleanup: destroyed a layersurface
[WARN] [/usr/src/debug/hyprland/Hyprland-0.48.1/src/protocols/SessionLock.cpp:49] SessionLockSurface object remains but surface is being destroyed???
[WARN] [/usr/src/debug/hyprland/Hyprland-0.48.1/src/protocols/SessionLock.cpp:49] SessionLockSurface object remains but surface is being destroyed??? |
Beta Was this translation helpful? Give feedback.
-
|
I can reproduce most of the same issue as here and #9440. A difference is that my "main" monitor still turns off and on correctly, while the secondary monitor is fozen w/ Dual monitors, I'm not using I am using integrated AMD ryzen 9 graphics, though I do have a 3090 installed but using it for other things. I'll see if I can repro the same logs. details/logsI have a pretty minimal install right now on a new computer with 2 monitors. A lot of data has already been shared in #9440 and here, but to add a bit: hyprland.conf |
Beta Was this translation helpful? Give feedback.
-
|
I think that's a very old issue. In my case, when dpms off/on while using hypridle/lock, on wake up, only main monitor wakes up but everything is frozen, it takes 10-15 seconds for the second monitor to wake up and unfreeze. I noticed that since 0.46.x. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
I have the same problem after systemctl suspend (idk if it is calling |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm that |
Beta Was this translation helpful? Give feedback.
-
|
I have also been struggling with this problem since I first tried Hyprland in December. My monitor configuration looks like this: The DP monitor is a newer Acer one, and the HDMI is a very old Asus monitor from 2012. For me this happens every time DPMS is turned off/on, both the monitors will shut down at the same time, but upon waking them up, only the DP monitor instantly gets a signal and turns on, while the HDMI is still dark. The picture on the DP monitor is frozen until the HDMI display turns on after ~15 seconds. I tried turning both the monitors on/off, and noticed that if I turn off the DP monitor using hyprctl and then re-enable it, the DPMS starts working perfectly for the rest of the session. This only works with the DP monitor, turning the HDMI monitor on/off does nothing. For a while I just added a script that runs on startup that just cycles the monitor on/off, but I recently noticed that this has the side effect (although this also happens when just suspending the PC!) of forcing my GPU memory clock speeds to the highest all the time. This looks to be able to be fixed by cycling the DP monitor refresh rate from 170 -> 60 -> 170, and the memory clock speeds go back to 96MHz on idle from 1,22GHz. I tried this in KDE and none of the problems happen there, so I would assume this is a Hyprland problem. For now I have worked around this by just disabling auto-DPMS and adding a script to hypridle after_sleep_cmd that cycles the DP monitor refresh rate. Would be nice to see this investigated & fixed. Looks like others who have this problem are also using a RX 7800 XT, maybe there is a connection? System infoMonitors |
Beta Was this translation helpful? Give feedback.
-
|
I found the solution in my case. So in hypridle conf resume, it should look like : With this, both of my monitor are waking up properly and I don't have the IPC error. |
Beta Was this translation helpful? Give feedback.
-
|
Same issue for me on latest hyprland-git. From all the reading Ive noticed that the isse could be related to HDMI-A outputs since I have my monitor connected this way also. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
I have the exact same issue as #9440. For me this bug always occurs while locked (thats why I tough at first its a hyprlock bug), but I've had the same issue happen even when unlocked, although I am not sure what causes the issue while unlocked, it only happens sometimes.
System info
Log:
hyprland.log
Ask if you need other logs.
Beta Was this translation helpful? Give feedback.
All reactions