- Open a file from a Windows shared folder.
- Severe the connection between the two computers (I just shut down the one with the share).
- Try to save the file.

=>
First what I'd like to see:
- If the save is to a network location (if that can be established), show a dialog that it's trying to establish connection, and let the user cancel it.
- After X seconds (10? 20? configurable parameter?) time out with an error, ask the user if they want to try again, if they do, attempt again with a longer, ~1-minute timeout.

What happens:
1. In 6.3 beta1 and a master debug build

The UI freezes, and after a minute you get a dialog:
"[Document Has Been Changed by Others]
The file has been changed since it was opened for editing in LibreOfficeDev. Saving your version of the document will overwrite changes mage by others.
Do you want to save anyway?"
=> Save Anyway

"[Error]
Error saving the document <file name>:
The operation on <file name with path> was started with an invalid parameter."
=> OK

The dialog stays, in the master build after a few more OKs, you get a debug error: abort() has been called.

In the 6.3 beta1 build, after ~3 OKs, you get a new dialog:
"[Document Could Not Be Locked]
The lock file could not be created for exclusive access by LibreOfficeDev, due to missing permission to create lock file on that location or lack of free disk space."
=> Open Read-Only

After a few seconds, there is the following error dialog:
"[Error]
Error saving the document <file name>:
Write Error.
The file could not be written."
=> OK

You are finally returned to the document.


2. In 5.0.0.5

The first result is the same ('Document Has Been Changed by Others').
However, after choosing 'Save Anyway', the second dialog is:
"Error saving the document <file name>:
The path <path> does not exist."

The next dialog is the error complaining about invalid parameter, and finally you are returned to the document.