indicator-sound-service crashed with SIGABRT in raise()

[Anmar Oueja]

I wasn't doing anything special. I had the system docked to a docking station. After I undocked it, it continued to play music but crashed shortly after.

Please note that the docking station has a display port on it and the system defaults to sending audio through the display port (calls it HDMI in the logs). I have to go to the sound preferences to change the output to the analog device for sound to come out of the speakers hooked up to the headphone jack at the back of the docking station. Switching the output used to cause sound preferences to crash but an update fixed that. Not sure if this is related.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-sound 0.8.1.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 16 12:17:31 2012
ExecutablePath: /usr/lib/indicator-sound/indicator-sound-service
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120124)
ProcCmdline: /usr/lib/indicator-sound/indicator-sound-service
Signal: 6
SourcePackage: indicator-sound
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
Title: indicator-sound-service crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-02-07 (9 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 #914883, 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.