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 test
https://bugs.kde.org/show_bug.cgi?id=355569
bluescreen_aven...@verizon.net changed:
What|Removed |Added
Component|general |backend-fbdev
--
You are recei
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: " << backend->bitsPer
https://bugs.kde.org/show_bug.cgi?id=355569
--- Comment #14 from Martin Gräßlin ---
The QImage is created in scene_qpainter_fb_backend.cpp in the ctor directly.
Maybe try add debug output there. What striked me as odd is the debug message
about the paint device which could indicate that something
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 #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.
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 #10 from bluescreen_aven...@verizon.net ---
OK, Seems on the qemu box, the framebuffer backend behaves the same trying to
access /dev/fb0, according to the log,
It tries to access the Framebuffer device with logind, fails, but then is
success
https://bugs.kde.org/show_bug.cgi?id=355569
--- Comment #9 from Martin Gräßlin ---
> how do I get kwin to output the debug output for the framebuffer backend,
> with qcdebug lines,
you need to modify: ~/.config/QtProject/qtlogging.ini
It should look something like:
[Rules]
kwin_core=true
kwin
https://bugs.kde.org/show_bug.cgi?id=355569
--- Comment #8 from bluescreen_aven...@verizon.net ---
and I meant the qemu where nothing draws (the text in the TTY freezes), vs the
physical Intel box where I force it to use the framebuffer, and it works. Sorry
about the lack of clarity in the first c
https://bugs.kde.org/show_bug.cgi?id=355569
--- Comment #7 from bluescreen_aven...@verizon.net ---
It seems comparing the strace output around the time kwin tries to access
/dev/fb0 is similar, so I'm not sure where it is failing... ...how do I get
kwin to output the debug output for the framebuff
13 matches
Mail list logo
