I'm confused... so, you're essentially saying it's the fault of the
application, choosing the wrong visual? So what exactly changed and why
did it change and how is this "better" than before? I don't think the
visual with a compositable alpha channel should be chosen as default by
accident. (?) The
Googling around I found those recent two patches:
http://patchwork.freedesktop.org/patch/20458/
http://patchwork.freedesktop.org/patch/20464/
[Mesa-dev] glx: Fix the default values for GLXFBConfig attributes
[Mesa-dev] glx: Fix the GLXFBConfig attrib sort priorities
Mightbe related...
--
You r
Ok, so this proves my point. The unwanted "change" somewhere in the X/GL
stack is that the visual with the composite alpha channels is now
"accidentally" chosen by default whereas the applications expect the
alpha channel to be ignored.
I just decompiled Minecraft and hacked the calls to glClearCo
I have a possible culprit.
The composite extension requires premultiplied alpha data when
compositing images with alpha. So (0, 0, 0, 0) means fully transparent
and (0, 0, 0, 1) means solid black. This is consistent with what I am
seeing with the login window.
I found some example code with walks
Note that you can find the GL setup code here:
https://github.com/LWJGL/lwjgl/blob/master/src/native/linux/opengl/org_lwjgl_opengl_Display.c
somewhere around Java_org_lwjgl_opengl_LinuxDisplay_nCreateWindow
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I did some bit of uneducated debugging.
It seems there is something going on with the GL/GLX and alpha bits.
The LWJGL code is creating a GLX window for its content.
I noticed that the screen displaying the logo on startup was entirely
translucent, without the 256x256 block in the lower left cor
PS: I tried the latest git version of xf86-video-intel (that includes
that fix "Avoid promoting region-to-whole migration and discarding
damage" by Chris) - same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
I'm not a Ubuntu user myself, but seeing the exact same issue on my
Gentoo (unstable) system. I've seen it before the last couple of months,
but only occasionally, typically after a long-running X session and it
usually went away with an X server restart. For a bit over a week now
the problem has b
