KDE users have this problem several years ago. The most typical scenario is:  Linux KDE users accesing a Windows shared folder. If the user try to open a LibreOffice document from that shared folder, the file is copied to "/var/tmp/kdecache-USERNAME/krun/" so the user is not working in the remote folder and that's a big problem.

A typical reply to this is "LibreOffice is a gnome application, so the cause of this is that they don't include in the '.desktop' file the protocols that the application is supossed to accept". I then added "X-KDE-Protocols=file,http,smb,ftp,fish,webdav" to all LibreOffice ".desktop" files  ... but no changes at all!!!.

But let's go a step further away, and we can try to open a "PNG" image with a "native" KDE application, like Gwenview. In its "gwenview.desktop" there is no a "X-KDE-Protocols" line at all. Well, if I try to open a remote image with Krusader in a "ftp", "smb" or "fish" protocols folders, only the "ftp" folder is opened by gwenview remotely. "smb" and "fish" protocols remote folders simply copied to "/var/tmp ...." the remote opened file.

Then I appended  "X-KDE-Protocols=file,http,smb,ftp,fish,webdav" to "gwenview.desktop" file, and the same results. So, where is the problem with KDE and remote files? Is a distro related issue? Is a long time (2009) KDE bug? Are the users foolish? 

Really I can't recommend seriously Linux + KDE to any company without a solution to this problems.


Reproducible: Always

Steps to Reproduce:
1.Launch "dolphin" or "krusader"
2.Open a remote folder with protocols "smb" or "fish"
3.Open a image or a LibreOffice document from that folder

Actual Results:  
Selected file is not opened remotely, but copied to a local folder.

Expected Results:  
Open remote file directly, without copying to local folder (at least, in samba shared folders)

While this issue is not fixed, in a business environment is impossible to work seriously. Users have to try workaround that doesn't work and is a waste of time.