glxinfo crashed with SIGSEGV in __libc_start_main()

[Walt Corey]

I don't even know what this does but it crashed right after I started vncserver -geometry 1400x900

ProblemType: Crash
Architecture: amd64
Date: Mon Nov 2 15:54:11 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/glxinfo
MachineType: Dell Inc. Precision WorkStation 490
NonfreeKernelModules: vmnet vmci vmmon nvidia
Package: mesa-utils 7.6.0-1ubuntu4
ProcCmdLine: root=UUID=1f2f32ff-3911-4a5b-a42b-ac03e6a14f9c ro quiet splash
ProcCmdline: /usr/bin/glxinfo
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu7
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SegvAnalysis:
 Segfault happened at: 0x403172: mov (%r14),%rbp
 PC (0x00403172) ok
 source "(%r14)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mesa
StacktraceTop:
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
 ?? ()
 ?? ()
Title: glxinfo crashed with SIGSEGV in __libc_start_main()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev users video
Xrandr:
 Error: command ['xrandr', '--verbose'] failed with exit code 1: Xlib: extension "RANDR" missing on display ":0.0".
 RandR extension missing
dmi.bios.date: 08/20/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0GU083
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd08/20/2007:svnDellInc.:pnPrecisionWorkStation490:pvr:rvnDellInc.:rn0GU083:rvrA00:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation 490
dmi.sys.vendor: Dell Inc.
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.31-14-generic

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #438730, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.