Issue 25543 - Crash: saving toolbars/settings with no permissions
Summary: Crash: saving toolbars/settings with no permissions
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 1.1
Hardware: PC Linux, all
: P4 Trivial (vote)
Target Milestone: ---
Assignee: mci
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-16 12:32 UTC by dominiccleal
Modified: 2004-02-16 13:56 UTC (History)
1 user (show)

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

Attachments
Crash output created by error handling tool (29.25 KB, text/xml)
2004-02-16 12:34 UTC, dominiccleal 		no flags Details
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 dominiccleal 2004-02-16 12:32:45 UTC 
For example, when toolbars are being customised, if the user doesn't have write 
permissions to the OO config directory, the program crashes or settings simply 
aren't saved.

An error can also appear when closing down the program saying that it cannot 
open a file.

I've now found multi-user installs need to be done with the -net parameter for 
the setup script.
Comment 1 dominiccleal 2004-02-16 12:34:16 UTC 
Created attachment 13184 [details]
Crash output created by error handling tool
Comment 2 mci 2004-02-16 13:54:38 UTC 
Hi dominiccleal,

thanks for using and supporting OpenOffice...

If you want an installation of OpenOffice used by more than one user you need to
use the -net option. That's what you've found out. 

I tried (just for fun) a workstation installation of OOo1.1.1b in /opt done by
root and used by two users at the same time making settings to the toolbars. All
went fine until I closed OpenOffice: 2 Messages appeared that some file couldn't
be written 
==> that's normal since the users didn't have write access to the config files....
==> It wasn't possible to crash OpenOffice this way...

reassigned to mci
Comment 3 mci 2004-02-16 13:55:43 UTC 
set to invalid
Comment 4 mci 2004-02-16 13:56:21 UTC 
closing