https://bugs.kde.org/show_bug.cgi?id=520896

--- Comment #7 from Angel Parra <[email protected]> ---
Created attachment 192855
  --> https://bugs.kde.org/attachment.cgi?id=192855&action=edit
drm_info output when background is dark (1/2)

> Okay, at least that won't affect the release then, since overlays are still 
> off
by default on AMD.

I would not be so confident about that. According to nvtop, plasmashell is
running on my AMD iGPU (device 1 in my setup) with only Graphic type, and then
there are three instances of kwin_wayland processes all with the same exact
command line arguments and same xwayland-xauthority. One is running on my AMD
card (dev 1) with TYPE Both G+C and the other two are running on my Nvidia GPU
(dev 0) with TYPE Graphic and TYPE Compute respectively. The one that has the
highest GPU usage of the three is the one that's running on the AMD card and
the other two that run on the Nvidia GPU mark their GPU usage as N/A.


For further testing:

I commented out the variable on /etc/enviroment and found that the flicker
doesn't trigger if there's a window of Konsole, Dolphin, System Settings or
Kate in the same virtual desktop, even if they're all behind the
Chromium/Electron app behind. As soon as I minimize all of them or move them to
another virtual desktop, leaving only the Chromium window, I can reproduce the
flicker again easily. Seems like Qt windows avoid the overlays to either kick
in or kick out, I'm not sure, and thus the "default" background seems to be the
darker one (as per the video).

I've attached what drm_info prints when the background is lighter and the
background is darker as you can see in the video. You may run a diff and find
that some values besides the IDs are different from each other. (I used the git
version of drm_info).

Additionally, besides pure Chromium window, this can also be reproduced with
webapps such as Proton Mail (that also run on Chromium), and it doesn't seem to
happen with Steam and Ferdium even when both are Electron apps.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to