metacity crashed with SIGABRT in _XError()

[Robie Basak]

Crash on login after upgrading just now. Yesterday's archive was OK. I seem to still have window manager decorations that work but no indicators or bar on the left.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: metacity 1:2.34.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 14 09:31:22 2011
ExecutablePath: /usr/bin/metacity
ProcCmdline: metacity
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/false
 PATH=(custom, no user)
Signal: 6
SourcePackage: metacity
StacktraceTop:
 ?? ()
 ?? ()
 _XError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: metacity crashed with SIGABRT in _XError()
UpgradeStatus: Upgraded to oneiric on 2011-09-03 (10 days ago)
UserGroups:

[Robie Basak (racb)]

This did not reproduce on Ctrl-Alt-Backspace (no other way to log out) and log in.

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 _XError (dpy=0x20fcc00, rep=<optimized out>) at ../../src/XlibInt.c:1583
 handle_error (dpy=0x20fcc00, err=0x218f630, in_XReply=<optimized out>) at ../../src/xcb_io.c:212
 handle_response (dpy=0x20fcc00, response=0x218f630, in_XReply=<optimized out>) at ../../src/xcb_io.c:324

[Pedro Villavicencio (pedro)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
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.

[Dmitry Shachnev (mitya57)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of private bug #848808, so 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.