nautilus crashed with SIGSEGV in g_closure_invoke()

Bug #423194 reported by James Deibele
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nautilus

I was deleting some files that are on an external (USB) drive formatted with ext4 when Nautilus crashed.

ProblemType: Crash
Architecture: amd64
Date: Wed Sep 2 06:19:58 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.27.91-0ubuntu2
ProcCmdline: nautilus --sm-client-id 10383bd9141cbf772f124710739879146500000047160043
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
SegvAnalysis:
 Segfault happened at: 0x4cc18e: mov 0x18(%rdi),%rdx
 PC (0x004cc18e) 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-9-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev pulse pulse-access sambashare vboxusers

Revision history for this message
James Deibele (jdeibele) wrote :
Revision history for this message
Apport retracing service (apport) wrote : 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 #407768, 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.

visibility: private → public
tags: removed: need-amd64-retrace
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.