| Summary: | Certain Plasma dialogs are sometimes or always super transparent with no blur | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Nate Graham <nate> |
| Component: | effects-various | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | kde, plasma-bugs |
| Priority: | VHI | Keywords: | regression |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/plasma/kwin/commit/1b4c725d108b595b85a75aaa2c69721ffb085bef | Version Fixed In: | |
| Sentry Crash Report: | |||
| Attachments: |
Task Manager tooltips
Transparent Breeze Task Switcher Transparent Large Icons Task Switcher KWin support information |
||
Created attachment 129612 [details]
Transparent Breeze Task Switcher
Created attachment 129613 [details]
Transparent Large Icons Task Switcher
Created attachment 129614 [details]
KWin support information
Seeing the same in Task Manager after having updated just now. I only restarted plasmashell yet but not KWin, so I think KWin's not at fault here. Cool, moving to plasmashell then. Glad I'm not insane! Hmm, I just bisected plasma-workspace, plasma-desktop, and plasma-framework back to June 1st and I didn't manage to find the guilty commit. > but was unsuccessful as it did not build past a certain point in time. :(
iirc there was a breaking change in kscreenlocker 5.19. so you need sometimes to switch between kscreenlocker 5.18 and kscreenlocker 5.19. :/
That didn't help sadly. Do you have any idea what could have been responsible for this, or where I should look? Marking VHI as we can't ship this regression in 5.20. Only affects X11, not the Wayland session. Did some looking.
I'm pretty sure it's 309fbf1837863c483b04491eda8af8bc5235260a in kwin
(which means it's not frameworks and we have a whil)
adding some debug:
@@ -411,8 +411,10 @@ QRegion BlurEffect::blurRegion(const EffectWindow *w) const
+
if (value.isValid()) {
+ qDebug() << "start" << w->shape() << w->rect();
.....
+ qDebug() << "end" << region;
} else if (w->decorationHasAlpha() &&
results in
22:17:59.165 KWin::BlurEffect::blurRegion start QRegion(0,0 364x239) QRect(0,0 364x239)
22:17:59.165 KWin::BlurEffect::blurRegion end QRegion(null)
not sure why it makes a difference &'ing these two rects should result in the same thing.
Edit, it's not that commit, but it is that area of code. For some reason the tooltip skips all the paths that set region (In reply to David Edmundson from comment #11) > not sure why it makes a difference &'ing these two rects should result in > the same thing. Is the appRegion empty? A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/94 Git commit 1b4c725d108b595b85a75aaa2c69721ffb085bef by David Edmundson. Committed on 30/06/2020 at 13:59. Pushed by davidedmundson into branch 'master'. Update clientGeometry for Unmanaged windows It was udpated when we received a configure event but not in the initial track. The symptom of this being missed out was that blur would not be applied to the window. Related: bug 423297 M +1 -0 unmanaged.cpp https://invent.kde.org/plasma/kwin/commit/1b4c725d108b595b85a75aaa2c69721ffb085bef |
Created attachment 129611 [details] Task Manager tooltips Everything KDE from git master with Qt 5.15.0 on openSUSE Tumbleweed. SUMMARY Various (but not all) Plasma dialogs are 100% transparent with no blur. The following Plasma dialogs exhibit this problem 100% of the time for me: - All Task Switchers (Breeze, Large Icons, Small Icons, etc.) The following Plasma dialogs exhibit this problems sometimes: - Task Manager tooltips (the first one you hover over is 100% transparent, then subsequent ones are fine; see video) The following Plasma dialogs never exhibit the problem for me: - Kicker/Kickoff - System Tray - Display chooser OSD - Volume/brightness/etc. OSD This started happening to me a week or two ago. I attempted to git bisect KWin but was unsuccessful as it did not build past a certain point in time. :( I am using X11 with a 250% scale factor on a 4k screen and an Intel integrated GPU.