nautilus crashed with SIGSEGV in gconf_client_get()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus-open-terminal (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I can not open nautilus, it always crashes
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus-
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Oct 5 12:52:22 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100804)
ProcCmdline: nautilus -n
ProcEnviron:
PATH=(custom, user)
LANG=es_ES.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fd9432a58be <gconf_
PC (0x7fd9432a58be) ok
source "%rax" ok
destination "(%rdx)" (0x700000008) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus-
StacktraceTop:
gconf_client_get () from /usr/lib/
gconf_
nautilus_
get_all_
reset_
Title: nautilus crashed with SIGSEGV in gconf_client_get()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio avahi avahi-autoipd backup bin bluetooth cdrom clamav clamsmtp couchdb crontab daemon davac4 dialout dip disk fax floppy fuse games gdm gnats gnokii haldaemon iocard irc kmem libuuid list lp lpadmin mail man messagebus mlocate netdev news ntp operator pcscd pkcs11 plugdev postdrop postfix powerdev proxy pulse pulse-access rtkit sambashare saned sasl shadow src ssh ssl-cert staff sudo sys syslog tape timidity tty users usrp utempter utmp uucp video voice www-data
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 #868221, 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.