Ubuntu
xscreensaver package

[nvidia] glknots crashed with SIGSEGV

Bug #208519 reported by sipickles on 2008-03-28

This bug report is a duplicate of: Bug #110125: [nvidia] GL xscreensavers crashed. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	xscreensaver (Ubuntu)	Incomplete	Medium	Unassigned

Bug Description

Binary package hint: xscreensaver

Crashed immediately after reboot on Hardy Upgrade:

Description: Ubuntu hardy (development branch)
Release: 8.04

ProblemType: Crash
Architecture: i386
Date: Fri Mar 28 20:01:44 2008
Disassembly: 0x40ea1968:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/xscreensaver/glknots
NonfreeKernelModules: nvidia
Package: xscreensaver-gl 5.04-2ubuntu2
PackageArchitecture: i386
ProcCmdline: glknots -root
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/lib/gnome-screensaver/gnome-screensaver:/usr/lib/xscreensaver:/usr/lib/xscreensaver
LANG=en_GB.UTF-8
Signal: 11
SourcePackage: xscreensaver
Stacktrace:
#0 0x40ea1968 in ?? ()
#1 0xb7bd828d in ?? ()
#2 0xbff98ab8 in ?? ()
#3 0xb7bd7e70 in ?? ()
#4 0x00000000 in ?? ()
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
ThreadStacktrace:

Title: glknots crashed with SIGSEGV
Uname: Linux 2.6.24-12-386 i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags:

Revision history for this message

sipickles (sipickles) wrote on 2008-03-28:

Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (4.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (667 bytes, text/plain; charset="utf-8")
Registers.txt Edit (505 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2008-03-28: Symbolic stack trace

Stacktrace.txt (retraced) Edit (119 bytes, text/plain)

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2008-04-02: Re: glknots crashed with SIGSEGV

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.