pulseaudio crashed with SIGABRT in pa_hook_fire()

[Carl Leitner]

pulseaudio

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: pulseaudio 1:4.0-0ubuntu2+build1
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic i686
ApportVersion: 2.12.1-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: litlfred 3947 F.... pulseaudio
 /dev/snd/pcmC1D0p: litlfred 3947 F...m pulseaudio
 /dev/snd/controlC0: litlfred 3947 F.... pulseaudio
 /dev/snd/pcmC0D0p: litlfred 3947 F...m pulseaudio
Date: Sun Sep 8 19:29:00 2013
ExecutablePath: /usr/bin/pulseaudio
InstallationDate: Installed on 2011-09-29 (710 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MarkForUpload: True
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
Signal: 6
SourcePackage: pulseaudio
StacktraceTop:
 ?? () from /usr/lib/pulse-4.0/modules/module-combine-sink.so
 ?? () from /usr/lib/pulse-4.0/modules/module-combine-sink.so
 pa_hook_fire () from /usr/lib/libpulsecore-4.0.so
 pa_sink_unlink () from /usr/lib/libpulsecore-4.0.so
 ?? () from /usr/lib/pulse-4.0/modules/libalsa-util.so
Title: pulseaudio crashed with SIGABRT in pa_hook_fire()
UpgradeStatus: Upgraded to saucy on 2013-08-18 (21 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare video
dmi.bios.date: 09/13/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: MWPNT10N.86A.0069.2010.0913.1432
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: D525MW
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE93082-301
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrMWPNT10N.86A.0069.2010.0913.1432:bd09/13/2010:svn:pn:pvr:rvnIntelCorporation:rnD525MW:rvrAAE93082-301:cvn:ct2:cvr:

[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 #1217036, 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.