[nvidia-glx-legacy] glxinfo crashed with SIGSEGV

Bug #132432 reported by Marco Rodrigues
10
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-180 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I run it on console.. gutsy tribe-4

ProblemType: Crash
Architecture: i386
Date: Sat Aug 11 22:47:10 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/glxinfo
NonfreeKernelModules: nvidia cdrom
Package: mesa-utils 7.0.0-0ubuntu3
PackageArchitecture: i386
ProcCmdline: /usr/bin/glxinfo
ProcCwd: /home/kmos
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.ISO-8859-1
 SHELL=/bin/bash
Signal: 11
SourcePackage: mesa
StacktraceTop:
 ?? () from /usr/lib/libGL.so.1
 ?? ()
 ?? () from /usr/lib/libGL.so.1
 ?? ()
 ?? () from /usr/lib/libGL.so.1
Title: glxinfo crashed with SIGSEGV
Uname: Linux localhost 2.6.22-9-generic #1 SMP Fri Aug 3 00:50:37 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
Marco Rodrigues (gothicx) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /usr/lib/libGL.so.1
?? ()
?? () from /usr/lib/libGL.so.1
?? ()
?? () from /usr/lib/libGL.so.1

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Tormod Volden (tormodvolden) wrote : Re: glxinfo crashed with SIGSEGV

Thanks for the bug report. Can you please attach /etc/X11/xorg.conf and /var/log/Xorg.0.log?

Changed in mesa:
assignee: nobody → tormodvolden
status: New → Incomplete
Revision history for this message
Marco Rodrigues (gothicx) wrote :
Revision history for this message
Marco Rodrigues (gothicx) wrote :
description: updated
Revision history for this message
Marco Rodrigues (gothicx) wrote :

Now with Tribe-5, it runs but after a while it seg fault.

kmos@bash:~$ glxinfo
name of display: :0.0
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual
...
....
Segmentation fault (core dumped)

Changed in mesa:
assignee: tormodvolden → nobody
status: Incomplete → Confirmed
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote : Re: [nvidia] glxinfo crashed with SIGSEGV

Broken GL when using composite with nvidia-glx-legacy is a known bug (see Bug #124913 and https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia ).

Marco:
How did you enable the legacy drivers - did you use restricted-manager?

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Setting back to New and punting from mesa -> linux-restricted-modules-2.6.22 .

Changed in mesa:
status: Confirmed → New
Revision history for this message
Marco Rodrigues (gothicx) wrote :

Yes, I use restriced-manager =)

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Punting from linux-restricted-modules-2.6.22 -> restricted-manager .

Changed in restricted-manager:
importance: Undecided → Medium
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

We are wondering if this is still an issue. Can you try it with the latest Ubuntu release? Thanks in advance.

Changed in restricted-manager:
status: New → Incomplete
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Hadmut Danisch (hadmut) wrote :

Hi,

it is still an issue, at least on my computer (ubuntu jaunty, AMD64). I have a

00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev a2)

graphics card, and although I have loaded nvidia-glx-180 (which loads the glx extension), glx still does not work:

% glxinfo
name of display: :0.0
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual or fbconfig

Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
3 GLXFBConfigs:
   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
----------------------------------------------------------------------
Segmentation fault

Other applications like compiz or googleearth complain about missing glx extensions as well (googleearth crashes with segmentation fault too).

affects: restricted-manager (Ubuntu) → nvidia-graphics-drivers-180 (Ubuntu)
Revision history for this message
Bryce Harrington (bryce) wrote :

I've posted a new version of the -nvidia driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get nvidia-graphics-drivers-180 - 185.18.14 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Marco Rodrigues (gothicx) wrote :

For me it works fine again with jaunty, but I didn't install the version from PPA.

http://pastebin.com/f104e549

Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks for letting us know the issue is resolved.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.