Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | OOo 1.0.0 writer won't start anymore: "unrecoverable error" during load | ||
---|---|---|---|
Product: | Writer | Reporter: | Unknown <non-migrated> |
Component: | code | Assignee: | stefan.baltzer |
Status: | CLOSED NOT_AN_OOO_ISSUE | QA Contact: | issues@sw <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues, oooqa |
Version: | OOo 1.0.0 | Keywords: | oooqa |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
Unknown
2002-06-12 09:29:40 UTC
Now even opening an existing document does not work any longer. :( I tried to use the 641d-build, which also ended up in the "an unrecoverable error occured" message. I'm getting into serious time problems now, because I started writing some business documents with OOo 1.0.0 which I have to finish during the next days. Restarting them will take up a whole lot more time, though. Now I think about "cheating" with Staroffice 6.0 beta, by setting up the wrong system date. But this is no real solution I can live with. So, if anyone could give a comment on this bug report (some hints, for example, which things I could try out) I would be very happy. As additional information: I installed StarOffice 6.0 beta (tuned my system clock back one year). When I tried to start SO6 it gave the same error message as I know from OOo: unrecoverable error occured. :(( Michael, thank you for using and supporting OOo. I'm sorry no one has touch this case since you posted it. Have you found a resolution to this issue? I'm sorry, too, as I didn't close this bug yet. Yes, I have found a solution. It was a problem with my hdd. It was slowly adding defective sectors, and magically the new installed programs were using those sectors. I guess that's another Murphy's... after exchanging the hdd for a new (and bigger ;) ) one now everything works perfectly. The problem never occured again. I'm not sure about the desired status for closing this bug... is it "invalid", or "fixed"? Therefor I leaving it open again, could you close it please with the correct resolution? User had a bad HD. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. |