gleidescope crashed with SIGSEGV in exit()

Bug #343416 reported by Dylan Taylor
6
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: xscreensaver

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

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/xscreensaver/gleidescope
Package: xscreensaver-gl 5.07-0ubuntu3
ProcCmdline: gleidescope -root
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: xscreensaver
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: gleidescope 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
visual_warning (screen=0x88d0990, window=134581453,

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 xscreensaver:
importance: Undecided → Medium
Revision history for this message
Brian Murray (brian-murray) wrote :

Since the crash is occurring libGL.so.1 reassigning to the package that provides it.

visibility: private → public
affects: xscreensaver (Ubuntu) → mesa (Ubuntu)
Bryce Harrington (bryce)
tags: added: crash
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi aliendude5300,

Thanks for including the attached files. Could you also include your /var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue?

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-xorglog
Changed in mesa (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 mesa (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.