rhythmbox crashed with SIGSEGV in __pthread_mutex_unlock_usercnt()

Bug #1104130 reported by Michael Terry
36
This bug affects 4 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Was just listening to a radio station.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: rhythmbox 2.98-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
Uname: Linux 3.8.0-1-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Thu Jan 24 10:42:48 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 (14 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: 0x7f4b8411b063 <__pthread_mutex_unlock_usercnt+3>: mov 0x10(%rdi),%edi
 PC (0x7f4b8411b063) 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 () from /lib/x86_64-linux-gnu/libpthread.so.0
 g_mutex_unlock (mutex=<optimized out>) at /build/buildd/glib2.0-2.35.4/./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
 ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
Title: rhythmbox crashed with SIGSEGV in __pthread_mutex_unlock_usercnt()
UpgradeStatus: Upgraded to raring on 2013-01-16 (7 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Michael Terry (mterry) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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=mutex@entry=0x7f4af80240e8) at /build/buildd/glib2.0-2.35.4/./glib/gthread-posix.c:229
 gst_element_remove_pad (element=element@entry=0x7f4b500e0e70, pad=pad@entry=0x7f4af80240d0) at gstelement.c:819
 gst_input_selector_release_pad (element=0x7f4b500e0e70, pad=0x7f4af80240d0) at gstinputselector.c:1678

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in rhythmbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Michael Terry (mterry)
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in rhythmbox (Ubuntu):
status: New → Confirmed
Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

Changed in rhythmbox (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]

Changed in rhythmbox (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.