rhythmbox-metadata crashed with SIGSEGV in _start()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| rhythmbox (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Opened an mp3 file using rhythmbox. Rhythmbox window appeared (but did not show the file that I had opened) and crashed immediately.
Description: Ubuntu precise (development branch)
Release: 12.04
rhythmbox:
Installed: 2.95-0ubuntu3
Candidate: 2.95-0ubuntu3
Version table:
*** 2.95-0ubuntu3 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: rhythmbox 2.95-0ubuntu3
ProcVersionSign
Uname: Linux 3.2.0-17-
ApportVersion: 1.94-0ubuntu1
Architecture: i386
CheckboxSubmission: a15aeb06833f0b0
CheckboxSystem: bb422ca46d02494
Date: Sat Mar 3 13:47:05 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: /usr/lib/
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x804e638 <_start+2108>: cmp %eax,0x4(%ebx)
PC (0x0804e638) ok
source "%eax" ok
destination "0x4(%ebx)" (0x00000005) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: rhythmbox
Stacktrace:
#0 0x0804e638 in _start ()
No symbol table info available.
StacktraceTop: _start ()
Title: rhythmbox-metadata crashed with SIGSEGV in _start()
UpgradeStatus: Upgraded to precise on 2012-03-02 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| Sarrvesh (sarrfriend) wrote | #1 |
| visibility: | private → public |
| visibility: | public → private |
| visibility: | private → public |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-i386-retrace |
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 #820601, 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.