Issue 39553 - Auto Recovery continually tries to recover a document
Summary: Auto Recovery continually tries to recover a document
Status: CLOSED DUPLICATE of issue 38758
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: 680m65
Hardware: All Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Joost Andrae
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-24 14:02 UTC by hurricaneandrew
Modified: 2010-04-06 22:37 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description hurricaneandrew 2004-12-24 14:02:29 UTC 
I was working in two Writer documents, when the application crashed.  The next
time I restarted, OO recovered one document, but couldn't recover the other one.
 Now, every time I start an OO application, I am presented with the auto recover
dialog.  Even an uninstall and reinstall does not cure the problem.  There
should be a way to eliminate this behaviour.
Comment 1 michael.ruess 2004-12-27 07:46:31 UTC 
reassigned to JA.
Comment 2 michael.ruess 2004-12-28 14:57:30 UTC 
.
Comment 3 Joost Andrae 2005-01-04 13:58:57 UTC 
JA->hurricaneandrew: delete the Recovery.xcu within your user profile in
"documents and settings"/<username>/"application
data"/OpenOffice.org1.9.65/user/registry/data/org/openoffice/Office/Recovery.xcu
Comment 4 Joost Andrae 2005-01-04 14:01:10 UTC 
JA: closing as duplicate

*** This issue has been marked as a duplicate of 38758 ***
Comment 5 Joost Andrae 2005-01-04 14:02:03 UTC 
.
Comment 6 hurricaneandrew 2005-01-04 14:12:24 UTC 
That did it.  I spent too much time poking around the registry itself.  I guess
I've just spent too much time in the past using Microsoft Office :)
Comment 7 Robert Pollak 2010-04-06 22:37:33 UTC 
I still saw this with (the German version of) OOo 3.1 on Ubuntu Karmic. My
workaround was to select "cancel" instead of "recover".

I don't know why this is marked as duplicate of issue 38758 "crashreporter
crashes if no crash data available", since in my case there was no crash
involved, as far as I know.