busyspheres crashed with SIGSEGV in exit()

Bug #344608 reported by Dylan Taylor
8
Affects Status Importance Assigned to Milestone
fglrx-installer (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: rss-glx

Description: Ubuntu jaunty (development branch)
Release: 9.04
xscreensaver:
  Installed: (none)
  Candidate: 5.07-0ubuntu3
  Version table:
     5.07-0ubuntu3 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
rss-glx:
  Installed: 0.8.2-1ubuntu3
  Candidate: 0.8.2-1ubuntu3
  Version table:
 *** 0.8.2-1ubuntu3 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/xscreensaver/busyspheres
NonfreeKernelModules: fglrx
Package: rss-glx 0.8.2-1ubuntu3
ProcCmdline: busyspheres -r
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: rss-glx
StacktraceTop:
 ?? () from /usr/lib/libGL.so.1
 ?? () from /usr/lib/libGL.so.1
 ?? () from /lib/ld-linux.so.2
 exit () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Title: busyspheres crashed with SIGSEGV in exit()
Uname: Linux 2.6.28-9-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Revision history for this message
Dylan Taylor (dylanmtaylor) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /usr/lib/libGL.so.1
?? ()
_dl_fini () at dl-fini.c:248
*__GI_exit (status=1) at exit.c:75
createWindow ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in rss-glx:
importance: Undecided → Medium
Revision history for this message
Brian Murray (brian-murray) wrote :

The crash is occurring in libGL.so.1 so reassigning to the driver package.

visibility: private → public
affects: rss-glx (Ubuntu) → fglrx-installer (Ubuntu)
Revision history for this message
Martin Olsson (mnemo) wrote :

Hi aliendude5300,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and also Xorg.0.log.old) file from after reproducing this issue (the best thing is if you can SSH into the machine immediately after it's crashed because the the logs usually have the most interesting information). If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

tags: added: needs-lspci-vvnn needs-xorglog
Bryce Harrington (bryce)
tags: added: crash
Revision history for this message
Bryce Harrington (bryce) wrote :

I've posted a new version of the -fglrx driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get fglrx 8.620 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

Changed in fglrx-installer (Ubuntu):
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

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.

Changed in fglrx-installer (Ubuntu):
status: Incomplete → Invalid
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.