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 655427 - gvfsd-http crashed with SIGSEGV in g_variant_unref()
gvfsd-http crashed with SIGSEGV in g_variant_unref()
Status: RESOLVED DUPLICATE of bug 655366
Product: gvfs
Classification: Core
Component: http backend
1.9.x
Other Linux
: Normal critical
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2011-07-27 14:33 UTC by Pedro Villavicencio
Modified: 2011-10-03 13:27 UTC
See Also:
GNOME target: ---
GNOME version: 3.1/3.2



Description Pedro Villavicencio 2011-07-27 14:33:21 UTC
this report has been filed here:

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

".

Thread 1 (Thread 7726)

  • #0 g_variant_unref
    at /build/buildd/glib2.0-2.29.14/./glib/gvariant-core.c line 617
  • #1 g_settings_get_string
    at /build/buildd/glib2.0-2.29.14/./gio/gsettings.c line 1770
  • #2 update_settings
    at gproxyresolvergnome.c line 206
  • #3 g_proxy_resolver_gnome_lookup
    at gproxyresolvergnome.c line 463
  • #4 g_proxy_resolver_gnome_lookup_async
    at gproxyresolvergnome.c line 591
  • #5 get_proxy_uri_async
    at soup-proxy-resolver-default.c line 180
  • #6 run_queue
    at soup-session-async.c line 418
  • #7 idle_run_queue
    at soup-session-async.c line 441
  • #8 g_main_dispatch
    at /build/buildd/glib2.0-2.29.14/./glib/gmain.c line 2500
  • #9 g_main_context_dispatch
    at /build/buildd/glib2.0-2.29.14/./glib/gmain.c line 3083
  • #10 g_main_context_iterate
    at /build/buildd/glib2.0-2.29.14/./glib/gmain.c line 3161
  • #11 g_main_loop_run
    at /build/buildd/glib2.0-2.29.14/./glib/gmain.c line 3369
  • #12 daemon_main
    at daemon-main.c line 295
  • #13 main
    at daemon-main-generic.c line 39

Comment 1 Rodney Dawes 2011-10-03 13:27:01 UTC

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