Bug 411977 - Graphical glitch on Breeze window buttons when GPU is stressed
Summary: Graphical glitch on Breeze window buttons when GPU is stressed
Status: RESOLVED DUPLICATE of bug 397215
Alias: None
Product: Breeze
Classification: Plasma
Component: window decoration (show other bugs)
Version: 5.16.5
Platform: Manjaro Linux
: NOR minor
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-16 16:09 UTC by TYY331
Modified: 2019-09-16 17:07 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Graphical glitches (1.26 KB, image/png)
2019-09-16 16:09 UTC, TYY331
Details

Note You need to log in before you can comment on or make changes to this bug.
Description TYY331 2019-09-16 16:09:02 UTC
Created attachment 122683 [details]
Graphical glitches

SUMMARY
Breeze Window buttons present graphical glitches when hovered making certain parts translucent, this glitch happens when the GPU (Intel HD 4400 in my case) is stressed in some way like playing fullHD video or another GPU intensive task

STEPS TO REPRODUCE
1. stress the GPU in some way (to cause FPS drops on Kwin)
2. hover the title bar buttons

OBSERVED RESULT
Graphical glitches are noticed around the window buttons

EXPECTED RESULT
Breeze buttons should render correctly upon hover

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 4.19 (Manjaro), also tested on KDE Neon live USB
(available in About System)
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.61
Qt Version: 5.13.1

ADDITIONAL INFORMATION
This glitch also happens in QT 5.12 and older version of plasma and frameworks, It might be affecting only Intel GPUs but I can't test because I don't have newer/older intel GPUs and Nvidia/AMD GPUs.

WORKAROUNDS TESTED
Tried using the Intel driver in SNA/UXA and DRI2/DRI3 settings, tearfree ON/OFF to no avail
Tried using the modesetting driver, same results
This glitch also happens with window decorations fork like SierraBreeze and SierraBreezeEnhanced
Aurorae window decorations are unaffected by this bug
Comment 1 trmdi 2019-09-16 17:07:26 UTC

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