After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 756885 - gvfsd crashes with error:0
gvfsd crashes with error:0
Status: RESOLVED DUPLICATE of bug 756105
Product: gvfs
Classification: Core
Component: daemon
1.24.x
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2015-10-20 19:53 UTC by Michael Orlitzky
Modified: 2015-10-20 23:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
core_backtrace from abrt (1.63 KB, text/plain)
2015-10-20 19:53 UTC, Michael Orlitzky
Details
backtrace from abrt (18.76 KB, text/plain)
2015-10-20 19:54 UTC, Michael Orlitzky
Details

Description Michael Orlitzky 2015-10-20 19:53:52 UTC
Created attachment 313772 [details]
core_backtrace from abrt

With gvfs-1.24.2, gvfsd is crashing on me. The main noticeable symptom is that everything using gvfs takes forever to start. I have log entries like,

Sep 15 21:43:25 [kernel] traps: gvfsd[2157] trap int3 ip:38b480f01f5 sp:3c99d55cd20 error:0

I first reported this at https://bugs.gentoo.org/show_bug.cgi?id=560592 and there's a tiny bit more info there, but I'm attaching my backtrace and core_backtrace from abrt here, too.
Comment 1 Michael Orlitzky 2015-10-20 19:54:17 UTC
Created attachment 313773 [details]
backtrace from abrt
Comment 2 Pacho Ramos 2015-10-20 20:13:13 UTC
[New LWP 2163]
[New LWP 2165]
[New LWP 2164]
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/libexec/gvfsd'.
Program terminated with signal SIGTRAP, Trace/breakpoint trap.

Thread 1 (Thread 0x3cb7d9f0700 (LWP 2163))

  • #0 _g_log_abort
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/glib/gmessages.c line 315
  • #1 g_logv
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/glib/gmessages.c line 1041
  • #2 g_log
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/glib/gmessages.c line 1079
  • #3 g_variant_valist_new_nnp
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/glib/gvariant.c line 4690
  • #4 g_variant_valist_new_leaf
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/glib/gvariant.c line 4846
  • #5 g_variant_valist_new
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/glib/gvariant.c line 5028
  • #6 g_variant_valist_new
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/glib/gvariant.c line 5080
  • #7 g_variant_new_va
  • #8 g_variant_new
  • #9 gvfs_dbus_daemon_complete_list_monitor_implementations
    at gvfsdbus.c line 1006
  • #10 handle_list_monitor_implementations
    at gvfsdaemon.c line 971
  • #11 ffi_call_unix64
    at /var/tmp/portage/dev-libs/libffi-3.0.13-r1/work/libffi-3.0.13/src/x86/unix64.S line 76
  • #12 ffi_call
    at /var/tmp/portage/dev-libs/libffi-3.0.13-r1/work/libffi-3.0.13/src/x86/ffi64.c line 522
  • #13 g_cclosure_marshal_generic
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/gobject/gclosure.c line 1448
  • #14 g_closure_invoke
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/gobject/gclosure.c line 768
  • #15 signal_emit_unlocked_R
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/gobject/gsignal.c line 3549
  • #16 g_signal_emitv
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/gobject/gsignal.c line 3044
  • #17 _gvfs_dbus_daemon_skeleton_handle_method_call
    at gvfsdbus.c line 1433
  • #18 g_dbus_interface_method_dispatch_helper
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/gio/gdbusinterfaceskeleton.c line 609
  • #19 skeleton_intercept_handle_method_call
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/gio/gdbusinterfaceskeleton.c line 650
  • #20 call_in_idle_cb
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/gio/gdbusconnection.c line 4884
  • #21 g_idle_dispatch
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/glib/gmain.c line 5393
  • #22 g_main_dispatch
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/glib/gmain.c line 3122
  • #23 g_main_context_dispatch
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/glib/gmain.c line 3737
  • #24 g_main_context_iterate
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/glib/gmain.c line 3808
  • #25 g_main_loop_run
    at /var/tmp/portage/dev-libs/glib-2.44.1/work/glib-2.44.1/glib/gmain.c line 4002
  • #26 main
    at main.c line 223

Comment 3 Ross Lagerwall 2015-10-20 23:15:12 UTC
This happens when there are no existing monitor implementations, which has happened because your configuration hasn't enabled any.

I've cherry-picked the commit that fixes this issue from master to the 1.24.x branch (GNOME 3.16):
https://git.gnome.org/browse/gvfs/commit/?h=gnome-3-16&id=c259305847b1ebde1ae89a3c921a13b6c0b67116

I'm not sure when (or if) there will be another 1.24.x release though but I expect that Gentoo can include this commit.

Thanks

*** This bug has been marked as a duplicate of bug 756105 ***