glxgears crashed with SIGSEGV in _fini()

Bug #542727 reported by Kernel-1
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
X.Org X server
New
Undecided
Unassigned
mesa (Debian)
New
Undecided
Unassigned
mesa (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

sigsev in _fini()

 (happened just prior to closing glxgears)

ProblemType: Crash
Architecture: amd64
Date: Sat Mar 20 15:38:09 2010
DistroRelease: Ubuntu 10.04
DkmsStatus: nvidia-current, 195.36.15, 2.6.32-16-generic, x86_64: installed
ExecutablePath: /usr/bin/glxgears
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
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
MachineType: Gigabyte Technology Co., Ltd. P35-DS3R
Package: mesa-utils 7.7-4ubuntu1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic root=UUID=c1fe7430-8d29-41de-81b4-50e08bdd798a ro quiet splash
ProcCmdline: glxgears
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x7f047a171a80: mov (%rax),%r12d
 PC (0x7f047a171a80) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%r12d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mesa
StacktraceTop:
 ?? () from /usr/lib/nvidia-current/libGL.so.1
 _fini () from /usr/lib/nvidia-current/libGL.so.1
 ?? () from /lib64/ld-linux-x86-64.so.2
 exit () from /lib/libc.so.6
 _XDefaultIOError () from /usr/lib/libX11.so.6
Title: glxgears crashed with SIGSEGV in _fini()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1262): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-terminal:1822): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
 (gnome-panel:1265): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
 (gnome-terminal:13053): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
dmi.bios.date: 06/19/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F13
dmi.board.name: P35-DS3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P35-DS3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-16-generic

Revision history for this message
Kernel-1 (oligofrenolog) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /usr/lib/nvidia-current/libGL.so.1
 _fini () from /usr/lib/nvidia-current/libGL.so.1
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Bryce Harrington (bryce)
tags: added: crash
Changed in mesa (Ubuntu):
status: New → Confirmed
Revision history for this message
Robert Hooker (sarvatt) wrote :

Your logs don't match up, they show you using nouveau yet its crashing with nvidia's libGL which is to be expected. Also your xorg.conf is for the nvidia proprietary drivers but that has not been used yet. Have you not rebooted after activating nvidia-current?

Changed in mesa (Ubuntu):
status: Confirmed → Incomplete
Bryce Harrington (bryce)
visibility: private → public
Bryce Harrington (bryce)
Changed in xorg-server:
importance: Unknown → Undecided
status: Unknown → New
Changed in mesa (Debian):
importance: Unknown → Undecided
status: Unknown → New
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.