Ubuntu
nautilus-open-terminal package

nautilus crashed with SIGSEGV in gconf_client_get()

Bug #865545 reported by lulo on 2011-10-03

This bug report is a duplicate of: Bug #865115: nautilus crashed with SIGSEGV in gconf_client_get(), if both nautilus-open-terminal and ubuntuone-client-gnome are installed. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	nautilus-open-terminal (Ubuntu)	New	Undecided	Unassigned

Bug Description

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus-open-terminal 0.19-1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Mon Oct 3 19:26:07 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110907)
ProcCmdline: nautilus -n
SegvAnalysis:
Segfault happened at: 0x7f068a51d8be <gconf_client_get+46>: cmp %rax,(%rdx)
PC (0x7f068a51d8be) 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-open-terminal
StacktraceTop:
gconf_client_get () from /usr/lib/libgconf-2.so.4
gconf_client_get_bool () from /usr/lib/libgconf-2.so.4
nautilus_open_terminal_get_file_items () from /usr/lib/nautilus/extensions-3.0/libnautilus-open-terminal.so
?? ()
?? ()
Title: nautilus crashed with SIGSEGV in gconf_client_get()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Tags:

Revision history for this message

lulo (lulojs11) wrote on 2011-10-03:

ProcEnviron.txt Edit (117 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-10-03: This bug is a duplicate

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 #865212, 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.