metacity crashed with SIGABRT in raise() after login

[Jaromir Obr]

Binary package hint: metacity

This bug started a few days ago, when a batch of updates was installed.
Since then, whenever I login to Gnome, this assertion failure occurs.

Used SW:
Ubuntu 10.04 (up-to-date), amd64
kernel: 2.6.32-23-generic
metacity: 1:2.30.1-0ubuntu1

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[Jaromir Obr (jaromir-obr)]

Pedro, I got this info when I want to submit crash report :
-----------------------------------------
The problem cannot be reported:

The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes.
-----------------------------------------
Is there any way how to report it ?

[Pedro Villavicencio (pedro)]

Yes, please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. Thanks in advance.

[Jaromir Obr (jaromir-obr)]

backtrace attached

[Jaromir Obr (jaromir-obr)]

I'm also attaching appropriate crash report

[Pedro Villavicencio (pedro)]

no need to attach .crash files to the reports, there's nothing we can do with those, you can use apport as described before and if that doesn't work try the next method i told you about but do not attach .crash files. thanks.

[Pedro Villavicencio (pedro)]

May you please attach the metacity-dbgsym packages and get a new backtrace? Thanks Jaromir for the quick response.

[Jaromir Obr (jaromir-obr)]

But I had installed package "metacity-dbgsym" before I made the backtrace

metacity: 1:2.30.1-0ubuntu1
metacity-dbgsym: 1:2.30.1-0ubuntu1

[Jaromir Obr (jaromir-obr)]

The issue persists after upgrade to Maverick (10.10)
metacity: 1:2.30.2-0ubuntu1

[Eliah Kagan (degeneracypressure)]

If this still occurs on a fully-updated Maverick, Natty, or Oneiric system, and you're not able to get a good trace using the above method, please use sudo apport-retrace -g ... (https://wiki.ubuntu.com/Apport#Tools) to automatically install all debug symbol package that are relevant and available and start an interactive gdb session where you can obtain a (hopefully better) backtrace. (Replace ... with the name of the .crash file in /var/crash corresponding to the most recent instance of this crash.)

[Launchpad Janitor (janitor)]

[Expired for metacity (Ubuntu) because there has been no activity for 60 days.]