Issue 9084 - Writer crashes when saving a four word file in native format
Summary: Writer crashes when saving a four word file in native format
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: PC Windows 95
: P3 Trivial (vote)
Target Milestone: ---
Assignee: stefan.baltzer
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2002-11-08 13:43 UTC by dhislop
Modified: 2003-09-08 16:56 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 dhislop 2002-11-08 13:43:53 UTC 
I've only just downloaded OOO, and have installed it as a network installation
with two client installations. The server is Windows Me, which also has a client
install on it (working fine), and the second client is Win95.

On the Win95 client, I open Writer, type the four words This is a test, select
File->Save, and save to a file (various names).

Every time I've tried it, the progress bar during the save gets a long way to
the right (seems not 100%) before disappearing, and I get a dialog "An
unrecoverable error has occurred. All modified files have been save and can
probably be recovered after a restart"
True to its word, OOO Writer restarts,asks me if I want to recover a file (with
some temp name, sorry, can't remember it), and recovers the file when I click Yes.

If I now save the recovered file in MS Word 97/2000/XP format it saves just
fine, same as it does if I try saving in Word to start with.

regards - David
Comment 1 Rainer Bielefeld 2003-06-17 12:05:37 UTC 
might have to do something with issue 12090 or issue 10250

Rainer
Comment 2 Rainer Bielefeld 2003-06-20 08:23:10 UTC 
I erally think this has to do with  issue 12090 or issue 10250.

I tried with result WFM.

Closing issue due to inactivity as WFM.

If you still see this problem with 1.0.3 or later, please first check
dependency to mentionned issues and then open new issue (if necessary).

Rainer
Comment 3 stefan.baltzer 2003-07-02 16:21:20 UTC 
Closed.