Issue 2973 - An unrecoverable error reading blank OO RTF document
Summary: An unrecoverable error reading blank OO RTF document
Status: CLOSED DUPLICATE of issue 2606
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: 641
Hardware: PC Linux, all
: P2 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-01-29 20:30 UTC by Unknown
Modified: 2003-09-08 16:56 UTC (History)
1 user (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 Unknown 2002-01-29 20:30:54 UTC 
I am experiencing consistent inability to open any rtf file in OO 641C on Debian
Linux - Release: Woody last updated on 02-01-26. Even newly saved blank page in
OO itself. OO dies with an Error dialog: "An unrecoverable error has occured -
All modified files has been saved and can probably be recovered at program restart."

I was forced to switch from SO52 to OO as I find out that M$Word2002 (M$ XP)
refuses to display any doc or rtf files made in SO52. All my documents are rtf
in attempt to remain flexible. Not this time :-(.

I will be happy to assist in diagnostic (strace, gdb,...) with the little
direction. What can I do to help isolate the problem?
I am opening an issue as a user making similar report on users mailing list
decided to give up and switch back to SO52. (Vahur Lokk 23 Jan)

Hoping I can be of help. Regards. Marko
Comment 1 stefan.baltzer 2002-02-04 09:34:36 UTC 
Reassigned to Michael.
Comment 2 michael.ruess 2002-02-04 12:41:33 UTC 
It looks like OO641 has a problem when running on newer Linux systems.
I could now see the problem on a RedHat 7.1. Others reported the same
on SUSE 7.3 or RedHat 7.2. This issue is related to issue #2606, so I
close this one here.

*** This issue has been marked as a duplicate of 2606 ***
Comment 3 michael.ruess 2002-11-29 08:37:49 UTC 
Problem is fixed in OpenOffice 1.0.1