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 659592 - gvfsd-http crashed with SIGSEGV in g_settings_get_child()
gvfsd-http crashed with SIGSEGV in g_settings_get_child()
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: general
1.9.x
Other Linux
: Normal critical
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2011-09-20 14:05 UTC by Pedro Villavicencio
Modified: 2018-09-21 17:11 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Pedro Villavicencio 2011-09-20 14:05:47 UTC
this report has been filed here:

https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/839828

crash seems to be happening after a restart, backtrace as follow:

".

Thread 1 (Thread 0x7f3f404fe7c0 (LWP 4242))

  • #0 g_settings_schema_get_string
    at /build/buildd/glib2.0-2.29.18/./gio/gsettingsschema.c line 254
  • #1 g_settings_get_child
    at /build/buildd/glib2.0-2.29.18/./gio/gsettings.c line 2275
  • #2 g_proxy_resolver_gnome_init
    at gproxyresolvergnome.c line 175
  • #3 g_type_create_instance
    at /build/buildd/glib2.0-2.29.18/./gobject/gtype.c line 1885
  • #4 g_object_constructor
    at /build/buildd/glib2.0-2.29.18/./gobject/gobject.c line 1629
  • #5 g_object_newv
    at /build/buildd/glib2.0-2.29.18/./gobject/gobject.c line 1412
  • #6 g_object_new
    at /build/buildd/glib2.0-2.29.18/./gobject/gobject.c line 1322
  • #7 get_default_proxy_resolver
    at /build/buildd/glib2.0-2.29.18/./gio/gproxyresolver.c line 88
  • #8 g_once_impl
    at /build/buildd/glib2.0-2.29.18/./glib/gthread.c line 1064
  • #9 soup_proxy_resolver_gnome_init
    at soup-proxy-resolver-gnome.c line 30
  • #10 g_type_create_instance
    at /build/buildd/glib2.0-2.29.18/./gobject/gtype.c line 1885
  • #11 g_object_constructor
    at /build/buildd/glib2.0-2.29.18/./gobject/gobject.c line 1629
  • #12 g_object_newv
    at /build/buildd/glib2.0-2.29.18/./gobject/gobject.c line 1412
  • #13 g_object_new
    at /build/buildd/glib2.0-2.29.18/./gobject/gobject.c line 1322
  • #14 g_vfs_backend_http_init
    at gvfsbackendhttp.c line 98
  • #15 g_type_create_instance
    at /build/buildd/glib2.0-2.29.18/./gobject/gtype.c line 1885
  • #16 g_object_constructor
    at /build/buildd/glib2.0-2.29.18/./gobject/gobject.c line 1629
  • #17 g_vfs_backend_constructor
    at gvfsbackend.c line 265
  • #18 g_object_newv
    at /build/buildd/glib2.0-2.29.18/./gobject/gobject.c line 1493
  • #19 g_object_new_valist
    at /build/buildd/glib2.0-2.29.18/./gobject/gobject.c line 1610
  • #20 g_object_new
    at /build/buildd/glib2.0-2.29.18/./gobject/gobject.c line 1325
  • #21 g_vfs_daemon_initiate_mount
    at gvfsdaemon.c line 1073
  • #22 daemon_start_mount
    at gvfsdaemon.c line 881
  • #23 daemon_message_func
    at gvfsdaemon.c line 983
  • #24 dbus_connection_dispatch
    at ../../dbus/dbus-connection.c line 4603
  • #25 message_queue_dispatch
    at dbus-gmain.c line 127
  • #26 g_main_dispatch
    at /build/buildd/glib2.0-2.29.18/./glib/gmain.c line 2442
  • #27 g_main_context_dispatch
    at /build/buildd/glib2.0-2.29.18/./glib/gmain.c line 3011
  • #28 g_main_context_iterate
    at /build/buildd/glib2.0-2.29.18/./glib/gmain.c line 3089
  • #29 g_main_loop_run
    at /build/buildd/glib2.0-2.29.18/./glib/gmain.c line 3297
  • #30 daemon_main
    at daemon-main.c line 295
  • #31 main
    at daemon-main-generic.c line 39

Comment 1 Tomas Bzatek 2011-09-21 17:22:44 UTC
This is coming from libsoup back to GIO: g_proxy_resolver_gnome_init(). Kinda weird, I would expect g_log() in the trace on incorrect GSettings usage (or schema missing)...
Comment 2 GNOME Infrastructure Team 2018-09-21 17:11:02 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/172.