Bug 77654 - Recovery Loop
Summary: Recovery Loop
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.2.2.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on: 80790
Blocks:
  Show dependency tree / graph
 
Reported: 2014-04-18 19:25 UTC by Richard A Blaine
Modified: 2015-10-17 19:31 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Infinite File Recovery Loop (221.56 KB, image/png)
2014-11-06 11:08 UTC, Malome Khomo 		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 Richard A Blaine 2014-04-18 19:25:51 UTC 
Vista x64, LibreOffice 4.2.2.1

After crash in CALC, I am caught up in a file recovery loop and am unable to create a new file or modifiy an existing file.  Recovery produces a blank screen with only an icon in the upper left-hand corner with I can access to close the window.

Tried new user profile - did not help.

I am now unable to use LibreOffice CALC (and possibly other modules)>
Comment 1 Richard A Blaine 2014-04-18 21:39:44 UTC 
4/18/2-14 1436
After more testing I find that this bug applies to all open document formats (.ods, .odt, etc).  I am unable to use any open document formatted file.  I can use non-open document formats ok.
Comment 2 Richard A Blaine 2014-04-20 16:00:36 UTC 
Tried reset user profile, clearing temp files, version 4.2.3.3 - still have reported problem.

Finally resolved by several system restores.
Comment 3 Malome Khomo 2014-11-06 11:08:59 UTC 
Created attachment 109020 [details]
Infinite File Recovery Loop

Attachment indicates the workflow crash/recovery/crash loop that needs to be broken more intuitively
Comment 4 Malome Khomo 2014-11-06 14:02:22 UTC 
Example reproduced with Version: 4.2.4.2.
The crash file was is a well-formed XML text file that Writer exploded on.
Comment 5 Richard A Blaine 2014-11-06 15:35:33 UTC 
This problem has not recurred with relaease 4.2.5.2 and following.
Comment 6 Julien Nabet 2015-10-17 19:31:59 UTC 
Following last Richard's comment, let's put this one to WFM.