When unity starts, compiz crashes with SIGABRT in Glib::exception_handlers_invoke()

[Niran Babalola]

Binary package hint: compiz

On a fresh install of Natty updated with the latest packages and running within VirtualBox, the default Ubuntu login session results in an infinite loop of corrupted graphics. When viewing the output of `top`, the pid of compiz continually increases. If I try to restart unity with `DISPLAY=:0 unity --replace &> unity.log`, unity crashes as well. Compiz works fine in the Ubuntu Classic session.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4git20110322-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-8.40-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Tue Apr 5 15:56:08 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110405)
InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110405)
ProcCmdline: compiz
ProcCwd: /home/niran
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature_: Ubuntu 2.6.38-8.40-generic 2.6.38.2
Signal: 6
SourcePackage: compiz
StacktraceTop:
 Glib::exception_handlers_invoke() () from /usr/lib/libglibmm-2.4.so.1
 Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/libglibmm-2.4.so.1
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: compiz crashed with SIGABRT in Glib::exception_handlers_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
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 #737792, 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.