gvfsd-trash crashed with SIGSEGV in g_simple_async_result_complete()

StacktraceTop:g_vfs_job_emit_finished (job=0x0) at gvfsjob.c:323
send_reply_cb (source_object=0x84b9568, res=0x84df090,
IA__g_simple_async_result_complete (simple=0x84df090)
complete_in_idle_cb (data=0x84df090)
g_idle_dispatch (source=0x84c8a98, callback=0x84ca778,

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=576731

I tried to empty Trash and there was an immediate crash.

As files were displaying, trash crashed (sorry for the goofy rhyme ;) )

I'm not sure if I'm having the same problem, but Nautilus crashes constantly when emptying the trash on Ubuntu 9.10 64-bit. There is no crash report but I do see something like this in my system log immediately after:

kernel: [271660.316416] gvfsd-trash[26882]: segfault at 28 ip 0000000000411e14 sp 00007fffdc55c5c0 error 4 in gvfsd-trash[400000+25000]
kernel: [271683.371537] nautilus[26820]: segfault at 8 ip 00000000005041ce sp 00007fffdd025c60 error 4 in nautilus[400000+1b3000]

Oddly enough, once it happens the first time it doesn't happen again until after I've logged out and then logged back in.

This bug seems to still be here in Ubuntu 11.04 as well.... :)

[32123.423470] show_signal_msg: 15 callbacks suppressed
[32123.423481] gvfsd-trash[1642]: segfault at 28 ip 00000000004113f4 sp 00007fffeccb13b0 error 4 in gvfsd-trash[400000+26000]
[33261.690786] nautilus[1581]: segfault at 18 ip 00000000004d4b0e sp 00007fffcd5567d0 error 4 in nautilus[400000+1c6000]

I don't remember at what point the crash occurred, or what exactly I did with Nautilus before the crash.

Ubuntu 11.04 64bit

[40333.440566] gvfsd-trash[18056]: segfault at 28 ip 00000000004113f4 sp 00007fff81e354f0 error 4 in gvfsd-trash[400000+26000]

got this while trying to empty trash [126 folders and 447 items = total 13.1GB]

After that Trash became inaccessible from Nautilus.

From command line I can tell that indeed Trash is now empty:

~$ du -h .local/share/Trash/
4.0K .local/share/Trash/files
4.0K .local/share/Trash/expunged
144K .local/share/Trash/info
156K .local/share/Trash/

I just got this bug in 12.04 beta 2, while trying to empty the trash. The name that the crash detector proposed was exactly the name of this bug, so I didn't submit it as a new bug.

Same bug as I am getting except i am on 64bit sys using 12.04lts b2.

This bug was fixed in the package gvfs - 1.12.0-0ubuntu5

---------------
gvfs (1.12.0-0ubuntu5) precise; urgency=low

  * debian/patches/metadata-dont-flush-null-tree.patch:
    - Don't try to flush a tree that doesn't exist. Fixes crash bug
      LP: #405432. Patch from upstream's Christian Kellner.
  * debian/patches/metadata-nuke-junk-data.patch:
    - If metadata file is bogus, erase it and start over. Related to
      above bug, to be able to recover from junk data in addition to
      not crashing. Patch from upstream's Christian Kellner.
  * debian/patches/dont-crash-on-null-job.patch:
    - Don't try to announce the finish of a NULL job. LP: #345754,
      LP: #838464
  * debian/patches/check-gdu-pool.patch:
    - If gdu_pool_new() returns NULL, handle it gracefully.
      LP: #832379
  * debian/patches/handle-inactive-vfs.patch:
    - If the VFS never initialized, don't crash when creating volume
      monitors. LP: #832533
 -- Michael Terry <email address hidden> Wed, 11 Apr 2012 16:01:32 -0400