https://bugs.documentfoundation.org/show_bug.cgi?id=170297
Bug ID: 170297
Summary: Semaphore file not deleteted at close of a document on
a network drive (computer or NAS)
Product: LibreOffice
Version: 26.2.0.0 alpha0+ master
Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: [email protected]
Reporter: [email protected]
When an opened document on a network drive will be closed the semaphore file
(.~lock.xxx.odt# etc.) is not deleted.
I have reproduced the beavior with LO 26.2.0 beta and LO 26.8.0.0 alpha in
Writer and in Calc.
To reproduce the problem find or create a test document on a network ressource
and follow the cases described below. Additionally watch the entries in the
folder containing the test document - make show also hidden files!
- When the opened document was not changed before close the not deleted
semaphore file causes the document can be opened on other computers only
readonly. On the same computer (and by the same user?) it can be opened without
any problems.
- When the document was changed LO asks for save before close. Even if the user
decides to save the document or not the file attribute "readonly" is set. The
next time the document can be opened only readonly.
In case the user decides to "Save as" not the original file but the saved as
document gets the file attribute readonly.
When one tries to solve the problem by manually delete the semaphore file and
clear the readonly attribute there are other problems.
The document can be opened without any problems but when one tries to save the
document (with or without any changes) one gets error messages as "Fehler beim
Speichern des Dokuments xxx: / Kein Zugriff auf Objekt. / Aufgrund fehlender
Zugriffsrechte kann auf das Objekt nicht zugegriffen werden." (ger, en [lt.
Google]: "Error saving document xxx: / No access to object. / Due to
insufficient access rights, the object cannot be accessed.") - test with LO
26.8.0.0 alpha - or with LO 26.2 Beta also "Fehler beim Speichern des Dokuments
xxx: Fehler beim Erstellen des Objekts. / Sicherungskopie konnte nicht erstellt
werden." (ger, en: "Error saving document xxx: Error creating object. / Backup
could not be created.")
This behavior is already described in Bug 160484.
--
You are receiving this mail because:
You are the assignee for the bug.
