rhythmbox-metadata crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firefox (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
rhythmbox (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Refreshing metadata
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: rhythmbox 2.99.1-0ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-8-generic x86_64
NonfreeKernelMo
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Sep 25 16:30:26 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-02-27 (210 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f8daa5dbfd7: movzbl (%r10,%rcx,1),%r10d
PC (0x7f8daa5dbfd7) ok
source "(%r10,%rcx,1)" (0x7f8e9c023907) 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 saucy on 2013-08-27 (29 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.