https://bugs.kde.org/show_bug.cgi?id=500402
Bug ID: 500402
Summary: Excess CPU usage from png_read_image
Classification: Plasma
Product: kwin
Version: 6.3.0
Platform: Other
OS: Linux
Status: REPORTED
S
https://bugs.kde.org/show_bug.cgi?id=492300
--- Comment #10 from derp ---
hm, are you saying the corruption would trigger for every app where the
application lies about effective opaque region? I think that would make sense,
and there's no way to reasonably protect against that without sca
https://bugs.kde.org/show_bug.cgi?id=492300
--- Comment #8 from derp ---
some investigation would be nice, if not for Firefox, at least for the fact
that the transparent area renders garbage breaking damage/buffer age tracking.
if Firefox really sends wrong data (even though I see nothing
https://bugs.kde.org/show_bug.cgi?id=492300
--- Comment #5 from derp ---
Created attachment 173029
--> https://bugs.kde.org/attachment.cgi?id=173029&action=edit
second variant of the bug #2
and the screenshout of bugs happening in transparent area
to above question: no, outside
https://bugs.kde.org/show_bug.cgi?id=492300
--- Comment #4 from derp ---
Created attachment 173028
--> https://bugs.kde.org/attachment.cgi?id=173028&action=edit
second variant of the bug
A second "variant" of the bug. Moving cursor over the bugged transparent area
results in
https://bugs.kde.org/show_bug.cgi?id=492300
--- Comment #2 from derp ---
WAYLAND_DEBUG=1 ./firefox may be used to print Wayland calls, and the
suspicious API calls that Firefox uses are (in no specific order):
[3175848.494] {Default Queue} -> wl_subcompositor#38.get_subsurface(new
https://bugs.kde.org/show_bug.cgi?id=492300
--- Comment #1 from derp ---
Surface hierarchy at the time of the screenshot:
Buffers
- wl_buffer@47 shm, width: 32, height: 32, format: 0
https://bugs.kde.org/show_bug.cgi?id=492300
Bug ID: 492300
Summary: kwin_wayland misplaces Firefox subsurface
Classification: Plasma
Product: kwin
Version: master
Platform: Other
OS: Linux
Status: REPORTED
