Crash dialog while waiting for songs to be added to Rhythmbox

Bug #1303386 reported by Leif Arne Storset
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

I set my music folder in Preferences, but grew tired of waiting for my songs to show up, so I dragged them into the window to play immediately. Rhythmbox processed them as an addition instead of instant play, which is probably not a bad idea, but it hung while processing "0 of 12 songs" or something, and then I got the rhythmbox-metadata crash dialog.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: rhythmbox 3.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux 3.13.0-22-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Apr 6 13:59:57 2014
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationDate: Installed on 2014-03-19 (17 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017)
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
SegvAnalysis:
 Segfault happened at: 0x7f6d7d210fd7: movzbl (%r10,%rcx,1),%r10d
 PC (0x7f6d7d210fd7) ok
 source "(%r10,%rcx,1)" (0x7f6e740e3ee7) not located in a known VMA region (needed readable region)!
 destination "%r10d" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstflump3dec.so
Title: rhythmbox-metadata crashed with SIGSEGV
UpgradeStatus: Upgraded to trusty on 2014-04-04 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data

Revision history for this message
Leif Arne Storset (lastorset) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1229400, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Leif Arne Storset (lastorset) wrote :

Bug #1229400 can't be found (perhaps it is also private?), so I can't verify whether it is a duplicate or add information.

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.