Comment 0 for bug 683972

Binary package hint: nautilus

i was ejecting 2 drives, ejected the second before the very final phase of eject for the first -> crash; currently not at home, will verify if this is reproducible like this then

will report on other g_closure_invoke bug i reported earlier, they were waiting for this crash dump

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: nautilus 1:2.32.0-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.37-7.18-generic 2.6.37-rc3
Uname: Linux 2.6.37-7-generic x86_64
Architecture: amd64
Date: Wed Dec 1 18:42:21 2010
ExecutablePath: /usr/bin/nautilus
ProcCmdline: nautilus
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x44c5a6: mov (%rax),%r14
 PC (0x0044c5a6) ok
 source "(%rax)" (0x64657469736976) not located in a known VMA region (needed readable region)!
 destination "%r14" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_closure_invoke()
UserGroups: adm admin cdrom dialout disk lpadmin plugdev sambashare