Bug 99890 - Two recovered documents get the same name
Summary: Two recovered documents get the same name
Status: RESOLVED DUPLICATE of bug 96607
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.3.2 release
Hardware: All Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-16 18:23 UTC by debbiecusick
Modified: 2016-06-06 00:07 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description debbiecusick 2016-05-16 18:23:04 UTC
I am a new user of LibreOffice, just installed yesterday. Today I used it for the first time. I had two documents open which I;ll call A.docx and B.docx. A.docx was an older document that I opened use as a template for the new one. I opened it and said "save as B.docx". That was I still had the original A.docx, and a new copy called B.docx which I began to modify, doing occasional saves as I went along. Then at one point LibreOffice Writer just crashed on me - just as I was trying to hit Save again. When I restarted it asked me if I wanted to recover B.docx. 

When the recovery finished I clicked to open B.docx, and that's when things got weird. Both A.docx and B.docx opened up. Except that A.docx (which I had not modified at all) now contained all the data I had inputted to B.docx - at least up to the point at which I had last saved (not recently enough, alas). And B.docx appeared to be almost the plain vanilla original A.docx, except it also had a couple of the changes I had made to B.docx. As an example the two documents were minutes of meetings, and the A meeting was April 1 and the B meeting was May 6. I had changed B to May 6 when I began to make my mods, but had never touched A. Yet when A opened after the recovery it showed May 6 as it's date, and also had the data from B, and when B opened it also showed the date as May 6 and the opening paragraph from B, but otherwise contained the correct A data. 

To recover I had to completely delete B (since it was just a corrupted version of A) since I was able to download a new A from Google drive, and then had to rename A back to its correct name of B, and re-input all the data I had put in after my last save but prior to the crash. 

It was as if the two documents swapped their names and then also mashed some of their data together. so completely bizarre that I struggle to explain it. Sorry I didn't think to save the files to submit. I was just in a hurry to try to resolve. But now I'm hitting Save on my doc every 30 seconds!
Comment 1 Buovjaga 2016-05-18 07:35:09 UTC
1. Created document A.docx with content "aaaa"
2. Copied it to B.docx, opened and added more content
3. Had autorecovery info save time as 2 minutes and waited for it to be saved
4. Simulated crash by killing soffice.bin forcefully
5. Opened LibO again and did recovery

No strangeness observed.

Win 7 Pro 64-bit Version: 5.2.0.0.alpha1+
Build ID: f688acfdae00ebdd891737e533d54368810185e1
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2016-05-18_00:11:31
Locale: fi-FI (fi_FI)
Comment 2 Aron Budea 2016-05-31 03:49:07 UTC
(In reply to Buovjaga from comment #1)
> 1. Created document A.docx with content "aaaa"
> 2. Copied it to B.docx, opened and added more content
> 3. Had autorecovery info save time as 2 minutes and waited for it to be saved
> 4. Simulated crash by killing soffice.bin forcefully
> 5. Opened LibO again and did recovery

I repeated these steps with this alternation:
2. Used Saved As... to save as B.docx, added more content (some unsaved), opened A.docx, added more content (all unsaved)

Results:
-both recovered documents were named A.docx, (bug)
-content was correct in both documents. (not bug)

Tested in LO 5.1.3.2, Windows 7.
Comment 3 Aron Budea 2016-06-06 00:07:22 UTC
Just noticed this is most likely the duplicate of bug 96607. Some things are definitely wrong with Save as... + autosave/recovery.

*** This bug has been marked as a duplicate of bug 96607 ***