Bug 461098

Summary: Maximizing a window causes it to freeze with compositor on
Product: [Plasma] kwin Reporter: oldherl <oldherl>
Component: compositingAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: 5.26.2   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: After maximizing a konsole window.

Description oldherl 2022-10-28 06:54:42 UTC
Created attachment 153251 [details]
After maximizing a konsole window.

SUMMARY
When compositor is on, maximizing a window with either the button or double click on the decoration, the window content freezes and wrong pixels are drawn on the extended area.

STEPS TO REPRODUCE
1. Make sure you have compositor on.
2. Open any non-maximized application window, such as konsole, and to make it updates regularly. I run "watch date" in the window, but you can also use any other animations etc. 
3. Maximize the window with double click on the decoration, or use the maximize button on the top right.

OBSERVED RESULT
The window freezes. It doesn't update the contents, but actually it is receiving input. For example, press some keys in the konsole window, it won't show up. But if you un-maximize it, it doesn't freeze anymore and those letters appears in the konsole window.

EXPECTED RESULT
It should not freeze on maximizing.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.26.2
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6
Kernel Version: 6.0.2-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 6800H with Radeon Graphics
Memory: 14.3 GiB of RAM
Graphics Processor: REMBRANDT
Manufacturer: TIMI
Product Name: Redmi Book Pro 15 2022

ADDITIONAL INFORMATION
There is a similar report on https://bbs.archlinuxcn.org/viewtopic.php?id=12985 .
Comment 1 oldherl 2022-10-28 06:58:39 UTC
FYI, I'm using 200% Global scale.
Comment 2 oldherl 2022-10-28 10:00:54 UTC

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