nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()

Bug #650711 reported by Stenten
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: nautilus

Reproducible crash when clicking the "Eject" icon next to my USB Flashdrive on the sidebar.

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: Tue Sep 28 19:09:38 2010
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100803.1)
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x808a884: mov (%eax),%eax
 PC (0x0808a884) ok
 source "(%eax)" (0x69736976) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown 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

Revision history for this message
Stenten (stenten) wrote :
Revision history for this message
Stenten (stenten) wrote :

Bug 650716 contains the apport data from another instance of this crash/bug, reproduced immediately after the one in this report. I thought it might be useful for comparison's sake. It seems this might be the cause (from .xsession-errors):

(nautilus:1323): Gtk-CRITICAL **: IA__gtk_widget_set_child_visible: assertion `GTK_IS_WIDGET (widget)' failed
(nautilus:1323): Gtk-CRITICAL **: IA__gtk_widget_size_allocate: assertion `GTK_IS_WIDGET (widget)' failed

Revision history for this message
Stenten (stenten) wrote :

I tried ejecting using File->Eject, which worked successfully, as well as Safely Remove Device. Since doing these (and emptying the trash in the process), I can no longer reproduce the bug.

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

StacktraceTop:
 nautilus_path_bar_size_allocate (widget=0x85361b0,
 g_cclosure_marshal_VOID__BOXED ()
 ?? () 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

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-i386-retrace
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.