rhythmbox crashed with SIGSEGV in gst_clock_id_wait()

Bug #1135933 reported by Gediminas Paulauskas
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Filtered by genre (Unknown) that had one track, started playing it, then modified the properties to fix the genre. The browser refreshed and the genre disappeared from the list. Music stopped playing. Tried to play another track, but Rhythmbox crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: rhythmbox 2.98-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0
Uname: Linux 3.8.0-8-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu4
Architecture: i386
Date: Thu Feb 28 17:47:31 2013
Disassembly: => 0xaaaaaaaa: Cannot access memory at address 0xaaaaaaaa
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2012-09-06 (174 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120905.2)
MarkForUpload: True
ProcCmdline: rhythmbox
SegvAnalysis:
 Segfault happened at: 0xaaaaaaaa: Cannot access memory at address 0xaaaaaaaa
 PC (0xaaaaaaaa) in non-executable VMA region: 0xaaaa2000-0xaab00000 ---p None
 Stack memory exhausted (SP below stack segment)
SegvReason: executing non-writable VMA None
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? ()
 gst_clock_id_wait () from /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
 gst_base_sink_wait_clock () from /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
Title: rhythmbox crashed with SIGSEGV in gst_clock_id_wait()
UpgradeStatus: Upgraded to raring on 2013-02-22 (5 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Gediminas Paulauskas (menesis) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 gst_clock_id_wait (id=0xb1b82c0, jitter=jitter@entry=0xa7fadb40) at gstclock.c:512
 gst_base_sink_wait_clock (sink=sink@entry=0xb149100, time=<optimized out>, jitter=jitter@entry=0xa7fadb40) at gstbasesink.c:1998
 gst_audio_base_sink_sync_latency (obj=0xa76baa00, bsink=0xb149100) at gstaudiobasesink.c:1423
 gst_audio_base_sink_render (bsink=0xb149100, buf=0xa76baa00) at gstaudiobasesink.c:1627

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-i386-retrace
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.

Other bug subscribers

Remote bug watches

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