Compiz FBConfig selection criteria
jajones at nvidia.com
Tue Nov 20 11:04:16 PST 2007
At some point I think I fixed exactly the bug you describe in compiz. The
GLX_BIND_TO_MIPMAP_TEXTURE_EXT configs should be preferred but not required.
If one isn't found, a flag should be set disabling mip-mapping when using
that config. I would recommend looking through the FBConfig selection code
and ensuring it still works that way.
On 11/19/07 11:41 PM, "Ben Gamari" <ben at mw0.ath.cx> wrote:
> Yes, I had seen that although I don't think it is the cause of my
> problem in this case.
> Instead, it seems that compiz is assuming my GLFBConfigs should have the
> GLX_BIND_TO_MIPMAP_TEXTURE_EXT attribute because I have
> GL_EXT_framebuffer_object. I still don't understand why this is the
> case but oh well. Any insight anyone?
> - Ben
> On Tue, 2007-11-20 at 08:16 +0100, Michel Dänzer wrote:
>> On Mon, 2007-11-19 at 21:34 -0500, Ben Gamari wrote:
>>> Recently I (perhaps stupidly) decided to try using git master of
>>> xf86-video-intel, drm, xorg-server, and mesa. Unfortunately, something
>>> in this update broke my fbconfigs badly, causing compiz to give me the
>>> ben at mercury ~ $ LIBGL_ALWAYS_INDIRECT=1 compiz --replace ccp
>>> compiz (core) - Fatal: No GLXFBConfig for default depth, this isn't
>>> going to work.
>>> compiz (core) - Error: Failed to manage screen: 0
>>> compiz (core) - Fatal: No manageable screens found on display :0.0
>> Beware of https://bugs.freedesktop.org/show_bug.cgi?id=9264 .
> xorg mailing list
> xorg at lists.freedesktop.org
More information about the xorg