metacity crashed with SIGABRT in _XError()

[Jean-Baptiste Lallement]

TEST CASE:
1. Launch vlc
2. click on button 'show playlist'

result:
This crash

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: metacity 1:2.34.1-1ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Mon Sep 26 23:10:09 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/metacity
ProcCmdline: metacity --replace --sync
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.utf8
Signal: 6
SourcePackage: metacity
StacktraceTop:
 ?? ()
 ?? ()
 _XError (dpy=0x8695ea8, rep=0xad200520) at ../../src/XlibInt.c:1583
 handle_error (dpy=0x8695ea8, err=0xad200520, in_XReply=1) at ../../src/xcb_io.c:212
 handle_response (dpy=0x8695ea8, response=0xad200520, in_XReply=1) at ../../src/xcb_io.c:324
Title: metacity crashed with SIGABRT in _XError()
UpgradeStatus: Upgraded to oneiric on 2011-07-12 (76 days ago)
UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin netdev plugdev scanner sudo video
XsessionErrors:
 (gnome-terminal:2896): Gtk-WARNING **: Unknown property: GtkHScale.update-policy
 (gnome-terminal:2896): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='common'
 (gwibber-service:2990): libindicate-WARNING **: Menu being changed when the indicator is visible. Listeners will NOT be notified of this change.
 (thunderbird-bin:3112): libebook-WARNING **: e_book_client_new: Failed to run book factory: Error calling StartServiceByName for org.gnome.evolution.dataserver.AddressBook1: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program /usr/lib/evolution/e-addressbook-factory: Success

[Apport retracing service (apport)]

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 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.