Bug 151708 - Unsaved documents are no longer recovered [recovered as empty documents with the status (Remote)]
Summary: Unsaved documents are no longer recovered [recovered as empty documents with ...
Status: NEEDINFO
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: AutoSave-AutoRecovery-Backup
  Show dependency treegraph
 
Reported: 2022-10-23 05:08 UTC by Matt
Modified: 2024-05-31 03:15 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
setup to reproduce (246.59 KB, image/jpeg)
2022-10-23 05:12 UTC, Matt
Details
saved file (194.39 KB, image/jpeg)
2022-10-23 05:13 UTC, Matt
Details
unsaved file (234.60 KB, image/jpeg)
2022-10-23 05:15 UTC, Matt
Details
End LibreOffice task using Task Manager (59.44 KB, image/jpeg)
2022-10-23 05:17 UTC, Matt
Details
recovery begins (53.89 KB, image/jpeg)
2022-10-23 05:18 UTC, Matt
Details
recovery says that it's successful (48.92 KB, image/jpeg)
2022-10-23 05:19 UTC, Matt
Details
saved file is recovered (203.83 KB, image/jpeg)
2022-10-23 05:20 UTC, Matt
Details
unsaved files are NOT recovered (133.96 KB, image/jpeg)
2022-10-23 05:21 UTC, Matt
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matt 2022-10-23 05:08:59 UTC
Description:
L/O Writer (vers 7.4.2.3) is no longer recovering unsaved files.  I do not know when I first noticed that it does not, but it has been several months (several versions earlier).  Finally, I uninstalled the current version, and installed two old versions (7.0.0.0 and 7.1.0.0) that I was reasonably sure did not have the problem because they were before I encountered the problem.  However, upon installing the old versions, they had the same problem, so now I am baffled.  After uninstalling them, and reinstalling 7.4.2.3, the problem still exists.


Steps to Reproduce:
Step 0 – Setup
I have one saved document (in a folder on the Desktop), and 4 unsaved, open documents (pic 01).  There is the saved document (named document 1.odt) (pic 02)  I have pics of unsaved documents (pics 03-06) all filled with text.  

Step 1 – End task
Then I kill LibreOffice using “End task” on Task Manager (pic 07).  I have used this often, with unsaved documents always being recovered upon restarting LibreOffice.  

Step 2 – Restart LibreOffice
Now, when I restart LibreOffice (pic 08), it looks like it is going to recover the documents.  I click “Start” which brings up a screen that says that all documents were “Successfully recovered” (pic 09).

Step 3 – View the results


Actual Results:
When you look at the "recovered" documents, the saved document looks good (pic 10), but all of the unsaved documents are empty with the text “(Remote)” added to the temporary, unsaved document name (pics 11-14). 

Expected Results:
I would expect all recovered documents to be as they were before.


Reproducible: Always


User Profile Reset: No

Additional Info:
This is my first bug report to LibreOffice.  

Safe Mode did not resolve the problem.  It didn't try to recover documents at all.  So, as instructed, I did not try to "reset" UserProfile.
Comment 1 Matt 2022-10-23 05:12:41 UTC
Created attachment 183205 [details]
setup to reproduce
Comment 2 Matt 2022-10-23 05:13:31 UTC
Created attachment 183206 [details]
saved file
Comment 3 Matt 2022-10-23 05:15:03 UTC
Created attachment 183207 [details]
unsaved file
Comment 4 Matt 2022-10-23 05:17:19 UTC
Created attachment 183208 [details]
End LibreOffice task using Task Manager
Comment 5 Matt 2022-10-23 05:18:16 UTC
Created attachment 183209 [details]
recovery begins
Comment 6 Matt 2022-10-23 05:19:12 UTC
Created attachment 183210 [details]
recovery says that it's successful
Comment 7 Matt 2022-10-23 05:20:06 UTC
Created attachment 183211 [details]
saved file is recovered
Comment 8 Matt 2022-10-23 05:21:02 UTC
Created attachment 183212 [details]
unsaved files are NOT recovered
Comment 9 Matt 2022-10-23 05:25:21 UTC
Pic numbers in description no longer relate to attachments.  

There should be a way to edit the bug report, but I don't see one.
Comment 10 Robert Großkopf 2022-11-13 07:50:41 UTC
You saved one file before killing the process. Did you changed content after you have saved something in the file? Is this new content also available in the recovered document?

Have tested this and no new content was available here.

What did you choose in Tools → Options → Load/Save → General → Save AutoRecovery Information every: … minutes?
Have set this to 2 minutes, waited 3 minutes after changing content or created a new unsaved document with new content.
All unsaved content is there, also the content of the unsaved document.

Tested with 
Version: 7.4.3.1 / LibreOffice Community
Build ID: 3793858a34d8fef5b92f8fee233f97766f05e281
CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded

So I can't confirm a buggy behavior here.
Comment 11 Matt 2022-11-18 03:34:14 UTC
(In reply to Robert Großkopf from comment #10)
> You saved one file before killing the process. Did you changed content after
> you have saved something in the file? Is this new content also available in
> the recovered document?
--------------------------------------------------------------
RESPONSE:
Changed information in "saved file" is also lost.  
--------------------------------------------------------------
> 
> Have tested this and no new content was available here.
> 
> What did you choose in Tools → Options → Load/Save → General → Save
> AutoRecovery Information every: … minutes?
> Have set this to 2 minutes, waited 3 minutes after changing content or
> created a new unsaved document with new content.
> All unsaved content is there, also the content of the unsaved document.
> 
--------------------------------------------------------------
RESPONSE:
Did not change AutoRecovery minutes from default.  Is set at 10 minutes, however  default is not activated.  Activated, retested, no change.  Still receiving original problem results.  

Using default settings, problem did not previously exist.
--------------------------------------------------------------

> Tested with 
> Version: 7.4.3.1 / LibreOffice Community
> Build ID: 3793858a34d8fef5b92f8fee233f97766f05e281
> CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb)
> Locale: de-DE (de_DE.UTF-8); UI: en-US
> Calc: threaded
> 
> So I can't confirm a buggy behavior here.

--------------------------------------------------------------
RESPONSE:
The screenshots that I provided prove buggy behavior.  These results were with a clean install of: 
Version 7.4.2.3 (Current Release)
Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf
Windows 10 current version
--------------------------------------------------------------
Comment 12 Justin L 2023-07-19 12:35:12 UTC
Matt, these recovery files should be saved in (I think) %APPDATA%\libreoffice\4\user\backup. You should be able to inspect them before you crash LO. Make a note of the file's timestamp for each of these recovery files before you crash LO. (LO does attempt to save files before an emergency shutdown - perhaps that is failing if it does manage to run at all in this case?)

Any idea why LO might think you are dealing with remote files? Is your profile on a network? Are you dealing with webdav or any server based storage?

I could not reproduce
-opened a file from desktop and made modifications
-started 4 new documents and filled with text ("lorem", then press F3)
-wait until autosave timer kicked in - saw 
instdir/user/backup
-rw-------  1 user user 12895 Jul 19 08:28 junk.docx_0.odt
-rw-------  1 user user 35448 Jul 19 08:29 untitled_0.odt
-rw-------  1 user user 35446 Jul 19 08:29 untitled_1.odt
-rw-------  1 user user 35451 Jul 19 08:29 untitled_2.odt
-rw-------  1 user user 35447 Jul 19 08:29 untitled_3.odt

-Ctrl-C to end my development run. Restarted LO and all 5 documents recovered OK
Comment 13 Stéphane Guillou (stragu) 2023-07-21 08:15:59 UTC
Maybe related to bug 95229
Comment 14 Buovjaga 2023-12-02 15:54:46 UTC
Is this the same as bug 124213? Said to be a regression from around 5.2
Comment 15 QA Administrators 2024-05-31 03:15:24 UTC Comment hidden (spam)