Bug 93137 - Document Recovery fails - logical error.
Summary: Document Recovery fails - logical error.
Status: RESOLVED DUPLICATE of bug 95535
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.4.1.2 release
Hardware: All Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-05 12:06 UTC by kie000
Modified: 2015-11-05 05:31 UTC (History)
3 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 kie000 2015-08-05 12:06:54 UTC
I deleted some cells, Libreoffice crashed (for the 100th time).

The document recovery did not work - a very common thing.

Error Message:

"C:\Users\Username\AppData\Roaming\LibreOffice\4\user\backup\10 SatFat.ods_0.ods does not exist."

Followed by

"Object not accessible.
The object cannot be accessed
due to insufficient user rights"

And then it goes totally retarded, it recovered nothing, reverted to the previously saved document, it then pops up a dialogue asking me if I want to save the already saved file in some directory that I never use!!!!!!! And for some icing on the cake - if I click yes, IT DOESN'T SAVE IT THERE ANYWAY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! In fact it doesn't save it at all!

Do you have a room with an infinite number of monkeys in writing LibreOffice code? It's so bad it boggles the mind.

The file name is not called "10 SatFat.ods_0.ods" it is called "10 SatFat.ods"
And none of the files in the backup directory start with "10 SatFat"

Why is 

(1) LibreOffice looking for a file that doesn't exist
(2) in a directory that contains no recovery information

It's bad enough that Calc crashes very frequently, but then to lose 10-20 mins of work is maddening.

LibreOffice should autosave every 60 seconds by default since the document recovery is so bad. - I've changed my setting to this.
Comment 1 PMouse 2015-08-25 18:44:42 UTC
This has been going on for me since v4, I think, too.

It just recurred for me with 4.4.5.2.
Comment 2 kie000 2015-08-26 12:51:01 UTC
@ Pmouse

I'd recommend upgrading to 5.x it very rarely crashes compared to 4.x
Comment 3 PMouse 2015-08-26 17:42:32 UTC
Libreoffice didn't crash, though; it was my computer.

Since recovery used to work fine, but is now broken, I don't expect upgrading to help.  Unless, you know for sure that it got fixed...is that what you mean?
Comment 4 Kumāra 2015-10-07 05:57:57 UTC
The failure seems random. When it fails, the recovery program looks for the file ending ".odt_0.odt", but what exists in the backup folder ends with ".odt_1.odt".
Comment 5 Kumāra 2015-10-07 06:05:21 UTC
(In reply to kie000 from comment #0)
> Do you have a room with an infinite number of monkeys in writing LibreOffice
> code? It's so bad it boggles the mind.

While I can empathize with your frustration, kie000, I can assure you that a comment as the above is likely to put off the coders, who aren't paid for this. Hope you understand.
Comment 6 kie000 2015-10-08 04:27:36 UTC
@ Kumāra

Fair enough, the code has been improved a lot in 5.x, 4 was a crashy mess and losing work due to recovery not working can indeed be very frustrating.
Comment 7 Kumāra 2015-10-08 09:46:28 UTC
(In reply to kie000 from comment #6)
> the code has been improved a lot in 5.x, 4 was a crashy mess
> and losing work due to recovery not working can indeed be very frustrating.

Yes, I hate it when that happens to. Good thing I have a pretty solid backup solution, AND developed a habit of hitting Ctrl-s very often!

Good to know 5.x works well for you. I've not upgraded yet, and would like to know the same as PMouse: For the new version, should LO be suddenly terminated, does the document recovery work properly?
Comment 8 Kumāra 2015-11-04 05:27:26 UTC
According to Bug 95535, the bug remains in LO5.
Comment 9 Kumāra 2015-11-05 05:31:50 UTC
I'm marking this as a duplicate of another report, which is nicer.

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