xscreensaver Atunnel crashed with SIGSEGV

Bug #223435 reported by Tsondo
6
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Medium
Unassigned

Bug Description

Since this is my first bug report I did not look closely at the details. It apparently occured while updgading Ubuntu to 8.04, but I am not sure whether the bug happened then or whether this reporting tool is new and picked up an old crash I didnt know about. The reporting tool seems to require in depth knowledge that I simply do not have. If what is needed is not already in the report I have nothing more to offer.

ProblemType: Crash
Architecture: i386
Date: Mon Apr 28 00:20:16 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/xscreensaver/atunnel
NonfreeKernelModules: fglrx
Package: xscreensaver-gl 5.04-4ubuntu1
PackageArchitecture: i386
ProcCmdline: atunnel -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_US.UTF-8
Signal: 11
SourcePackage: xscreensaver
StacktraceTop:
 ?? () from /usr/lib/dri/fglrx_dri.so
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: atunnel crashed with SIGSEGV
Uname: Linux 2.6.24-16-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Tsondo (tsondo) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /usr/lib/dri/fglrx_dri.so
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

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.