compiz crashed with SIGABRT in Glib::exception_handlers_invoke()

[Mir Tanvir Hossain]

Binary package hint: compiz

I was upgrading from 10.08. The upgrade process hung at the end. I had to force restart my laptop. Then, I selected the kernel included with 11.04 on the GRUB screen. That kernel did not work. So, I used the latest kernel included in 10.04. I got the exception right when I logged into my account.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4git20110322-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic i686
Architecture: i386
Date: Sat Apr 2 13:15:52 2011
DistroCodename: natty
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
InstallationMedia_: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature_: Ubuntu 2.6.35-28.49-generic 2.6.35.11
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/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: compiz crashed with SIGABRT in Glib::exception_handlers_invoke()
UpgradeStatus: Upgraded to natty on 2011-04-02 (0 days ago)
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu1

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