Hello!

Fedora 14 (Laughlin)
KDE 4.5.3

Situation:
1. Open the network file OpenOffice.org or, for example, drawing in Gimp.
2. Making changes to a file.
3. Close the file.
4. Changes are not saved in the event that is open another instance of the program. And only after the complete closure application changes are downloaded to the server using kioexec.
This situation is particularly critical when running a quick start OpenOffice.org. Changes are not saved as a quick strart keeps in memory a copy of soffice.
How to solve a similar problem without the use of mounted network drives?

Thank you.

In Konsole, if you pass the full network path to oowriter, is it able to open the file without issues?

If I type in console:

Code: Select all

[Karymov@karymov ~] $/usr/bin/oowriter fish://karymov@X.X.X.X:22/home/karymov/Test.odt


The result - "Operation not supported by the operating system."

If I connect to a remote machine in midnight commander, and open the file over the network, it is copied into the folder /tmp/mc-karymov/ and remains there. Changes are not uploaded to the server after file is closed.

Unfortunately in this case, your only option is to mount the file system, to get the behavior you desire.

Use the last chance Maybe I inaccurately described the problem. Here is an illustration with an explanation. Still, the only way to mount?
Thank you!

In this case, it depends on the application.

If it does not support KIO (all KDE applications do) and uses a single process (like OpenOffice does) then it will encounter problems for all files opened after the first instance of it is launched.

This is because KIO, in order to support non-KIO supporting applications, copies the file to the local machine, then launches the app with the local file. Once the app closes, the file is copied back if it has been changed.

This is what causes your problem, as OpenOffice simply "forks" itself to the parent process if it -is not the first instance to be started. This is the case with a second file or QuickStart.

The only workaround for this unfortunately is to either use KIO supporting applications, or to mount the share locally.

Thank you very much. Topic can be marked as solved.