Bug 684254

Summary: Nautilus fails to connect to secure webdav server
Product: [Fedora] Fedora Reporter: Jonathan Underwood <jonathan.underwood>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: alexl, bnocera, ccecchi, jon, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 16:06:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jonathan Underwood 2011-03-11 15:32:28 UTC
Description of problem:
I am trying to connect to a secure webdav (davs://) server. This works using gnomevfs

eg. gnomevfs-ls davs://USERNAME.ac.uk/plugins/servlet/confluence/default/Global/PhysAstTheoryGrpComp/

returns a listing successfully. But when I try and open the same location within Nautilus, after entering my password, nothing happens for a while, and then eventually I get dialogue box pop up with the message:

Could not open location 'davs://USERNAME.ac.uk/plugins/servlet/confluence/default/Global/PhysAstTheoryGrpComp'

DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Version-Release number of selected component (if applicable):
rpm -qa | grep nautilus
brasero-nautilus-2.32.0-1.fc14.x86_64
nautilus-sendto-2.32.0-1.fc14.x86_64
totem-nautilus-2.32.0-1.fc14.x86_64
evince-nautilus-2.32.0-3.fc14.x86_64
nautilus-extensions-2.32.2.1-2.fc14.x86_64
nautilus-2.32.2.1-2.fc14.x86_64

rpm -qa | grep gnomevfs
gnome-python2-gnomevfs-2.28.1-3.fc14.x86_64

rpm -qa | grep vfs
gvfs-afc-1.6.6-1.fc14.x86_64
gvfs-gphoto2-1.6.6-1.fc14.x86_64
gnome-python2-gnomevfs-2.28.1-3.fc14.x86_64
gvfs-smb-1.6.6-1.fc14.x86_64
gvfs-obexftp-1.6.6-1.fc14.x86_64
gnome-vfs2-2.24.4-1.fc14.x86_64
gvfs-archive-1.6.6-1.fc14.x86_64
gvfs-1.6.6-1.fc14.x86_64
gvfs-fuse-1.6.6-1.fc14.x86_64


How reproducible:
Everytime

Comment 1 Tomáš Bžatek 2011-03-11 16:33:49 UTC
That's a gvfs issue, backend crashing. You should see a segfault in dmesg or abrt. Or, it might be a gnome-keyring issue we've fixed recently. Anyway, backtrace of the crash would be great to have.

There are known crashes in the dav backend due to race condition in avahi.

Comment 2 Jonathan Underwood 2011-03-17 12:38:44 UTC
Well, oddly enough, there's nothing in dmesg, /var/log/messages, and abrt doesn't report any segfault or crash. I'm not sure how to debug this further...

Comment 3 Jon Phillips 2012-06-24 04:33:41 UTC
I'm seeing the same issue. This is annoying.

I see this on F17 with:

$ rpm -qa | grep nautilus
nautilus-devel-3.4.2-5.fc17.x86_64
file-roller-nautilus-3.4.2-1.fc17.x86_64
evince-nautilus-3.4.0-2.fc17.x86_64
nautilus-python-1.1-2.fc17.x86_64
nautilus-extensions-3.4.2-5.fc17.x86_64
seahorse-nautilus-3.4.0-2.fc17.x86_64
rabbitvcs-nautilus-0.15.0.5-1.fc17.x86_64
nautilus-3.4.2-5.fc17.x86_64
nautilus-sendto-3.0.2-2.fc17.x86_64

$ rpm -qa | grep gnomevfs
gnome-python2-gnomevfs-2.28.1-8.fc17.x86_64

$ rpm -qa | grep vfs
gnome-python2-gnomevfs-2.28.1-8.fc17.x86_64
davfs2-1.4.6-3.fc17.x86_64
gvfs-1.12.3-1.fc17.x86_64
gvfs-gphoto2-1.12.3-1.fc17.x86_64
gvfs-obexftp-1.12.3-1.fc17.x86_64
gvfs-archive-1.12.3-1.fc17.x86_64
gnome-vfs2-2.24.4-7.fc17.x86_64
gvfs-fuse-1.12.3-1.fc17.x86_64
gvfs-afc-1.12.3-1.fc17.x86_64
gvfs-afp-1.12.3-1.fc17.x86_64
gvfs-smb-1.12.3-1.fc17.x86_64


###

I'm getting the same error. gnomevfs-ls totally working for me.

Comment 4 Fedora End Of Life 2012-08-16 16:06:18 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping