https://bugs.documentfoundation.org/show_bug.cgi?id=156747
Bug ID: 156747
Summary: Unsaved files not recovering on next launch.
Product: LibreOffice
Version: 7.5.4.2 release
Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: jd4...@hotmail.com
Description:
I am on version 7.5.4.2. I used to use version 5 couldnt say with sub version a
lot. And i use to open up a dozen or so documents at a time, write some notes.
Then i would turn off my computer, the next day, it would recover all those
files perfectly fine. I did this daily for ages without issue. Had to reinstall
windows recently and since then upgraded to the latest version and now it will
still show the recover option when i launch libre office writer, however it
just recovers a blank document with the (remote) in brackets, which again i
never had during version 5, i never saw (remote) anywhere. Yes i know it is my
fault for not saving however, this issue basically means the recovery system is
not working, and i do not know if existing documents i have recovered recently
have actually saved the changes or not, as i bounce between documents often i
forget what changes i made recently.
Steps to Reproduce:
1.turn off the computer with unsaved writer documents open.
2.turn on computer and open writer
3."successfully" recover those files, but instead it just opens blank remote
files
Actual Results:
Any unsaved documents show up in the recovery window and show successful
recovery but instead are replaced with empty (remote) documents and the unsaved
documents are lost.
Expected Results:
As before in version 5. whatever it should successfully recover the unsaved
documents, open them all back up with all the data still there as it used to.
Reproducible: Always
User Profile Reset: No
Additional Info:
[Information automatically included from LibreOffice]
Locale: en-GB
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: yes
I did not try resetting the user profile yet as i did not know that was a
thing, and to test properly would require restarting windows and that would
mean redoing this bug report, which is still relevant even if it ends up beign
a user profile corruption issue. If its possible to update and add more
information to this bug report later i can add to it if that did fix it.
--
You are receiving this mail because:
You are the assignee for the bug.
