I seem to get this crash each time I start rhythmbox. My library loads and songs seem to play without incident however.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: rhythmbox 3.0.1-1ubuntu16
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Mar 31 00:35:27 2014
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationDate: Installed on 2011-07-08 (997 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
PATH=(custom, user)
LANGUAGE=en_US
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f38e85b0fd7: movzbl (%r10,%rcx,1),%r10d
PC (0x7f38e85b0fd7) ok
source "(%r10,%rcx,1)" (0x7f39d8023907) 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 2013-12-04 (116 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare sbuild vboxusers
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.