gvfsd-trash crashed with SIGSEGV in g_main_context_prepare()

[John Vivirito]

Binary package hint: gvfs

when i started gnome + irssi i got a few apps crash on me gvfs trash crashed, anymore info needed please let me know. on a side note i doubt this is related to bug #185726 since it was filed against gvfsd-computer

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Disassembly: 0xb739b0d9:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
NonfreeKernelModules: nvidia
Package: gvfs-backends 0.99.4-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.7 /org/gtk/gvfs/exec_spaw/2
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:
 ?? ()
 g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_loop_run () from /usr/lib/libglib-2.0.so.0
 ?? ()
Title: gvfsd-trash crashed with SIGSEGV in g_main_context_prepare()
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Apport retracing service (apport)]

StacktraceTop:?? ()
IA__g_main_context_prepare (context=0x911a210, priority=0xbfa953b8)
g_main_context_iterate (context=0x911a210, block=1, dispatch=1, self=0x9111778)
IA__g_main_loop_run (loop=0x911a868) at /build/buildd/glib2.0-2.17.6/glib/gmain.c:2928
daemon_main (argc=4, argv=0xbfa95534, max_job_threads=10, default_type=0x8061d06 "trash",

[Sebastien Bacher (seb128)]

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

[John Vivirito (gnomefreak)]

that bug crashed with gvfsd-trash crashed with SIGSEGV in g_main_context_dispatch()
how is that the same as gvfsd-trash crashed with SIGSEGV in g_main_context_prepare()
that looks like they crash on different functions

[Sebastien Bacher (seb128)]

those crashes are likely the same issue, the stacktrace are not really informative but having a valgrind log would be useful