Bug 422341 - open windows do not repaint after a full screen application is closed
Summary: open windows do not repaint after a full screen application is closed
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.18.90
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-01 19:52 UTC by Pawel
Modified: 2020-11-28 12:34 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Pawel 2020-06-01 19:52:14 UTC 
SUMMARY

open windows do not repaint after a full screen application is closed. See the attached recorded video.


STEPS TO REPRODUCE
1. Open a bunch of apps and minimize them
2. Launch a game (from steam for example)
3. exit the game
4. maximize the applications - observe the windows are not repainted but instead stuck on a desktop wallpaper static image until resized or maximized

OBSERVED RESULT

the windows are not repainted but instead stuck on a desktop wallpaper static image until resized or maximized

EXPECTED RESULT

the windows should be fully repainted without the need to minimize, or move the window

SOFTWARE/OS VERSIONS

Operating System: Arch Linux 
KDE Plasma Version: 5.18.90
KDE Frameworks Version: 5.70.0
Qt Version: 5.15.0
Kernel Version: 5.6.0-1-amd-staging-drm-next-git-00586-g61216b378716
OS Type: 64-bit
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 5700 XT 


ADDITIONAL INFORMATION

https://mega.nz/file/F0wziAza
Comment 1 Vlad Zahorodnii 2020-06-05 08:43:29 UTC 
The video is not accessible because mega asks a decryption key.
Comment 2 Pawel 2020-06-05 14:03:14 UTC 
Hi,

Apologies, try this link:

https://mega.nz/file/Zt5HGaSI#j2fQU4Nj-7r_s7QWFoYIphWjLSI5uyuyGvAS-VWv51E
Comment 3 Pawel 2020-11-28 12:34:06 UTC 
Hi,

I can no longer reproduce this in 20.3.0 so marking as resolved.