[apport] beryl crashed with SIGSEGV in XPending()

Bug #96138 reported by afarmer2005
730
Affects Status Importance Assigned to Milestone
beryl-core (Ubuntu)
Invalid
High
Unassigned

Bug Description

Binary package hint: beryl-core

Running Beryl give an unstable system.

ProblemType: Crash
Architecture: i386
Date: Sun Mar 25 19:13:31 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/beryl
Package: beryl-core 0.2.1.dfsg+git20070318-0ubuntu2
PackageArchitecture: i386
ProcCmdline: beryl
ProcCwd: /home/afarmer
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 ltue0027 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

Tags: iso-testing
Revision history for this message
afarmer2005 (afarmer2005) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:doPoll (timeout=<value optimized out>) at display.c:1332
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
Daniel Hahler (blueyed)
Changed in beryl-core:
status: Unconfirmed → Confirmed
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Marked as high importance because of high number of duplicates.

Changed in beryl-core:
importance: Undecided → High
Revision history for this message
Nick (lupine) wrote :

It appears to be an issue with the 'text' plugin... although what, I'm not sure, as the code there looks fine. Could you check and confirm whether disabling the text plugin works around this issue?

Revision history for this message
liddokun10 (liddokun10) wrote : RE: [Bug 96138] Re: [apport] beryl crashed with SIGSEGV in XPending()

Hi, which text plugin are you referring to? Not too sure.

>It appears to be an issue with the 'text' plugin... although what, I'm
>not sure, as the code there looks fine. Could you check and confirm
>whether disabling the text plugin works around this issue?
>
>--
>[apport] beryl crashed with SIGSEGV in XPending()
>https://bugs.launchpad.net/bugs/96138
>You received this bug notification because you are a direct subscriber
>of a duplicate bug.

_________________________________________________________________
Get an advanced look at the new version of Windows Live Messenger.
http://get.live.com/messenger/overview

Revision history for this message
Aaron D. Campbell (aaroncampbell) wrote :

Well, it seems that a few of my crashes were duplicates of this. I'd love to help if I can, but like liddokun10...I don't see a "text plugin" to disable. How would I do that (through beryl-settings, or even a config file).

Revision history for this message
Aaron D. Campbell (aaroncampbell) wrote :

I found what you mean. In beryl-settings, go to "Image Format" then uncheck text on the left. I did this, and I guess we'll wait and see if it crashes again. What benefit does this plugin offer? Cleaner looking text during effects?

Revision history for this message
degouttes (bradbti-launchpad) wrote :

Thanks, I think its working OK now.
I've done multiple boots now, Beryl hasn't crashed since
changing TEXT to disable.
       Thanks

Aaron D. Campbell wrote:
> I found what you mean. In beryl-settings, go to "Image Format" then
> uncheck text on the left. I did this, and I guess we'll wait and see if
> it crashes again. What benefit does this plugin offer? Cleaner looking
> text during effects?
>
>

Revision history for this message
Harrison Conlin (harrisony) wrote :

It seems to me that this is quite a serious problem to do with the text plugin as stated here https://bugs.launchpad.net/ubuntu/+source/beryl-core/+bug/96138/comments/5
there are over 50 duplicates!!!!! this issue seems to only apply to the ubuntu package from the official reps. and not a beryl issue it self

Revision history for this message
Elephantman (elephantman) wrote :

+1

Revision history for this message
William Grant (wgrant) wrote : Beryl has been removed from Gutsy

Beryl is replaced by Compiz Fusion, so has been removed from Gutsy.

  status invalid
  subscribe

Changed in beryl-core:
status: Confirmed → Invalid
Revision history for this message
Aaron D. Campbell (aaroncampbell) wrote :

So, because this is being replaced in 3 months with another version...it's invalid? What about for the next few months?

Revision history for this message
Pookito pookito (pookito) wrote : Re: [Bug 96138] Re: [apport] beryl crashed with SIGSEGV in XPending()

Aaron D. Campbell wrote:
> So, because this is being replaced in 3 months with another
> version...it's invalid? What about for the next few months?
>
>
Hi Aaron, thank you for writing me. If this is going to be replace in
around 3 months, does that mean that Beryl will finally be stable?

Thanks

Revision history for this message
William Grant (wgrant) wrote : Re: [Bug 96138] Re: [apport] beryl crashed with SIGSEGV in XPending()

On Sat, 2007-07-14 at 11:37 +0000, Joshua Duran wrote:
> Aaron D. Campbell wrote:
> > So, because this is being replaced in 3 months with another
> > version...it's invalid? What about for the next few months?
> >
> >
> Hi Aaron, thank you for writing me. If this is going to be replace in
> around 3 months, does that mean that Beryl will finally be stable?

Beryl has been discontinued upstream (it merged with Compiz in order to
create Compiz Fusion). The release he speaks of is Ubuntu 7.10, which
will include Compiz Fusion. The chance of any bugfixes to Beryl is
minimal.

Revision history for this message
shanen (Shannon Jacobs) (shanen) wrote :

How can I tell if this is the crash I'm seeing? Where should I look in the logs? All I'm actually seeing is a white screen of total death--but now it's up to twice per hour.

Revision history for this message
shanen (Shannon Jacobs) (shanen) wrote :

Sorry, just getting subscribed with this one.

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/96138

tags: added: iso-testing
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.