Description of problem: failure to gvfs-mount a password protected webdav share (I should get authentication prompt): [fabrice@e4310 ~]$ gvfs-mount davs://af18148h.fr/af18148h/prive Error mounting location: Message did not receive a reply (timeout by message bus) In order to help debugging this issue, gvfsd daemon was started before in debug mode and raised following messages at time of gvfs-mount: [fabrice@e4310 ~]$ kill $(ps -ef|grep [g]vfs|awk '{print $2}') [fabrice@e4310 ~]$ GVFS_DEBUG=1 GVFS_HTTP_DEBUG=all /usr/libexec/gvfsd -r 2>&1 Added new job source 0x1d8b230 (GVfsBackendDav) Queued new job 0x1d99ad0 (GVfsJobMount) + mount > OPTIONS /af18148h/prive HTTP/1.1 > Soup-Debug-Timestamp: 1359642874 > Soup-Debug: SoupSessionSync 1 (0x1da5840), SoupMessage 1 (0x7fddd4006080), SoupSocket 1 (0x1d9f640) > Host: dossier.univ-st-etienne.fr > Accept-Encoding: gzip, deflate > User-Agent: gvfs/1.14.2 > Accept-Language: fr-fr, fr;q=0.9 > Connection: Keep-Alive + soup_authenticate_interactive (first auth) ** (process:26756): WARNING **: Non-utf8 value for key object (process:26756): GLib-CRITICAL **: g_hash_table_insert_internal: assertion `hash_table != NULL' failed (process:26756): GLib-CRITICAL **: g_hash_table_iter_init: assertion `hash_table != NULL' failed ** (gvfsd:26745): WARNING **: dbus_mount_reply: Error from org.gtk.vfs.Mountable.mount(): Message did not receive a reply (timeout by message bus) Added new job source 0x20d3230 (GVfsBackendDav) Version-Release number of selected component: gvfs-1.14.2-2.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-dav --spawner :1.286 /org/gtk/gvfs/exec_spaw/0 crash_function: g_hash_table_iter_next executable: /usr/libexec/gvfsd-dav kernel: 3.7.4-204.fc18.x86_64 remote_result: NOTFOUND uid: 1000 var_log_messages: Jan 31 15:34:35 e4310 abrt[26763]: Saved core dump of pid 26756 (/usr/libexec/gvfsd-dav) to /var/spool/abrt/ccpp-2013-01-31-15:34:35-26756 (35926016 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 g_hash_table_iter_next at ghash.c:769 #1 _secret_attributes_validate at secret-attributes.c:212 #2 secret_service_search_sync at secret-methods.c:460 #3 g_vfs_keyring_lookup_password at gvfskeyring.c:183 #4 soup_authenticate_interactive at gvfsbackenddav.c:1512 #13 soup_auth_manager_emit_authenticate at soup-auth-manager.c:169 #14 authenticate_auth at soup-auth-manager.c:418 #19 soup_message_got_headers at soup-message.c:1062 #20 io_read at soup-message-io.c:568 #21 io_run_until at soup-message-io.c:828
Created attachment 690956 [details] File: backtrace
Created attachment 690957 [details] File: cgroup
Created attachment 690958 [details] File: core_backtrace
Created attachment 690959 [details] File: dso_list
Created attachment 690960 [details] File: environ
Created attachment 690961 [details] File: limits
Created attachment 690962 [details] File: maps
Created attachment 690963 [details] File: open_fds
Created attachment 690964 [details] File: proc_pid_status
Workaround found on apache server side, replacing the accented character ("é") by a regular one ("e"): < AuthName "Cartable priv� de Allibe Fabrice" --- > AuthName "Cartable prive de Allibe Fabrice" Now glib is no longer crashing, and we are getting a normal authentication prompt which ends up successfully: [fabrice@e4310 ~]$ gvfs-mount davs://af18148h.fr/af18148h/prive Saisissez le mot de passe pour Cartable prive de Allibe Fabrice Password: [fabrice@e4310 ~]$ gvfs-mount -l Mount(0): af18148h sur dossier.univ-st-etienne.fr -> davs://af18148h.fr/af18148h Type: GDaemonMount
Anyway, a bug is hidding somewhere in glib/dbus/gvfs-dav components, which are unable to deal with some accented characters provided by webdav server... then ending up with segfault in libglib and gvfsd-dav killed by SIGSEGV.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.