nautilus crashed with SIGSEGV in g_object_ref() after removal of an SD card

[Eugene Crosser]

Binary package hint: nautilus

Was copying files from an (automatically mounted) SD card. Then, right-clicked the card icon on the desktop and selected 'eject', the icon disappeared, I took the card off the slot, and then the whole screen flashed and the bug report window appeared.

ProblemType: Crash
Architecture: amd64
Date: Sun Sep 13 00:13:16 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.27.92-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.31-generic
SegvAnalysis:
 Segfault happened at: 0x7fd54e8564e1 <g_object_ref+17>: cmpq $0x50,(%rax)
 PC (0x7fd54e8564e1) ok
 source "$0x50" ok
 destination "(%rax)" (0x700000008) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_object_ref () from /usr/lib/libgobject-2.0.so.0
 g_datalist_clear () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 ?? ()
Title: nautilus crashed with SIGSEGV in g_object_ref()
Uname: Linux 2.6.31-10-generic x86_64
UserGroups: adm admin cdrom dialout dip lpadmin plugdev sambashare

[Apport retracing service (apport)]

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 #412966, 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.