rhythmbox-metadata crashed with SIGSEGV in _start()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Due to investigating bug 926329 after closing Rhythmbox and launching it again via dash - recent apps it crashed twice.
Launched fine on third and fourth attempt.
The initial launch also works fine via dash or indicator.
Terminal output:
~$ rhythmbox
GLib-GIO-CRITICAL **: GApplication subclass 'RBShell' failed to chain up on ::startup (from start of override function)
## There're other bugs (screenshot) regarding metadata crash with Oneiric.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: rhythmbox 2.95-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Fri Feb 3 21:37:25 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x4081a5 <_start+1937>: cmp %rbp,0x8(%rbx)
PC (0x004081a5) 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 0x00000000004081a5 in _start ()
No symbol table info available.
StacktraceTop: _start ()
Title: rhythmbox-metadata crashed with SIGSEGV in _start()
UpgradeStatus: No upgrade log present (probably fresh install)
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 #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.