[apport] beryl crashed with SIGSEGV in XPending()

Bug #116116 reported by zandrame
2
Affects Status Importance Assigned to Milestone
beryl-core (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: beryl-core

crashed on boot-up. no idea what the cause was!

ProblemType: Crash
Architecture: i386
Date: Mon May 21 01:57:22 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/beryl
Package: beryl-core 0.2.1.dfsg+git20070318-0ubuntu2
PackageArchitecture: i386
ProcCmdline: beryl --use-copy --force-aiglx --xgl-binding --skip-gl-yield
ProcCwd: /home/zandrame
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: beryl-core
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 XPending () from /usr/lib/libX11.so.6
Uname: Linux zandrame 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
zandrame (zandrame) wrote :
Revision history for this message
Martin Pitt (pitti) wrote : Symbolic stack trace

StacktraceTop:doPoll (timeout=<value optimized out>) at display.c:1332
eventLoop () at display.c:1896
main (argc=5, argv=) at main.c:370

Revision history for this message
Martin Pitt (pitti) wrote : Symbolic threaded stack trace
Revision history for this message
Martin Pitt (pitti) wrote : Symbolic stack trace

StacktraceTop:doPoll (timeout=<value optimized out>) at display.c:1332
eventLoop () at display.c:1896
main (argc=5, argv=) at main.c:370

Revision history for this message
Martin Pitt (pitti) wrote : Symbolic threaded stack trace
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 96138 and is being marked as such. Please feel free to report any other bugs you may find.

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.