nautilus crashed with SIGSEGV in g_closure_invoke() clicking refresh after unmount usb drive

Bug #470715 reported by Keith Powers
84
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: nautilus

crashed after unmounting usb drive and clicking refresh

steps to reproduce
1 navigate to folder on usb drive
2 use places link to unmount
3 click refresh button

ProblemType: Crash
Architecture: amd64
Date: Mon Nov 2 07:29:41 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia wl
Package: nautilus 1:2.28.1-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x4cc81e: mov 0x18(%rdi),%rdx
 PC (0x004cc81e) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Keith Powers (k-w-vendors-launchpad) wrote :
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

let's keep it private since it contains a coredump.gz.

visibility: public → private
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:nautilus_file_peek_display_name (file=0x0) at nautilus-file.c:3700
nautilus_file_get_display_name (file=0x0)
selection_changed_callback (window=0x12d81f0,
g_closure_invoke ()
?? () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: removed: need-amd64-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

Changed in nautilus (Ubuntu):
status: New → Invalid
visibility: private → public
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.