gvfsd-trash crashed with SIGSEGV in IA__g_file_equal()

[Jamie Strandboge]

Binary package hint: gvfs

Computer was sitting idling overnight, and when I sat down at it this morning, gvfsd-trash had crashed.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
Package: gvfs 1.1.6-0ubuntu1
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.5 /org/gtk/gvfs/exec_spaw/1
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 IA__g_file_equal (file1=0x18904c0, file2=0x1886e80)
 ?? ()
 IA__g_closure_invoke (closure=0x1888dc0,
 signal_emit_unlocked_R (node=0x1861a90, detail=0,
 IA__g_signal_emit_valist (instance=0x1889460,
Title: gvfsd-trash crashed with SIGSEGV in IA__g_file_equal()
Uname: Linux 2.6.28-8-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm libvirtd lpadmin plugdev pulse pulse-access pulse-rt scanner video

[Apport retracing service (apport)]

StacktraceTop:IA__g_file_equal (file1=0x18904c0, file2=0x1886e80)
dir_watch_parent_changed (
IA__g_closure_invoke (closure=0x1888dc0,
signal_emit_unlocked_R (node=0x1861a90, detail=0,
IA__g_signal_emit_valist (instance=0x1889460,

[Sebastien Bacher (seb128)]

could be the same issue than bug #332554

[Allison Karlitskaya (desrt)]

i'm quite certain this is the same as bug 332554

that '??' appearing in the stack trace is almost certainly dir_watch_parent_changed() since this is a signal handler that calls g_file_equal().