nautilus crashed with SIGSEGV in gconf_client_get()

Bug #865212 reported by Peter Johnson
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
nautilus-open-terminal (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

nautilus crashed after navigating to a random folder

ubuntu version:
Description: Ubuntu oneiric (development branch)
Release: 11.10

nautilus:
  Installed: 1:3.2.0-0ubuntu5
  Candidate: 1:3.2.0-0ubuntu5
  Version table:
 *** 1:3.2.0-0ubuntu5 0
        500 http://at.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
        100 /var/lib/dpkg/status

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: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Mon Oct 3 12:26:45 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x7fe1b22828be <gconf_client_get+46>: cmp %rax,(%rdx)
 PC (0x7fe1b22828be) 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: Upgraded to oneiric on 2011-09-30 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Peter Johnson (cmeater) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gconf_client_get (client=0x19c3980, key=0x7fe1b2499850 "/desktop/gnome/lockdown/disable_command_line", err=0x7fff8c0712c8) at gconf-client.c:1593
 gconf_client_get_bool (client=0x19c3980, key=0x7fe1b2499850 "/desktop/gnome/lockdown/disable_command_line", err=0x0) at gconf-client.c:1778
 nautilus_open_terminal_get_file_items () from /tmp/tmpkiMMBq/usr/lib/nautilus/extensions-3.0/libnautilus-open-terminal.so
 get_all_extension_menu_items (window=0x2026150, selection=0x0) at nautilus-view.c:4576
 reset_extension_actions_menu (selection=0x0, view=0x209d840) at nautilus-view.c:4845

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus-open-terminal (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nautilus-open-terminal (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel Hahler (blueyed) wrote :

Duplicate of bug 865115?

visibility: private → public
Revision history for this message
Piers Cilliers (piers) wrote :

How can this problem be of "medium" importance???? Whether this is exactly the same problem or not I do not know, but I CANNOT open ANY window and it crashes! Please in Gods name find a fix for this blasted bug or what ever it is! My machine is completely unusable at this stage!

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Piers, the latest nautilus-open-terminal fixes this.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.