Ubuntu
metacity package

Metacity (and X Server) crashed when starting beryl

Bug #78191 reported by Michael Wohlmuther
4
Affects Status Importance Assigned to Milestone
metacity (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: metacity

I am using Ubuntu on my AMD Athlon 64 3200+ and Nvidia (PCI-E) Card.

Metacity crashes instantly when starting beryl-manager (on edgy)

Revision history for this message
Michael Wohlmuther (mwohlmuther) wrote :
Revision history for this message
Marnanel Thurman (marnanel) wrote :

Did you have compositing turned on in metacity?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you reply to the previous question? Does it happen every time you enable beryl?

Changed in metacity:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Kim Chee Leong (kc-leong) wrote :

Every time I start beryl-manager , I get a crash. Using i386.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you try to get a backtrace with the metacity-dbgsym package installed?

Revision history for this message
Kim Chee Leong (kc-leong) wrote :

Backtrace didn't work, I've metacity-dbgsym and beryl-manager-dbgsym packages installed. gdb says (no debugging symbols found)

The strace did work, attached a dump.

The xorg log also spitted a error:

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x81) [0x80c5d81]
1: [0xb7f42420]

Fatal server error:
Caught signal 11. Server aborting

Revision history for this message
Kim Chee Leong (kc-leong) wrote :

# Did you have compositing turned on in metacity?
compositing is turned off in the gconf-editor

Revision history for this message
Kim Chee Leong (kc-leong) wrote :

Found in the strace log that I got a crash in glxinfo. After reinstalling the Nvidia driver and re-setting the xorg.conf file with the Nvidia's own installer everything was fine.

beryl-manager and glx-info (or other glx.. commands) work

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you get a debug backtrace?

Revision history for this message
Kim Chee Leong (kc-leong) wrote :

Did not got a debug backtrace. Now running Feisty, never got this crash again.

Revision history for this message
Sebastien Bacher (seb128) wrote :

closing the bug then

Changed in metacity:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.