glxinfo crashed with SIGSEGV in __libc_start_main()

StacktraceTop:

Confirming this issue as my report was marked as a dupe of this one. glxinfo appears to run automatically in the background at some stage (during startup or restricted drivers manager?) which causes this crash. It's also reproducible by just running the glxinfo command. 3D is broken due to nvidia/something not liking the xorg.conf, but in any case, glxinfo shouldn't be crashing.

The reason why my compiz/glxinfo wouldn't work is that the symlink to /usr/lib/xorg/modules/extensions/libglx.so was wrong. It was linked to an old and non-existant library installed in Hardy. I removed the symlink and created it again with the latest libglx.so.177.76 library. Now everything workes again.

This is still a problem on Jaunty with mesa-utils 7.3~rc3-1ubuntu1 . I'm not sure what graphics driver I'm really using since I've tried nv, nvidia and nouveau now. Changing sourcepackage to mesa since this crash is occurring in glxinfo.

I just had it with Jaunty as well. Entered dupe for logs and such if they are needed.

I receive the error also after upgrading to Jaunty. \

Received this error using nvidia 180.35 and trying to replace metacity with compiz.

Received this error with jaunty and I have no idea what to do.

I still have this bug with the latest nvidia-glx-180. In /usr/lib/xorg/modules/extensions the symlink to libglx.so.180.44 is made, but in /usr/lib/xorg/modules/ it still links to the old module /usr/lib/xorg/modules/extensions/libglx.so.180.37 which doesn´t exist anymore.

Kim, see bug #354484
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/354484

Thanks Graham. I noticed that on my other Ubuntu machine there is no link to libglx in /usr/lib/xorg/modules. So today I removed this link and with only the link in /usr/lib/xorg/modules/extensions it works perfectly.

Problem still exists with current Karmic. This looks similar to bug 256021.

This is fixed on karmic now, fix was released in mesa 7.4.1.

http://cgit.freedesktop.org/mesa/mesa/commit/?h=mesa_7_4_branch&id=d2f67910629d7f9b00ba127f2e869f02a72306d2

Accepted mesa into jaunty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

The patch in comment #15 is clearly correct, it's just a null pointer check immediately before dereference which should have no chance of regression. It has been 2 months since this was accepted in jaunty-proposed, which ought to be plenty of time for testing! It would be nice to get this cleared out, since we have other mesa srus needing attention (e.g. #347569)

This bug was fixed in the package mesa - 7.4-0ubuntu3.2

---------------
mesa (7.4-0ubuntu3.2) jaunty-proposed; urgency=low

  * Add 107_glxinfo_segfault.patch. Adds a null pointer check in
    glXGetFBConfigs(), which fixes segfaults in glxinfo most commonly
    seen when nvidia binary drivers are present. (LP: #256021, #257600)

 -- Robert Hooker (Sarvatt) <email address hidden> Wed, 24 Jun 2009 21:40:45 -0400