gvfsd-trash crashed with SIGSEGV in g_idle_funcs()

[Savvas Radevic]

Binary package hint: gvfs

It just crashed, no info on how to reproduce it
Ubuntu intrepid ibex 8.10 alpha 5 (updated)

gvfs:
  Installed: 0.99.7.1-0ubuntu1
  Candidate: 0.99.7.1-0ubuntu1
  Version table:
 *** 0.99.7.1-0ubuntu1 0
        500 http://archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
Disassembly: 0x7fd0ff5c299c:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
NonfreeKernelModules: nvidia
Package: gvfs-backends 0.99.7.1-0ubuntu1
ProcAttrCurrent: /usr/share/gdm/guest-session/Xsession (enforce)
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.6 /org/gtk/gvfs/exec_spaw/0
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? () from /lib/libpthread.so.0
 ?? ()
 g_idle_funcs () from /usr/lib/libglib-2.0.so.0
 g_main_context_dispatch ()
Title: gvfsd-trash crashed with SIGSEGV in g_idle_funcs()
Uname: Linux 2.6.27-2-generic x86_64
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:?? ()
?? () from /lib/libpthread.so.0
?? ()
g_idle_funcs () from /usr/lib/libglib-2.0.so.0
IA__g_main_context_dispatch (context=0x152f190)

[Savvas Radevic (medigeek)]

Crashed once more, a few minutes after boot up and login.

$ dmesg
[ 28.596900] r8169: eth0: link up
[ 29.286462] NET: Registered protocol family 17
[ 39.312506] eth0: no IPv6 routers present
[ 57.489344] gvfsd-trash[6220]: segfault at 7f03d9a4399c ip 00007f03d9a4399c sp 00007fffe536c390 error 4 in libgvfsdbus.so[7f03da51d000+25000]

[Andreas Moog (ampelbein)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 252174, so it 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. Feel free to continue to report any other bugs you may find.