Description of problem: I can access a webdav share using nautilus. But when I try to open a file in the share, for example a video, I get an input/output error If I go to the mounted directory under /run/user/1000/gvfs/dav:host=host,port=5005,ssl=false,user=user/share I can cd to the different directories, but doing a ls returns I/O error accessing the files. Version-Release number of selected component (if applicable): gvfs-1.14.2-3.fc18.x86_64 How reproducible: Always Additional info: This worked in F17
We have ported dav and http backends to new libsoup infrastructure so things may be little different in F19. Any chance to test it there? Does the video player use GIO natively or it's going through gvfsd-fuse? Note that seeking may be a problem, also depends on server capabilities. Can you try gvfs-copy? (In reply to comment #0) > I can cd to the different directories, but doing a ls returns I/O error > accessing the files. Assuming directory listing works in Nautilus, right?
(In reply to comment #1) > We have ported dav and http backends to new libsoup infrastructure so things > may be little different in F19. Any chance to test it there? > I have just a laptop here... it's difficult that I install F19 in it > Does the video player use GIO natively or it's going through gvfsd-fuse? > Note that seeking may be a problem, also depends on server capabilities. > Its totem-3.6.3-2.fc18.x86_64, its seems linked with libgio-2.0.so.0 > Can you try gvfs-copy? > Yes, it works from desktop to webdav share and viceversa > (In reply to comment #0) > > I can cd to the different directories, but doing a ls returns I/O error > > accessing the files. > > Assuming directory listing works in Nautilus, right? Yes, it works
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This was fixed upstream in https://bugzilla.gnome.org/show_bug.cgi?id=706798
Can the upstream fix be backported?
gvfs-1.14.2-5.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/gvfs-1.14.2-5.fc18
Package gvfs-1.14.2-5.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gvfs-1.14.2-5.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-21825/gvfs-1.14.2-5.fc18 then log in and leave karma (feedback).
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.
Can the fix be pushed to stable?
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.