rhythmbox crashed with SIGSEGV in monitor_entry_file()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crashed when I was starting rhythmbox.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: rhythmbox 2.97-1ubuntu4
ProcVersionSign
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Mon Sep 3 01:52:02 2012
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120831)
ProcCmdline: rhythmbox
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f18672af0d0 <monitor_
PC (0x7f18672af0d0) ok
source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rsi" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
monitor_entry_file (db=0x184c240, entry=<optimized out>) at rhythmdb-
monitor_entry_file (entry=<optimized out>, db=0x184c240) at rhythmdb-
rhythmdb_
_monitor_
?? () from /lib/x86_
Title: rhythmbox crashed with SIGSEGV in monitor_
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 #1029333, 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.