Bug 95787 - Recovery recovers "wrong" file.
Summary: Recovery recovers "wrong" file.
Status: RESOLVED DUPLICATE of bug 96607
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.0.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 95818 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-11-12 23:31 UTC by libreoffice
Modified: 2016-06-10 22:47 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:

Attachments
Buggy file with image. (14.20 KB, application/vnd.oasis.opendocument.text)
2015-11-12 23:31 UTC, libreoffice 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description libreoffice 2015-11-12 23:31:14 UTC 
Created attachment 120516 [details]
Buggy file with image.

Hello again!

While trying to print a document which caused an Libre Office Writer crash I discovered an unexpected behaviour - see bug report #95786.

I saved "Bug1.odt" as "Bug2.odt". In the title bar stood "Bug2.odt", too. Then I tried to print the document which caused Writer to crash. After restarting the application the crash recovery started. Instead of recovering "Bug2.odt" it said that it recovered "Bug.odt". I don't know what happens there because I can open bothe files without recovery.


In short: save as -> Writer crashes -> document recovery restores original document

Have a nice day.
Florian
Comment 1 Joel Madero 2015-11-13 04:21:27 UTC 
Bodhi 3.x (Ubuntu 14.04 with Enlightenment replacing Unity)
LibreOffice 5.0.4 developer build

Cannot reproduce.

Tested using these steps:
1) Started writer from terminal;
2) Wrote some text;
3) Saved as test1;
4) Typed a bit more;
5) Saved as test2;
6) Forced crash
7) Started writer again;

Recovery started - recovered "test2" as expected.
Comment 2 libreoffice 2015-11-15 15:03:47 UTC 
Today I had the chance to test it on my notebook. The problem appeared just on this special computer with 5.0.3.2
Comment 3 Joel Madero 2015-11-15 15:52:07 UTC 
So the first thing we recommend when an issue only comes up on one computer is to reset your profile: https://wiki.documentfoundation.org/UserProfile#Resolving_corruption_in_the_user_profile
Comment 4 Buovjaga 2015-11-15 18:29:52 UTC 
*** Bug 95818 has been marked as a duplicate of this bug. ***
Comment 5 Greg 2016-06-01 22:15:32 UTC 
I can confirm this behavior in 5.0.6.2 (Fedora 23).

This bug should be escalated because it results in data loss.

I've used this product for years (first as StarOffice 5, then OpenOffice and then LibreOffice), and one of the best things about it was that it was so good at document recovery in the event of a LibreOffice or computer crash.  This bug needs to be fixed to restore that good behavior. :)

This has happened to me on two or three occasions now.

If a file's name is changed via Save As..., the document recovery does not work at all.  It does recover the old document under the old filename, but generates an error trying to access the temporary recovery file (under the old name) in the libreoffice directory, and the new document is neither re-opened nor recovered.
Comment 6 Aron Budea 2016-06-10 20:33:34 UTC 
This seems to be the same issue as bug 96607. Since there's already some activity in that report, I'm closing this one.

If you think this is a different issue, reset status to UNCONFIRMED.
Comment 7 Aron Budea 2016-06-10 22:47:12 UTC 

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