nautilus crashed with SIGSEGV in gconf_client_get() - nautilus hasn't started until I removed the nautilus-open-terminal package
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus-open-terminal (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I've installed Ubuntu 11.10. That was a fresh install not an upgrade.
I was unable to start the nautilus until I removed the nautilus-
When I try to launch nautilus from a terminal the application gave me the following debug output:
mymachine:
Initializing nautilus-gdu extension
Initializing nautilus-
Initializing nautilus-
** (nautilus:11955): DEBUG: SyncDaemon already running, initializing SyncdaemonDaemon object
(nautilus:11955): Gtk-CRITICAL **: gtk_action_
(nautilus:11955): Gtk-CRITICAL **: gtk_action_
Segmentation fault
I really like the nautilus-
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus-
ProcVersionSign
Uname: Linux 3.0.0-12-
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Sun Oct 16 20:08:54 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: nautilus
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
LANGUAGE=en_US:en
SegvAnalysis:
Segfault happened at: 0xb3e05f99 <gconf_
PC (0xb3e05f99) 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: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev root uucp video
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.