[apport] beryl crashed with SIGSEGV in XPending()

Bug #99132 reported by TheJoker
4
Affects Status Importance Assigned to Milestone
beryl-core (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: beryl-core

beryl crashes after kde login (autostart)

Kubuntu 7.04 beta

ProblemType: Crash
Architecture: i386
Date: Fri Mar 30 20:28:09 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/beryl
Package: beryl-core 0.2.1.dfsg+git20070318-0ubuntu2
PackageArchitecture: i386
ProcCmdline: beryl
ProcCwd: /home/seb
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: beryl-core
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 XPending () from /usr/lib/libX11.so.6
Uname: Linux seb-laptop 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
TheJoker (sebhohns) wrote :
Revision history for this message
António Oliveira (tomane) wrote :

I get this message often at startup too.
I'm running KDE.
I don't knoe if this helps, but here goes some more info:
If I start the beryl manager from the K-menu, beryl doesn't start at all, doesn't crash, it's like if it wasn't even there. The only effect is the KDE launch feedback that is activated and ends after 30 seconds or so. It seems that it fails about half of the times I try so fire it up.
Is there any place where I can grab info about beryl startup?
cheers,
--to

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

StacktraceTop:eventLoop () at display.c:1896
main (argc=1, argv=) at main.c:370

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
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.