Bug 505356

Summary:	HDMI Display (TV) cannot wake up from sleep, even when PC actually already woke up
Product:	[Plasma] kwin	Reporter:	mohdyusuf
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	john.kizer, nate
Priority:	NOR
Version First Reported In:	6.3.5
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description mohdyusuf 2025-06-08 22:06:13 UTC

SUMMARY
HDMI TV display connected to PC (Fedora 42 + KDE) cannot wake up from sleep.
PC can wake up on mouse + keyboard USB trigger, but TV screen will not show display.
Same hardware works completely fine on Windows 11 (screen can wake up fine).

STEPS TO REPRODUCE
1. Leave PC idle, it goes to sleep. Screen goes to sleep (HDMI).
2. Tap on keyboard, PC wakes up from the sleep.
3.

OBSERVED RESULT
TV shows “hdmi connected” but the screen remained dark.

EXPECTED RESULT
TV screen should wake up. 

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: Fedora 42, kernel 6.14.9-300.fc42.x86_64
KDE Plasma Version: 6.3.5 
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0

ADDITIONAL INFORMATION
Hardware:
- AMD Ryzen 9 7900
- NVidia RTX 4090 (Gigabyte) - driver version 575.57.08
- Gigabyte B650 Aorus Pro AX
- TV TCL QM8 144hz

Comment 1 mohdyusuf 2025-06-09 17:21:39 UTC

Small correction to the observed result.

OBSERVED RESULT
TV shows “hdmi connected” but the screen says “No signal.”

Comment 2 John Kizer 2025-06-19 05:46:33 UTC

Hi - this one appears to be an upstream NVIDIA driver issue. For reference, the most recent NVIDIA documentation on workarounds is located at bullet point 4 of this document: https://download.nvidia.com/XFree86/Linux-x86_64/575.57.08/README/dynamicpowermanagement.html#KnownIssuesAndW6426e

And the NVIDIA forums thread on this topic is located here: https://forums.developer.nvidia.com/t/black-screen-after-pc-wakes-up-from-suspend/304023?u=john.kizer

Thanks!

*** This bug has been marked as a duplicate of bug 466705 ***