Monitor gets signal but remains black after coming out of (monitor) standby on GNOME

[Gert-dev]

NVIDIA Open GPU Kernel Modules Version

580.82.07

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.

• I confirm that this does not happen with the proprietary driver package.

Operating System and Version

Arch Linux

Kernel Release

6.16.5

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.

• I am running on a stable kernel release.

Hardware: GPU

NVIDIA GeForce RTX 4090 Laptop GPU

Describe the bug

(This is an upstream report of mutter issue 3579 that was pinpointed to likely be caused by the NVIDIA open kernel modules.)

Often, when the secondary monitor attached to my NVIDIA dGPU comes back after having blanked, the monitor stays black and gives 'no signal', and then rapidly gets signal but shows nothing, whilst the internal AMD iGPU monitor is fine.

Switching to a TTY and back fixes it.

To Reproduce

1. Have an internal screen attached to an iGPU and an NVIDIA dGPU.
2. Perform an action that blanks the monitors (lock the screen, suspend, ...).
3. Wait several minutes.
4. Press the keyboard to resume or unlock and wait for monitors to come back.
5. Observe the internal monitor coming back, but the external monitor giving 'no signal' for a moment, then indicating there is signal, but GNOME doesn't show up.

Bug Incidence

Sometimes

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

More Info

This is using GNOME 48 with mutter 48.4.

• When this occurs, the monitor does come out of standby, shows 'no signal' after ~5 seconds, and then suddenly removes the OSD message with the monitor LED now indicating it has signal, but the screen remains black (and the GNOME lock screen never shows up). Perhaps a race condition or timing issue somewhere in mutter?
• It seems to matter how long you wait after the screens blanking. If you immediately try to unlock after blanking and the monitor having given 'no signal', it almost always comes back as expected, as if mutter or a driver doesn't immediately release some state until at least several minutes later.
• The monitor is a Gigabyte MO34WQC, which always takes ~5 seconds before it gets its initial signal after it gets connected or configured.
• I used to have this on boot as well, leading me to believe this was this bug, but I managed to fix that by early loading the NVIDIA driver. Since then this never happens on (re)boot.
• To work around this, I can drop to a TTY and go back, and then the monitor will be used properly.
• The monitor is being recognised when this happens and is seen as connected successfully in GNOME when this happens.
• I haven't noticed any errors or warnings in the system logs around this.

To work around this, I can drop to a TTY and go back, and then the monitor will be used properly.

The monitor is being recognised when this happens and is seen as connected successfully in GNOME when this happens.

I haven't noticed any errors or warnings in the system logs around this.

[Gert-dev]

#572 sounds similar and may be related, but specifically mentions KDE instead.

In my case I also have a monitor attached to the iGPU as well that always comes back successfully.

[Gert-dev]

Some KMS debugging logs from mutter can be found here in the upstream post.

I was suggested to also explicitly mention that there are KMS hotplug events occurring as part of this problem. This may or may not be relevant to the driver - furthermore, the monitor isn't physically being hotplugged (by replugging the cable plug or similar), it just happens as part of normal operation and screen locking.