External monitor doesn't resume properly on wake up from sleep and hibernate

[logrusx]

Already reported ? *

• I have searched the existing open and closed issues.

Regression?

I don't know, I started using Hyprland only recently

System Info and Hyprland Version

System/Version info

Hyprland 0.46.2 built from branch  at commit 0bd541f2fd902dbfa04c3ea2ccf679395e316887  (version: bump to 0.46.2).
Date: Thu Dec 19 19:26:47 2024
Tag: v0.46.2, commits: 5566
built against:
 aquamarine 0.5.0
 hyprlang 0.5.3
 hyprutils 0.4.0
 hyprcursor 0.1.10
 hyprgraphics 0.1.1


flags set:
debug


System Information:
System name: Linux
Node name: joro-lt
Release: 6.1.91-gentoo-default
Version: #4 SMP PREEMPT Fri Jan  3 17:42:14 EET 2025


GPU information: 
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2560] (rev a1) (prog-if 00 [VGA controller])
05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c5) (prog-if 00 [VGA controller])
NVRM version: NVIDIA UNIX x86_64 Kernel Module  550.144.03  Mon Dec 30 17:44:08 UTC 2024


os-release: NAME=Gentoo
ID=gentoo
PRETTY_NAME="Gentoo Linux"
ANSI_COLOR="1;32"
HOME_URL="https://www.gentoo.org/"
SUPPORT_URL="https://www.gentoo.org/support/"
BUG_REPORT_URL="https://bugs.gentoo.org/"
VERSION_ID="2.17"


plugins:

Description

When waking up from S3 sleep or hibernate (both tested), my external monitor does not wake up properly. The picture is restored, but nothing changes. When I move the mouse it goes there but doesn't show up. I'm sure it's logically in that space because it doesn't return immediately on the way back as if it had stopped at the edge. Also the floating window on my integrated display loses focus. I can move windows on that workspace but the display is never refreshed.

The way to resume proper operation of the display is to VT switch to the DM screen or an FB console.

One detail which might or might not be relevant is the external display always lights up first after VT switch. When resuming, either from sleep or hibernate, the integrated display comes up first.

I am running Hyprland on the AMD iGPU. I use GDM to start the session.

EDIT: I tested the main branch as well. Now the internal monitor comes up first, but still the issue persists.

How to reproduce

Provided you have an external display connected (It might happen on a desktop computer with two monitors as well but I have no way to test that):

1. Log in.
2. Issue systemctl suspend/hibernate or put the system to sleep in another way.
3. Resume
4. Move the mouse through the external (or maybe secondary display on a desktop setup). It won't refresh.

Attach not paste

• I understand that all text files must be attached, and not pasted directly. If not respected, this issue will likely get closed as spam

Checklist of files to include below

• Hyprland config - hyprctl systeminfo -c (always include)
• Crash report (always include in case of crash)
• Video (always include in case of a visual bug)
• Logs (might contain useful info such as errors)

Additional info & File uploads

hyprland.log

config.txt

With hypridle and hyprlock configured, it looks like hyprlock is able to alter the picture a bit before it gets frozen like that even after entering the password:

Here's an issue that might be related. At first I didn't consider it because it seemed related to dpms function and I didn't experience that when the monitor was dpms turned off, but the first comment has pointed me in that direction:

Only one monitor resumes after dpms off with new wlroots

It was also closed but now I see it was closed before a major refactoring occurred.

[ctilley83]

This is similar to the behavior I'm experiencing. I use uwsm to manage hyprland. The problem has been going on for a couple days. Don't have a bisect for this one. I use hypridle and simply turn the display off with dpms. If I wake the display within a few minutes the system doesn't crash. Beyond a certain amount of time then it's guaranteed to crash.

System Info

Crash Log

[logrusx]

This is similar to the behavior I'm experiencing.

I'm not sure if it's the same issue, but might be related.

I use uwsm to manage hyprland. The problem has been going on for a couple days. Don't have a bisect for this one.

I too use uwsm, but the issue was present before that. Also I don't think it's recent because on Gentoo the stable version is 0.45.2 and this is the version I first installed a few days ago and the issue was present there as well.

I use hypridle and simply turn the display off with dpms.

At first I didn't use hypridle but simply issued systemctl suspend

If I wake the display within a few minutes the system doesn't crash. Beyond a certain amount of time then it's guaranteed to crash.

It doesn't crash for me but certainly, if I let the system sleep overnight the next day the external monitor is not waked at all and then I need to unplug the monitor, switch it on and off so that it starts seeking signal to make the system to detect it. I still haven't tested if that works reliably as I just came with the idea while I was writing the paragraph below. I even have monitors.conf generated from nwg-displays and that has improved the situation a bit in the cases when the external monitor wakes up. Before that I haven't observed it resumed properly on it's own and now it occasionally does so. However I haven't used Hyprland that long to have more reliable observations.

That might be related to the NVIDI chip that's driving the MUX. I'm not sure how to make the chip do something so that I can test if it's some power saving functionality in it causing this. And when I was writing this line I came up with the idea to unplug the monitor and went back and edited it in in the above paragraph. Thank you for provoking me to think about it!

Actually this is only the second morning I experience the issue in this way. The previous few mornings it either woke up the external monitor partially or the computer was completely turned off.

Best Regards,
Georgi

[logrusx]

@ctilley83

If I wake the display within a few minutes the system doesn't crash. Beyond a certain amount of time then it's guaranteed to crash.

It doesn't crash for me...

Well it started. But it started only after I switched to SDDM and setup Hypland as the compositor for SDDM.

I decided to test for how long it'll take to stop recognizing the external monitor and after maybe a couple of hours it froze on the password screen and stayed there. NumLock was responsive, but the only thing I could do was to switch to an FB console and restart SDDM.

BTW how do you switch to another VT? You should use CTRL+ALT+F and if it doesn't work, do you know the Magic SysRq combinations?

You first need to switch the keyboard off of RAW mode with Alt+SysRQ(or PrtScr if you don't have it)+R.

Best Regards,
Georgi

[logrusx]

@ctilley83
I suspect yesterday's crash happened due to power outage and problem's I'm having with S3 sleep on battery since somewhere after Linux kernel 6.1.47.

Please try with the SysRq combinations next time, I think your system might not have crashed, but maybe only the graphics.

[logrusx]

Still experiencing the same issue with 0.48.0. Unplugging the monitor works reliably but sometimes it needs a few retries. One thing I've noticed is when the unplugging is successful, the mouse would move on my primary (integrated) display in the right bottom quadrant, as if the display is divided in a 3x3 grid. If that happens, when I plug the external monitor back, it'll certainly wake up properly.

It doesn't display the workspace though. I honestly don't know which workspace it display but it's empty. I need to go back to the workspace that used to be on it when I suspended the computer.

I see a a whole bunch of users with hybrid graphics with NVIDIA dGPU's experiencing similar problems. I didn't have such problems on Gnome.

p.s. although unrelated the S3 sleep problems have gone now, with the whole 6.13 line and recent 6.12 kernels.

[vaxerski]

Hello there!

This issue has been closed, as we are moving from issues to discussions. More about this can be found here and in #9854.

Firstly, please make sure this issue is still relevant in latest Hyprland. If so, we ask you to open a discussion (please read the discussion guidelines first, in the pinned post)

Thank you for your understanding!

[jonnjonnjo]

so, the only solution is only by doing the unplug-plug to the external monitor cable?

[logrusx]

so, the only solution is only by doing the unplug-plug to the external monitor cable?

If the monitor does not wake up at all - yes. If it does, then you can cycle through a frame buffer console a couple of times.

[logrusx]

Soft solution I've found - open the hyprland monitor configuration, change something small and just save the file. Hyprland will reload the configuration and re-initialize the monitor. This will save you cycling through the FB console several times. Unless the monitor doesn't wake up at all. Then re-plugging is the only solution.

Don't routinely unplug your monitor, you'll damage the port at some point, always try the soft solutions first.

[jonnjonnjo]

so still there's no solution?

How come people use hyrpland when it's not working properly on multi-screen device??

[logrusx]

so still there's no solution?

There is, I've written it above. Edit monitor configuration, save, revert the charge, save. This would cause Hypland to reinitialize the monitor and fix the issue. If it still doesn't work, unplug the monitor and plug it in again.

How come people use hyrpland when it's not working properly on multi-screen device??

A lot more is working than in most other compositors. I haven't used many, but maybe Sway is the only real competitor.

So yeah, some stuff is not working great but the rest is definitely worth it. And it'll only get better. I hope...

[logrusx]

New information:

Hyprlock's 0.9.2 release included "monitor replug workaround for nvidia" and that prompted me to conduct some more tests.

My external monitor is capable of handling 10bit signal. However there was a problem with bitdepth=10 in some of the recent versions of Hyprland and I used to keep it commented since then. This is the line I've been using to comment, save, uncomment, save to make Hyprland reinitialize the monitor and fix the frozen picture. However, with testing the yesterday's release of Hyprlock 0.9.2 I found out that the issue with 10bit signal is resolved and, if I keep it, the external monitor wakes up properly. At least for now. If I disable it, it still wakes up with frozen Hyprlock screen or if I have disabled hyprlock, with whatever was on the screen previously.