rhythmbox crashed with SIGSEGV in __pthread_mutex_unlock_usercnt()

[Michael Terry]

Was just playing internet radio.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: rhythmbox 2.98-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Mar 20 16:22:31 2013
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20120703-2
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2013-01-09 (69 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08
MarkForUpload: True
ProcCmdline: rhythmbox
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f2b54b3e053 <__pthread_mutex_unlock_usercnt+3>: mov 0x10(%rdi),%edi
 PC (0x7f2b54b3e053) ok
 source "0x10(%rdi)" (0xaaaaaaaaaaaaaaba) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 __pthread_mutex_unlock_usercnt (mutex=0xaaaaaaaaaaaaaaaa, decr=decr@entry=1) at pthread_mutex_unlock.c:37
 __GI___pthread_mutex_unlock (mutex=<optimized out>) at pthread_mutex_unlock.c:297
 g_mutex_unlock (mutex=<optimized out>) at /build/buildd/glib2.0-2.35.8/./glib/gthread-posix.c:229
 gst_element_remove_pad () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstcoreelements.so
Title: rhythmbox crashed with SIGSEGV in __pthread_mutex_unlock_usercnt()
UpgradeStatus: Upgraded to raring on 2013-01-31 (47 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers

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