nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__BOXED()

[Tom]

Binary package hint: nautilus

I was in the Ubuntu 10.10 Live CD, and had inserted a CD-ROM with a bash shell script. After the CD was viewable with the File Manager window, I had a terminal window open to copy the script to the /root directory. Then, in the File Manager window for the CD, I pressed on the right-click Eject selection which then proceeded to crash nautilus. Note: I have two CD-ROM devices.

1) Description: Ubuntu 10.10, Release: 10.10 (Maverick Meerkat)
2) ???
3) I expected the CD to eject - which it did, and the File Manager window for the CD-ROM to close
4) The File Manager window closed with nautilus crash.

-- Tom

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 Oct 19 14:32:48 2010
ExecutablePath: /usr/bin/nautilus
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x808a882: mov (%esi),%eax
 PC (0x0808a882) ok
 source "(%esi)" (0x00000008) 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

[Apport retracing service (apport)]

StacktraceTop:
 nautilus_path_bar_size_allocate (widget=0x97abda0, allocation=0xbfbdbf70)
 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

[Pedro Villavicencio (pedro)]

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.