compiz crashed with SIGABRT in raise()

[Dan Kegel]

May be a dup of bug 857738, I haven't seen the stack yet so I can't tell.

This happened after about 40 minutes of uptime; I had just pressed the button on the DVD drive to eject
a game disc, inserted a blank cd-rom, and was surprised to see that the desktop had not noticed this
and unmounted the dvd; I then right-clicked the DVD icon in the unity launcher and chose 'eject'.
The crash happened a few seconds thereafter. Might be a coincidence; I was thinking about reporting the
missed ejection event as a bug when the desktop crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.0.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic-pae 3.2.2
Uname: Linux 3.2.0-12-generic-pae i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Thu Feb 2 06:40:31 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: unity
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
Title: compiz crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-02-01 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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

[Dan Kegel (dank)]

The stack trace is different from the five or so similar bugs I could find, so this doesn't seem to be a dup. Here's the stacktrace:

#2 0xb6d192b5 in abort () from /lib/i386-linux-gnu/libc.so.6
#3 0xb6d4facc in ?? () from /lib/i386-linux-gnu/libc.so.6
#4 0xb6d5a892 in ?? () from /lib/i386-linux-gnu/libc.so.6
#5 0xb6d5b532 in ?? () from /lib/i386-linux-gnu/libc.so.6
#6 0xb6d5e61d in free () from /lib/i386-linux-gnu/libc.so.6
#7 0xb6f2e51f in operator delete(void*) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#8 0xb6f1599b in std::string::_Rep::_M_destroy(std::allocator<char> const&) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#9 0xb409efdb in unity::IconLoader::Impl::Iteration() () from /usr/lib/compiz/libunityshell.so
#10 0xb409f0ab in unity::IconLoader::Impl::Loop(unity::IconLoader::Impl*) () from /usr/lib/compiz/libunityshell.so

Maybe this happened when I did right-click eject on the DVD icon, then?

I've installed libc6-dbg and unity-dbgsym so if this happens again, I can provide a slightly better backtrace.

[Dan Kegel (dank)]

Freaky - the mount point for the DVD I first ejected is still hanging around, I guess the desktop crashed before it removed that.
(I removed the mount point by hand, ejected my freshly-burned cd, reinserted it, and the desktop mounted it fine, so the system did seem to recover somewhat by itself.)

[Dan Kegel (dank)]

This really doesn't look like a dup of bug 750386. The stack traces look completely different. What is "apport retrace service" smoking?