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
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
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!
** Also affects: mesa (Ubuntu Jaunty)
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_branchid=d2f67910629d7f9b00ba127f2e869f02a72306d2
** Changed in: mesa (Ubuntu)
Status: Triaged = Fix Released
--
glxinfo crashed with SIGSEGV in __libc_start_main()
Problem still exists with current Karmic. This looks similar to bug
256021.
--
glxinfo crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/257600
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in ubuntu.
5 matches
Mail list logo
