metacity crashed with SIGABRT in raise()

[Muelli]

Just tried to log in guess

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: metacity 1:2.34.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4
Uname: Linux 3.0-2-generic x86_64
Architecture: amd64
Date: Sat Jul 2 12:35:10 2011
ExecutablePath: /usr/bin/metacity
ProcCmdline: metacity
ProcEnviron:
 LC_MESSAGES=en_GB.UTF-8
 LANG=en_US.UTF-8
 SHELL=/bin/false
 PATH=(custom, no user)
Signal: 6
SourcePackage: metacity
StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 ?? ()
 ?? ()
 _XError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: metacity crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to oneiric on 2011-07-02 (0 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 meta_bug (format=<value optimized out>) at core/util.c:398
 x_error_handler (xdisplay=0xf64000, error=0x7fff3da211b0) at core/errors.c:247
 x_error_handler (xdisplay=0xf64000, error=0x7fff3da211b0) at core/errors.c:203

[Brian Murray (brian-murray)]

This happened to me when trying to log into the "Ubuntu" session.

[Barry Warsaw (barry)]

This occurred for me after trying to start mumble.

[Zhong (xuanzhong)]

On 7/27/2011 10:46 PM, Barry Warsaw wrote:
> This occurred for me after trying to start mumble.
>
what is your hardware details?

[hellojoker (hellojoker81-deactivatedaccount)]

Even for me, happened immediately after login nvidia 8800 gts 640MB

275.09.07-0ubuntu4 nvidia-current

[hellojoker (hellojoker81-deactivatedaccount)]

It also happens with the nouveau

[Francesco Muriana (f-muriana)]

It also affects me

[Pedro Villavicencio (pedro)]

Thank you 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 797078, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.