metacity crashed with SIGABRT in raise()

[Michael Harkess]

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu (11.10 Oneric Ocelot Development Distro)
2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center (metacity:
  Installed: 1:2.34.1-1ubuntu4
  Candidate: 1:2.34.1-1ubuntu4
  Version table:
 *** 1:2.34.1-1ubuntu4 0
        500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
        100 /var/lib/dpkg/status
)
3) What you expected to happen (Was simply opening VLC media player - Using 2D Unity as VLC was crashing COMPIZ in Unity 3D)
4) What happened instead (Headers disappearing, metacity crashed)

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: metacity 1:2.34.1-1ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Thu Sep 22 22:16:53 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/metacity
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: metacity
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: metacity
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
 _XError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: metacity crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to oneiric on 2011-09-21 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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