https://bugs.kde.org/show_bug.cgi?id=387159
Bug ID: 387159
Summary: Mesa requires explicit "don't care"(or "true") to list
srgb capable fbconfigs
Product: kwin
Version: git master
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: platform-x11-standalone
Assignee: kwin-bugs-n...@kde.org
Reporter: pie...@pirsoft.de
Target Milestone: ---
Created attachment 108987
--> https://bugs.kde.org/attachment.cgi?id=108987&action=edit
Patch adding GLX_FRAMEBUFFER_SRGB_CAPABLE_ARB attribute
On systems where the only ARGB visual/fbconfig combination is sRGB capable and
which use mesa after 17.2, kwin will not render windows using an ARGB visual.
Steps to Reproduce:
1) Start an application that chooses ARGB visuals for some of its windows
For example, QT4 apps may choose the ARGB visual for their menus or
drop-downs. (They probably should not, but they do here.)
2) Make the application show such a window
Actual Results:
The window is invisible
Expected Results:
The window should be visible
Build Date & Platform:
Using the 5.11.3 release on a gentoo system. Inspection of the git repository
shows bug still present.
Mesa 17.3 branch. The commit changing mesa behaviour went into 17.2.
Xserver 1.19.5
Additional Information:
Commit 6e06e281c6ee342276d087ed4ee4a442626e433a in mesa changed the behaviour
of glXChooseFBConfig so that it can filter for sRGB capable fbconfigs. By
default, it will filter out all sRGB capable fbconfigs. The only ARGB
visual/fbconfig combination on my system is sRGB capable, so kwin never finds
it when an application uses the ARGB visual on a window, thus it will not be
able to render the windows content.
I solved this problem by adding
GLX_FRAMEBUFFER_SRGB_CAPABLE_ARB, int(GLX_DONT_CARE)
to the attribute list of glXChooseFBConfig,
plugins/platforms/x11/standalone/glxbackend.cpp, about line 550. It may be more
appropriate to use GLX_FRAMEBUFFER_SRGB_CAPABLE_EXT(which is the same value).
--
You are receiving this mail because:
You are watching all bug changes.
