https://bugs.kde.org/show_bug.cgi?id=355569
Martin Gräßlin changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=355569
--- Comment #17 from bluescreen_aven...@verizon.net ---
Well, I know why that patch fixed it on QEMU, but broke it on Intel, the
virtual framebuffer device reports itself as 32 bits, but the alpha length, and
the alpha offset are both 0, so with the
https://bugs.kde.org/show_bug.cgi?id=355569
--- Comment #16 from bluescreen_aven...@verizon.net ---
For this I attempted to create https://git.reviewboard.kde.org/r/126262/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=355569
--- Comment #15 from bluescreen_aven...@verizon.net ---
I added lines
+qWarning() << "Bytes Per Line: " << backend->bytesPerLine();
+qWarning() << "Buffer Size: " << backend->bufferSize();
+qWarning() << "Bits Per Pixel: " <<
https://bugs.kde.org/show_bug.cgi?id=355569
--- Comment #13 from bluescreen_aven...@verizon.net ---
How should I go about testing that? I have realized that there are some issues
with the way libvirt is passing CPU features, but It seems that kwin is working
under the Wayland backend under Weston
https://bugs.kde.org/show_bug.cgi?id=355569
--- Comment #11 from bluescreen_aven...@verizon.net ---
I tried to add the lines
qCWarning(KWIN_FB) << "Alpha Length: " << m_alpha.length;
qCWarning(KWIN_FB) << "Alpha Offset: " << m_alpha.offset;
qCWarning(KWIN_FB) << "Red Length: "
https://bugs.kde.org/show_bug.cgi?id=355569
--- Comment #12 from Martin Gräßlin ---
hmm, maybe the memory mapping to a QImage fails?
--
You are receiving this mail because:
You are watching all bug changes.