nautilus crashed with SIGSEGV in g_type_check_instance_cast()

Binary package hint: nautilus

Hi,
While trying to copy files from my storage drive to my empty desktop, there were no errors, but when trying to copy the same files (after editing) back to the storage drive (so that the originals would be overwritten) I was presented with this error for nautilus. Both drives are formatted in ext4, and I am using Ubuntu Lucid Alpha 2.
Thanks,
James

Nautilus 2.29.1 (1:2.29.1-0ubuntu2),Gnome 2.29.4

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Jan 15 10:29:01 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
NonfreeKernelModules: nvidia
Package: nautilus 1:2.29.1-0ubuntu2
ProcCmdline: nautilus
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SegvAnalysis:
 Segfault happened at: 0x3e7e19 <g_type_check_instance_cast+41>: mov (%eax),%edi
 PC (0x003e7e19) ok
 source "(%eax)" (0x73736170) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_type_check_instance_cast ()
 ?? () from /usr/lib/libappindicator.so.0
 g_cclosure_marshal_VOID__STRING ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Tags: lucid
Title: nautilus crashed with SIGSEGV in g_type_check_instance_cast()
Uname: Linux 2.6.32-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

StacktraceTop:
 g_type_check_instance_cast ()
 status_icon_changes (self=0x8cc2080, data=0x8fbf988)
 g_cclosure_marshal_VOID__STRING ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0

The same thing when copying new files to my IRiver. I've noticed than all files had copied by that moment.

This happened when I tried copying from and to an external Hard-drive.
I'm on x86_64 in case it matters

I'm also getting this bug on Lucid 64bit.

The issue seems to be due to the new indicator change

I will fix that one

The issue seems to not happen there, do people having the bug close the copy dialog? do you have an indicator applet configured?

the bug is due to indicator-application and triggered when the application service is not running, Ted could you have a look to this issue?

To Sebastien,
I can still recreate the bug almost consistantly. The first time it happened it involved me using my second hard drive, but I am seeing this happen in any location I paste large files or directories into, including desktop to desktop to make a copies of files.

All I need to do is copy a large file like an ISO image, or a large group of miscellaneous files in a folder, then paste the contents into another location. When the progress window opens up (the one that has the title "file operations"), it goes to about 90% and then crashes, and it also crashes any nautilus windows I have open. If I copy a very large amount of files (5gb or more), I can see my screen go from lite to dark several times during each transfer and the progress staggers. It appears that my files are unharmed and they actually completed every transfer every time. I can still copy and paste without crashing if the transfer size is small enough to not start the progress "file operations" window.

Normally I don't have an indicator applet in use because I like only using a single panel. Also, I didn't have this problem in Lucid Alpha 1. If I find anything else to add, I'll be back later.
Thanks for the help

Sorry I forgot.... I don't try to close anything during the file operations. The problem happens during normal file operations.

This bug was fixed in the package indicator-application - 0.0.9-0ubuntu2

---------------
indicator-application (0.0.9-0ubuntu2) lucid; urgency=low

  * Backport an upstream change to a fallback situation crasher
    (lp: #507975)
 -- Sebastien Bacher <email address hidden> Tue, 19 Jan 2010 20:52:41 +0100

cheers!

Thanks

Program received signal SIGSEGV, Segmentation fault.
0x002cf189 in g_type_check_instance_cast () from /usr/lib/libgobject-2.0.so.0
(gdb) backtrace full
#0 0x002cf189 in g_type_check_instance_cast () from /usr/lib/libgobject-2.0.so.0

Rest of the backtrace http://paste.ubuntu.com/438481/

var/log/messages reports:
afrodeity-desktop kernel: [122911.291879] nautilus[13859]: segfault at 7 ip 0035a189 sp bff4ab20 error 4 in libgobject-2.0.so.0.2400.1[330000+3d000]

valgrind reports a memory leak
http://paste.ubuntu.com/440366/

Marking this as Invalid for Nautilus and as Fix Released for Indicator Application since this was a bug that was fixed in the 0.0.10 release of Indicator Application and is not related to Nautilus at all.