| Summary: | Non-kde programs cannot write files to kioslave's folders, sometimes they cannot even read | ||
|---|---|---|---|
| Product: | [Unmaintained] kio | Reporter: | Kamil Neczaj <kneczaj> |
| Component: | general | Assignee: | David Faure <faure> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | CC: | antonis+kdebugs, aria, loonyphoenix, nf2.email, rayanAyar, toddrme2178, turist |
| Priority: | NOR | ||
| Version: | 4.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
The idea was discussed in kde-brainstorm forum, and guys told me that there is already kiofuse project, which exactly do what I said - http://techbase.kde.org/Projects/KioFuse KioFuse needs development, because now it's not complete and integration with kde to mount resources transparently, without using CLI. I've forgotten, it's the link to the kde-brainstorm topic: http://forum.kde.org/kde-brainstorm-f-83-2.html So assign this to the kio-fuse people... Personally I have enough work with KDE programs already, non-KDE programs are not the priority ;-) (btw gimp can still be started with a file from a kioslave, kde will take care of downloading the file first into a tempfile and uploading after modifications. It's just File/Open inside gimp itself that can't work this way.) For me gimp cannot open file from ftp:/ using kioslave. I have an error: Could not open 'ftp://kneczaj@ftp.republika.pl:21/DSC_0278.JPG' for reading: Login denied Gedit also cannot even open the file. Error message translated to english: "Can't open file: ftp://kneczaj@ftp.republika.pl:21/smb.conf. Gedit cannot handle ftp:/ protocol" Openoffice haven't any problems. Read as well as write works. Before reading kde ask me one more time for password to ftp server and after saving in openoffice ask whether I want to save file as you said. The fuse is only proposed solution for the errors. In my opinion the best. Well - as GVFS provides this FUSE feature already - and because having a single VFS subsystem might be quite beneficial for lots of reasons, something like this might also be an option: http://live.gnome.org/KioGioBridge *** This bug has been confirmed by popular vote. *** Kiofuse (and KioGioBridge) is dead (no activity since 5 years). Maybe it’s time to reopen. |
Version: (using KDE 4.2.0) OS: Linux Installed from: Unlisted Binary Package For egzample gimp cannot read images from ftp and kioslave. In my opinion gnome's solution, which use gvfs is really good. Gvfs creates fuse file system, and mount it in ~/.gvfs. Then every resource, which is using via gvfs have its folder created in ~/.gvfs directory. When user try to open a document, the program which he is using get path to file mounted in ~/.gvfs directory, so there's no problem to read the file. The real advantage of this solution is the fact that the whole resource is mounted in ~/.gvfs ("some_ftp" server has it's directory in ~/.gvfs/some_ftp, as I remember) so the user can write modified file there and even write it in different file or even different director in the same resource (server or device). It would be great if gvfs and kioslaves become compatible.