Ubuntu
nautilus package

nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()

Bug #706641 reported by Marcos de Itapema on 2011-01-23

This bug report is a duplicate of: Bug #630884: nautilus crashed with SIGSEGV in g_closure_invoke(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	nautilus (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: nautilus

Running from Live-CD Ubuntu 10.10, nautilus with 2 panels (F3) browsing 2 local hard disk different filesystems (ext3 and fat), after having copied one little file from ext3 to fat, nautilus crashed when I clicked the eject buttom for the ext3 filesystem.
(I'm in a few years old Acer aspire 7520-5821 model notebook).

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Sun Jan 23 15:23:50 2011
ExecutablePath: /usr/bin/nautilus
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: nautilus
ProcEnviron:
LANG=pt_BR.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x808a882: mov (%esi),%eax
PC (0x0808a882) ok
source "(%esi)" (0x00000001) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
?? ()
g_cclosure_marshal_VOID__BOXED () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Marcos de Itapema (emmfamlame-001) wrote on 2011-01-23:

GConfNonDefault.txt Edit (472 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (1.6 KiB, text/plain; charset="utf-8")
usr_lib_nautilus.txt Edit (268 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-01-23: 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 #705233, 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-i386-retrace

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2011-01-27:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 630884, so it 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.