nautilus crashed with SIGSEGV in g_closure_invoke()

Bug #779180 reported by jim galley
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Nautilus
Expired
Critical
nautilus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: nautilus

was connected to a remote server via ssh, and viewing the files in a second panel. The remote server disconnected, and the associated panel went gray. I went to close nautilus, and it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu13
ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
Uname: Linux 2.6.38-9-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Fri May 6 17:21:27 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x466e42: mov 0x18(%rax),%rbp
 PC (0x00466e42) ok
 source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to natty on 2011-04-11 (25 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
jim galley (jim-galley) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 nautilus_window_slot_get_location (slot=0x17b56c0) at nautilus-window-slot.c:229
 nautilus_navigation_window_update_split_view_actions_sensitivity (window=<value optimized out>) at nautilus-navigation-window-menus.c:542
 g_closure_invoke (closure=0x139a2f0, return_value=0x0, n_param_values=2, param_values=0x168ec60, invocation_hint=0x7fff1b127960) at /build/buildd/glib2.0-2.28.6/./gobject/gclosure.c:767
 signal_emit_unlocked_R (node=<value optimized out>, detail=0, instance=0xc70800, emission_return=0x0, instance_and_params=0x168ec60) at /build/buildd/glib2.0-2.28.6/./gobject/gsignal.c:3252
 g_signal_emit_valist (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>, var_args=<value optimized out>) at /build/buildd/glib2.0-2.28.6/./gobject/gsignal.c:2983

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 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Changed in nautilus (Ubuntu):
status: New → Triaged
Revision history for this message
Pedro Villavicencio (pedro) wrote :

this looks like the bug pointed there https://bugzilla.gnome.org/show_bug.cgi?id=638806

Changed in nautilus:
importance: Unknown → Critical
status: Unknown → New
Changed in nautilus:
status: New → Incomplete
Changed in nautilus:
status: Incomplete → Expired
Revision history for this message
Sebastien Bacher (seb128) wrote :

The bug didn't get activity/new duplicates for some years and the nautilus code saw quite some changes since which probably deprecated the issue so closing it. If it's still a problem in recent Ubuntu/nautilus version please submit a new report

Changed in nautilus (Ubuntu):
status: Triaged → Invalid
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.