Bug 426312

Summary: dual driver monitor doesn't wake display properly
Product: [Plasma] kwin Reporter: Ryein Goddard <ryein>
Component: compositingAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: claudius.ellsel
Priority: NOR    
Version First Reported In: 5.19.5   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Ryein Goddard 2020-09-08 18:31:01 UTC
SUMMARY
I have a dual driver monitor the Acer Predator 43 inch display.  It has dual display ports that allow the monitor to run at 144 hz. (side note: 144 hz option doesn't show up) but the issue I am bringing up here is when you wake the display from being turned off for "power saving" it doesn't come back properly.  I think the compositor is broken as all the extra effects like blur and transparency are broken and some windows like firefox are cut off and moved on the display and some windows even have a black border around it.

STEPS TO REPRODUCE
1. Get an acer predator 43 monitor 
2. let the display "sleep" or power off
3. wake the display with the keyboard or mouse

OBSERVED RESULT
As described above.  The display won't display correctly and compositor effects are "disabled" and visual artifacts exist.

EXPECTED RESULT
Everything should return as you left it with all effects working.

SOFTWARE/OS VERSIONS
Running latest KDE Neon User edition 5.19
Plasma Version : 5.19.5
Framewokrs 5.73.0
Qt 5.14.2
Kernel 5.4.0-45-generic
64 bit
Graphics Driver is Closed Source Nvidia driver with a 1070
Nvidia driver version 440.100

ADDITIONAL INFORMATION
To fix this problem you can simply change the compositor from whatever setting you had it on such as OpenGL 2/3 and switch it.  Then return it back to your original setting.  Everything appears as it was, except the window positions are wrong.
Comment 1 David Edmundson 2023-09-06 10:38:42 UTC
This bug was reported against an outdated version of KWin. We have made many changes since the. 
If the issue persists in newer versions can you reopen the bug report updating the version number.