Bug 185811 - Non-kde programs cannot write files to kioslave's folders, sometimes they cannot even read
Summary: Non-kde programs cannot write files to kioslave's folders, sometimes they can...
Status: RESOLVED DUPLICATE of bug 75324
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.2.0
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: David Faure
Depends on:
Reported: 2009-02-28 17:25 UTC by Kamil Neczaj
Modified: 2013-08-15 14:33 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Kamil Neczaj 2009-02-28 17:25:43 UTC
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.
Comment 1 Kamil Neczaj 2009-05-22 23:19:29 UTC
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.
Comment 2 Kamil Neczaj 2009-05-22 23:21:16 UTC
I've forgotten, it's the link to the kde-brainstorm topic: http://forum.kde.org/kde-brainstorm-f-83-2.html
Comment 3 David Faure 2009-05-23 03:05:14 UTC
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.)
Comment 4 Kamil Neczaj 2009-05-23 15:36:52 UTC
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.
Comment 5 nf2.email 2009-05-30 22:42:52 UTC
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:

Comment 6 Markus Torstensson 2009-11-08 18:37:29 UTC
*** This bug has been confirmed by popular vote. ***
Comment 7 Todd 2013-06-15 10:46:40 UTC

*** This bug has been marked as a duplicate of bug 75324 ***
Comment 8 ariasuni 2013-07-22 11:08:10 UTC
Kiofuse (and KioGioBridge) is dead (no activity since 5 years). Maybe it’s time to reopen.
Comment 9 Todd 2013-08-15 14:33:11 UTC
This bug has been marked as a duplicate.  Please post additional comments in bug 75324, which is still open.