[kwin] [Bug 355569] kwin_wayland master doesn't display anything on the framebuffer

[Martin Gräßlin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=355569

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kwin
   ||/3247382752071f77b78fb71457
   ||2f7d31f148e47a
   Version Fixed In||5.5.1
 Status|UNCONFIRMED |RESOLVED

--- Comment #18 from Martin Gräßlin  ---
Git commit 3247382752071f77b78fb714572f7d31f148e47a by Martin Gräßlin, on
behalf of Nerdopolis Turfwalker.
Committed on 15/12/2015 at 12:05.
Pushed by graesslin into branch 'Plasma/5.5'.

[backends/fbdev] Support framebuffers with different color depths

Support more framebuffer color depths

REVIEW: 126262
FIXED-IN: 5.5.1

M  +34   -1backends/fbdev/fb_backend.cpp

http://commits.kde.org/kwin/3247382752071f77b78fb714572f7d31f148e47a

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 355569] kwin_wayland master doesn't display anything on the framebuffer

[via KDE Bugzilla]

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 tests I had it doing, it was selecting
the 24 bit format...
...Is this a possible bug in the Intel driver?...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 355569] kwin_wayland master doesn't display anything on the framebuffer

[via KDE Bugzilla]

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.

[kwin] [Bug 355569] kwin_wayland master doesn't display anything on the framebuffer

[via KDE Bugzilla]

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->bitsPerPixel();


in QEMU:
Bytes Per Line: 3072
Buffer Size: 2359296
Bits Per Pixel: 24

It also seems that that qpainter debug message happens with:
QPainter p(_backBuffer);
judging by the debug lines I threw into it.

On intel box
Bytes Per Line: 5120
Buffer Size: 4096000
Bits Per Pixel: 32

...and now for some reason this time after realizing I should set my
Framebuffer to be 32 bits, it worked in QEMU too (I must have been mistaken
somewhere, as I thought setting the framebuffer to 32 bits in QEMU still failed
the first time...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 355569] kwin_wayland master doesn't display anything on the framebuffer

[via KDE Bugzilla]

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 on QEMU...   
...It's usually breaking some things with LLVM, causing apps to crash, so it
could be unrelated...  
So how's a good way for me to test why (or if) memory mapping for the qimage
would be failing under just QEMU, only when using the framebuffer backend

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 355569] kwin_wayland master doesn't display anything on the framebuffer

[via KDE Bugzilla]

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: "   << m_red.length;
qCWarning(KWIN_FB) << "Red Offset: "   << m_red.offset;
qCWarning(KWIN_FB) << "Green Length: " << m_green.length;
qCWarning(KWIN_FB) << "Green Offset: " << m_green.offset;
qCWarning(KWIN_FB) << "Blue Length: "  << m_blue.length;
qCWarning(KWIN_FB) << "Blue Offset: "  << m_blue.offset;
in FramebufferBackend::queryScreenInfo()

to see if a difference there could be the cause of the late:
   QPainter::begin Paint device returned engine == 0, type 3
which occurs sometime after Xwayland starts, which that line does not appear on
my physical box when using the framebuffer at least. (if that even is related
to the issue)

and they all seem to be correct for what FramebufferBackend::imageFormat()
tries to match for in QEMU...
Alpha Length:0
Alpha Offset:0
Red Length: 8
Red Offset: 16
Green Length: 8
Green Offset: 8
Blue Length: 8
Blue Offset :0

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 355569] kwin_wayland master doesn't display anything on the framebuffer

[Martin Gräßlin via KDE Bugzilla]

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.