aplay crashed with SIGABRT in pthread_cond_wait@@GLIBC_2.3.2()

[Florian Hars]

I played sound from festival, using (tts "README" nil) and pressed Ctrl-C after some time, which sometimes results in

festival> (tts "README" nil)
^CSIOD ERROR: control-c interrupt
closing a file left open: README
festival> Assertion 'pthread_mutex_destroy(&m->mutex) == 0' failed at pulse
core/mutex-posix.c:83, function pa_mutex_free(). Aborting.
Aborted (core dumped)

SIOD ERROR: control-c interrupt

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: alsa-utils 1.0.25-3ubuntu2.1
ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4
Uname: Linux 3.5.0-24-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
CrashCounter: 1
Date: Tue Feb 26 15:00:32 2013
ExecutablePath: /usr/bin/aplay
InstallationDate: Installed on 2011-10-29 (485 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MarkForUpload: True
ProcCmdline: aplay -q -c 1 -t raw -f s16 -r 16000 /tmp/audiofile_28572
Signal: 6
SourcePackage: alsa-utils
StacktraceTop:
 pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0
 pa_threaded_mainloop_wait () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
 pulse_wait_operation () from /usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_pulse.so
 ?? () from /usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_pulse.so
 ?? () from /usr/lib/x86_64-linux-gnu/libasound.so.2
Title: aplay crashed with SIGABRT in pthread_cond_wait@@GLIBC_2.3.2()
UpgradeStatus: Upgraded to quantal on 2012-09-29 (150 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

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