Bug 16718 - No sane visuals are reported, "couldn't find RGB GLX visual"
Summary: No sane visuals are reported, "couldn't find RGB GLX visual"
Status: RESOLVED DUPLICATE of bug 13358
Alias: None
Product: Mesa
Classification: Unclassified
Component: GLX (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-15 01:46 UTC by Guillaume Melquiond
Modified: 2009-08-24 12:30 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Guillaume Melquiond 2008-07-15 01:46:25 UTC
I have a working system with xorg 1.4.2, drm 2.3.1, and mesa 7.0.3 (Debian packages). I have then tried to use mesa git, without pulling the other sources.

glxinfo from git still works fine, but neither the old glxinfo nor glxgears from git (!) work. This is what the old glxinfo reports:

name of display: :0.0
libGL: XF86DRIGetClientDriverName: 1.9.0 i915 (screen 0)
libGL: OpenDriver: trying .../mesa/lib/i915_dri.so
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 4, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 4, (OK)
drmOpenByBusid: drmOpenMinor returns 4
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
Error: couldn't find RGB GLX visual

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
0x23 24 tc  1  0  0 c  .  .  0  0  0  0  0  0  0  0  0  0  0  0 0 None
0x24 24 tc  1  0  0 c  .  .  0  0  0  0  0  0  0  0  0  0  0  0 0 None
...

I don't know if this is a bug, or if this an incompatibility because I was not using drm and server from git. If it is an intended incompatibility, it may be worth detecting it at configure time or displaying a better warning at runtime. In particular, it is quite surprising that glxinfo from git works while glxgears from git does not.
Comment 1 Guillaume Melquiond 2008-07-15 08:23:46 UTC
Actually, it's a bit worse than what I thought. The very first run of the old glxinfo works fine, it is only the later runs that are going wrong. So it seems there is some persistent data somewhere that are broken by mesa git.

Note that applications using the shared libraries of old mesa are still running fine, even after the failure of mesa git. It is the applications that are using the libraries of mesa git that work only once (except for the strange case of glxinfo from git).

To summarize, when run in the following order, I get

1. glxinfo "old" with mesa "old" OK
2. glxinfo "old" with mesa "git" OK
3. glxinfo "old" with mesa "git" FAIL
4. glxinfo "git" with mesa "git" OK
5. glxgear "git" with mesa "git" FAIL
6. glxgear "git" with mesa "old" OK
Comment 2 Guillaume Melquiond 2008-07-15 08:56:01 UTC
Sorry for the spam, I'm not even sure it is related. But I was trying to understand why the glxinfo from git was still working properly, so I looked through the recent patches to the tools. As a consequence, I noticed some strange code at line 433:

      if (!visinfo)
         configs = glXChooseFBConfig(dpy, scrnum, fbAttribSingle, &nConfigs);
      if (!visinfo)
         configs = glXChooseFBConfig(dpy, scrnum, fbAttribDouble, &nConfigs);

It seems to me that the first assignment is some dead code. Moreover, since it is followed by Xfree(configs), I suppose this is also a memory leak.
Comment 3 Michel Dänzer 2008-07-15 10:17:28 UTC
(In reply to comment #1)
> The very first run of the old glxinfo works fine, it is only the later runs
> that are going wrong.

Sounds like bug 13358 (not sure why it was resolved as fixed). Is this on x86_64 as well?
Comment 4 Guillaume Melquiond 2008-07-15 11:26:50 UTC
Yes, it is on x86-64 as well. And it does indeed sound like the same bug, especially since the reporter said that "if I install mesa 7.0 I can get opengl working again without restarting the X server", which I'm experiencing as well. It may be worth reopening the first report and marking this one as a duplicate then.
Comment 5 Michel Dänzer 2008-07-15 23:45:18 UTC

*** This bug has been marked as a duplicate of bug 13358 ***
Comment 6 Adam Jackson 2009-08-24 12:30:38 UTC
Mass version move, cvs -> git


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.