rhythmbox-metadata crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
It crashed when I started rhythmbox.
$ lsb_release -rd
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
$ apt-cache policy rhythmbox
rhythmbox:
Installed: 3.0.1-1ubuntu8
Candidate: 3.0.1-1ubuntu8
Version table:
*** 3.0.1-1ubuntu8 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: rhythmbox 3.0.1-1ubuntu8
ProcVersionSign
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Jan 29 15:23:37 2014
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2014-01-26 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
LANGUAGE=en_CA:en
XDG_RUNTIME_
LANG=en_CA.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f7a31321fd7: movzbl (%r10,%rcx,1),%r10d
PC (0x7f7a31321fd7) ok
source "(%r10,%rcx,1)" (0x7f7b2c028907) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd 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.