https://bugs.documentfoundation.org/show_bug.cgi?id=161977
Bug ID: 161977
Summary: Backup folder - if access revoked or cannot read/write
- then it's impossible to save file and all changes is
lost.
Product: LibreOffice
Version: 7.6.7.2 release
Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: [email protected]
Reporter: [email protected]
First - I haven't being able to reproduce the issue.
Before I even begin, let me just start to inform that the location of the LibO
backup folder are placed on a shared network drive, and I know from before that
this particular network drive has caused issues in the past, also to other
programs - probably because it can fail when a program try to write to it. It
can periodically fail for some seconds and then suddenly of itself get to work
like nothing happens, and can read and write to it normally.
Therefore I assume the solution is probably in the way LibO respond in a case
where the backup folder for some reason stop to allow processes to read/write
to it.
So I'd put this as a feature request because I don't think it's a bug (never
happens when I use Linux at home).
Version: 7.6.7.2 (x86) / LibreOffice Community
Build ID: dd47e4b30cb7dab30588d6c79c651f218165e3c5
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win
Locale: nb-NO (nb_NO); UI: en-US
Calc: CL threaded
Steps to reproduce:
* Have the LibO backup location to an unstable network drive.
* Use LibO normally for a long time, but if and when there is r/w issues to the
backup location, then:
* Open file
* Save file as another file name
- Save file : this will cause a generic message that says "document cannot be
saved" (unfortunately I lost the printscreen for that message and can only
reply as I remembered it worded)
- Save as : Same result, get the same error message and cannot save the file.
- Save as to another location (to a known working usb drive) - same result,
LibO fails to create the files with the changes.
- In the LibO backup dir, only a copy of the file as it was when saved the
first time is located there. That means all changes to the file (spend half an
hour) is lost and there is nothing I can do to correct this. This suggest there
is a problem to the backup directory itself (my theory).
After I closed LibO and opened again, I was able to save and save as normally
without any issues.
Suggested solution: When the backup folder for some reason disconnects, LibO
should be able to pick up on that instead of preventing the current opened file
to be written to.
--
You are receiving this mail because:
You are the assignee for the bug.
