https://bugs.kde.org/show_bug.cgi?id=492300
Nate Graham changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/fram |
|eworks/kdbusaddons/-/commit |
https://bugs.kde.org/show_bug.cgi?id=492300
Nate Graham changed:
What|Removed |Added
Version Fixed In|6.7 |
Resolution|FIXED |
https://bugs.kde.org/show_bug.cgi?id=492300
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=492300
David Edmundson changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/fram
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 scanning p
https://bugs.kde.org/show_bug.cgi?id=492300
--- Comment #9 from Vlad Zahorodnii ---
> the transparent area renders garbage breaking damage/buffer age tracking
ff sets the opaque region for the main surface (it mainly contains the client
side drop shadow). if a subsurface is translucent or not co
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 suspici
https://bugs.kde.org/show_bug.cgi?id=492300
Vlad Zahorodnii changed:
What|Removed |Added
Resolution|--- |DOWNSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=492300
--- Comment #6 from Vlad Zahorodnii ---
gfx.webrender.compositor.force-enabled used to have bugs last time I tested it
and I won't be surprised if those issues still persist up to this day because
the clients often get subsurface wrong way.
> KWin does
https://bugs.kde.org/show_bug.cgi?id=492300
David Edmundson changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
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 of the overvie
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 duplicate visible
https://bugs.kde.org/show_bug.cgi?id=492300
David Edmundson changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
CC|
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 id
wl_subsurf
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
- wl_buf
15 matches
Mail list logo
