nautilus crashed with SIGSEGV in g_closure_invoke()

Bug #520944 reported by Henrique Ferreiro
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: nautilus

I had just removed two files using shift+delete and then pressed the left arrow key or clicked elsewhere, I don't remember the exact details.

ProblemType: Crash
Architecture: amd64
Date: Fri Feb 12 13:07:11 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: nautilus 1:2.28.1-0ubuntu3
ProcCmdline: nautilus
ProcEnviron:
 LANG=gl_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.57-generic
SegvAnalysis:
 Segfault happened at: 0x4cc82e: mov 0x18(%rdi),%rdx
 PC (0x004cc82e) 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-20-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare scard

Revision history for this message
Henrique Ferreiro (henrique-ferreiro) wrote :
visibility: private → public
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
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.