Bug 489294

Summary:	Fullscreen applications do not output video after restarting the Monitor
Product:	[Plasma] kwin	Reporter:	dirleyjordan
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	xaver.hugl
Priority:	NOR
Version First Reported In:	6.1.1
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description dirleyjordan 2024-06-27 09:25:19 UTC

SUMMARY
Monitor reports no signal after being turned off and on again when any fullscreen (borderless) application (Wayland or XWayland) is in focus. Hitting the super key to bring up the application launcher brings back picture and switching focus to a window with a border is also fine. Switching focus back to a borderless application gives no signal to the monitor again.
Restarting the desktop solves this until the monitor is restarted.

This is common for me as my OLED monitor needs to do a pixel refresh every so often which involves turning it off and on again.

STEPS TO REPRODUCE
1. Open a fullscreen application (Steam games, YouTube fullscreen, etc.)
2. Turn the monitor off and on again

OBSERVED RESULT
The picture will not return as long as the fullscreen app is in focus.

EXPECTED RESULT
The picture returns displaying the fullscreen app as it was when the monitor was turned off.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: CachyOS (Plasma Wayland)
(available in About System)
KDE Plasma Version: 6.1.1
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
Nvidia proprietary driver with a single monitor hooked up via DisplayPort.

Comment 1 Zamundaaa 2024-06-27 10:17:26 UTC

If you set KWIN_DRM_NO_DIRECT_SCANOUT=1 for KWin, does the problem go away?

Comment 2 dirleyjordan 2024-06-27 11:04:50 UTC

(In reply to Zamundaaa from comment #1)
> If you set KWIN_DRM_NO_DIRECT_SCANOUT=1 for KWin, does the problem go away?

I set it in /etc/environment and restarted but it doesn't seem to have helped unfortunately.

Comment 3 Zamundaaa 2024-06-27 11:45:39 UTC

Okay. Do you have adaptive sync enabled?

Comment 4 dirleyjordan 2024-06-27 12:00:42 UTC

(In reply to Zamundaaa from comment #3)
> Okay. Do you have adaptive sync enabled?

Yes, disabling it has fixed the issue.
Is there anything I can do to prevent this while still having adaptive sync enabled?

Thank you for your help in finding the problem.

Comment 5 Bug Janitor Service 2024-07-12 03:47:09 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Zamundaaa 2024-07-12 15:29:18 UTC

(In reply to dirleyjordan from comment #4)
> (In reply to Zamundaaa from comment #3)
> > Okay. Do you have adaptive sync enabled?
> 
> Yes, disabling it has fixed the issue.
> Is there anything I can do to prevent this while still having adaptive sync
> enabled?
Unfortunately not that I know of. You can report it to https://forums.developer.nvidia.com/c/gpu-graphics/linux/148, and hope that NVidia fixes it.