rhythmbox-metadata crashed with SIGSEGV in _start()

Bug #948662 reported by Colan Schwartz
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

Not sure what caused this crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: rhythmbox 2.90.1~20110908-0ubuntu1.3
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Tue Mar 6 22:22:43 2012
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
ProcEnviron:
 SHELL=/bin/zsh
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
SegvAnalysis:
 Segfault happened at: 0x408095 <_start+1937>: cmp %rbp,0x8(%rbx)
 PC (0x00408095) ok
 source "%rbp" ok
 destination "0x8(%rbx)" (0x00000009) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: rhythmbox
Stacktrace:
 #0 0x0000000000408095 in _start ()
 No symbol table info available.
StacktraceTop: _start ()
Title: rhythmbox-metadata crashed with SIGSEGV in _start()
UpgradeStatus: Upgraded to oneiric on 2011-10-02 (156 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse logcheck lp lpadmin mail netdev plugdev powerdev sambashare tape vboxusers video

Revision history for this message
Colan Schwartz (colan) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #815837, 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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.