Issue 5483

Summary:	Crash occurs when default save directory does not exist
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:	P1 (highest)	CC:	issues, oooqa
Version:	OOo 1.0.0	Keywords:	oooqa
Target Milestone:	---
Hardware:	Other
OS:	Linux, all
Issue Type:	DEFECT	Latest Confirmation in:	---
Developer Difficulty:	---

Description Unknown 2002-06-02 04:07:50 UTC

I did a 'system install': files installed to /usr/local/.....  
  
1) Start swriter and type anything into the default document   
2) Click the save icon to save the document  
3) A dialog appears saying: "/usr/local/OpenOffice.org1.0/work does  
not exist"  
4) click OK  
5) Save As dialog pops up  
6) In the dialog type "/home/<username>/something  
7) click Save  
8) New dialog appears:  
Error saving the document Untitled1:  
Wrong parameter.  
The operation was started under an invalid parameter.  
9) click OK  
10) Application exits and all changes are lost: the file is not  
saved.  
 
Issue notes: 
- When I first installed, some symlinks were not created and I had 
to create them in /usr/local/bin for the app to work. 
- I am running on RH7.3 using KDE3.0 with all latest Redhat patches 
applied. 
- I could not, as of writing this bug, find out how to properly set 
the default directory for swriter to use in order to avoid this 
crash bug.

Comment 1 Unknown 2002-06-19 05:14:44 UTC

Well, I seem to have caused the problem to disapear by removing the
open office directory in my user dir and then removing the version file.

The I installed a version of java (1.4) and re-initiated the installer
by running swriter.

After installation, the problem disapeared (I suspect this is because
the default directory now correctly points to my user dir).

Comment 2 prgmgr 2002-07-10 00:11:29 UTC

Thanks for the post Jacques.

I set my default directory and then deleted the physical directory. 
Then, I followed your instructions but I did not get the same error
you experienced.

Considering that you no longer experience the problem, I'll just close
your issue.

Comment 3 prgmgr 2002-07-10 00:12:03 UTC

Closing ticket.