Ubuntu
xscreensaver package

[fglrx] antinspect crashed with SIGSEGV

Bug #178997 reported by Jaakan Shorter on 2007-12-28

This bug report is a duplicate of: Bug #181121: OpenGL screensavers cause crashes. Edit Remove

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

Bug Description

Binary package hint: xscreensaver

I was just going through my screen savers

ProblemType: Crash
Architecture: amd64
Date: Thu Dec 27 21:57:15 2007
Disassembly: 0x2b67884a5d1e:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/xscreensaver/antinspect
NonfreeKernelModules: fglrx
Package: xscreensaver-gl 5.04-1ubuntu1
PackageArchitecture: amd64
ProcCmdline: antinspect -root
ProcCwd: /home/jaakan
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_US.UTF-8
Signal: 11
SourcePackage: xscreensaver
Stacktrace: #0 0x00002b67884a5d1e in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: antinspect crashed with SIGSEGV
Uname: Linux jms1000 2.6.24-2-generic #1 SMP Thu Dec 20 17:58:55 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner video

Tags:

Revision history for this message

Jaakan Shorter (jaakanshorter) wrote on 2007-12-28:

Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (8.8 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (683 bytes, text/plain; charset="utf-8")
Registers.txt Edit (1003 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2007-12-28: Symbolic stack trace

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

StacktraceTop:?? ()

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2008-03-28: Re: antinspect 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.