nautilus crashed with SIGSEGV in gconf_client_get()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus-open-terminal (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Using Gnome Shell. Nautilus constantly crashes. External media inserted (SD Card) and opened. Went to change directories once and crashed... then on restart, went to open additional pane and it carashed.
(Similar behavior exhibited with VLC in ubuntu... doing anything other than letting opened video play... locks up system.)
Never experienced anything like this on any previous *buntus (user since 07.04). One would think the file manager would be stable. Only started a week and half ago when updates to 11.10 beta 2 were done. Has been one or two massive upgrades since then... but issue persists.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus-
ProcVersionSign
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Sat Oct 8 20:56:00 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: nautilus -n
ProcEnviron:
PATH=(custom, no User Name)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x10fef99 <gconf_
PC (0x010fef99) ok
source "%eax" ok
destination "(%edx)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nautilus-
StacktraceTop:
gconf_client_get () from /usr/lib/
gconf_
nautilus_
nautilus_
?? ()
Title: nautilus crashed with SIGSEGV in gconf_client_get()
UpgradeStatus: Upgraded to oneiric on 2011-09-03 (35 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #869856, 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.