[savage] glxinfo crashed with SIGSEGV

[Daniel Che]

The bug happens when i start glxinfo in terminal.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: mesa-utils 7.8.2-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Sun Sep 19 04:53:53 2010
ExecutablePath: /usr/bin/glxinfo
GdmLog2: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100918)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 13fe:1f00 Kingston Technology Company Inc. DataTraveler 2.0 4GB Flash Drive / Patriot Xporter 32GB (PEF32GUSB) Flash Drive
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ECS M925
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- locale=pt_BR console-setup/layoutcode?=br console-setup/modelcode?=abnt2
ProcCmdline: glxinfo
ProcEnviron:
 SHELL=/bin/bash
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x82db33: mov 0x14(%eax),%edx
 PC (0x0082db33) ok
 source "0x14(%eax)" (0x00000014) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mesa
StacktraceTop:
 ?? () from /usr/lib/mesa/libGL.so.1
 ?? () from /usr/lib/dri/savage_dri.so
 ?? () from /usr/lib/dri/savage_dri.so
 ?? () from /usr/lib/dri/savage_dri.so
 ?? () from /usr/lib/dri/savage_dri.so
Title: glxinfo crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:3453): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (bluetooth-applet:3450): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
 (nautilus:3457): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
dmi.bios.date: 04/02/01
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 07.00T
dmi.board.name: M925
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.asset.tag: 0123ABC
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr07.00T:bd04/02/01:svnECS:pnM925:pvr1.0:rvnECS:rnM925:rvr1.0:cvnECS:ct3:cvr1.0:
dmi.product.name: M925
dmi.product.version: 1.0
dmi.sys.vendor: ECS
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-22-generic

[Apport retracing service (apport)]

StacktraceTop:
 __glXDRIGetDrawableInfo (drawable=0x8a3b488,
 __driUtilUpdateDrawableInfo (pdp=0x8a3b488)
 savageGetLock (imesa=0x88ff888, flags=0)
 savageFlushCmdBuf (imesa=0x88ff888, discard=1 '\001')
 savageDestroyContext (driContextPriv=0x8900870)

[bugbot (bugbot)]

Hey Daniel,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[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.