https://bugs.kde.org/show_bug.cgi?id=393101
--- Comment #6 from Allan Sandfeld ---
Okay. I knew X11 was closed for development. I only reported it after I noted
the lack of some of the underlying things such as image format in Screen, and
detection of window format. The pixel corruption wouldn't
https://bugs.kde.org/show_bug.cgi?id=393101
--- Comment #5 from Martin Flöser ---
(In reply to Allan Sandfeld from comment #4)
> So not going to fix it for wayland either?
Your bug report was about X11 and I answered for that. There are quite some
differences between Wayland and X11 in this area
https://bugs.kde.org/show_bug.cgi?id=393101
--- Comment #4 from Allan Sandfeld ---
So not going to fix it for wayland either? The underlying problem is the same,
and you will need the underlying fixes anyway in the near future to support
HDR. You need to be aware of the screen format and the form
https://bugs.kde.org/show_bug.cgi?id=393101
Martin Flöser changed:
What|Removed |Added
Flags||Wayland-, X11+
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=393101
--- Comment #2 from Allan Sandfeld ---
Created attachment 112001
--> https://bugs.kde.org/attachment.cgi?id=112001&action=edit
screenshot showing bad window decoration
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393101
--- Comment #1 from Allan Sandfeld ---
Btw. An easy way of seeing the corruption without changing Qt is launching
Chromium. It will render its internal corrupt because GTK has terrible support
for the same, but the window decoration by Kwin will also be
