rhythmbox-metadata crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The crash message appears, whenever I start Rhythmbox.
It seems that the crash does not affect the main application.
Maybe the crash is related to the fact, that I have the music on an NTFS partition which is mounted as readonly.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: rhythmbox 3.0.1-1ubuntu16
ProcVersionSign
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Mar 29 18:11:13 2014
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-10-20 (160 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f95b259ffd7: movzbl (%r10,%rcx,1),%r10d
PC (0x7f95b259ffd7) ok
source "(%r10,%rcx,1)" (0x7f96a40570e7) 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/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: rhythmbox-metadata crashed with SIGSEGV
UpgradeStatus: Upgraded to trusty on 2014-03-29 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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.