Issue 1458 - New Installation Core Dumps on Solaris 8
Summary: New Installation Core Dumps on Solaris 8
Status: CLOSED FIXED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: 633
Hardware: Sun Solaris
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Olaf Felka
QA Contact: issues@installation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-08-11 20:27 UTC by Unknown
Modified: 2003-09-08 16:53 UTC (History)
1 user (show)

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


Attachments
truss file for soffice (128.13 KB, text/plain)
2001-08-11 20:54 UTC, Unknown
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2001-08-11 20:27:38 UTC
My first down load of the Open Office version.  I down loaded the three patches
from Sun
that the installation notes defined as being needed. I ran setup and when it
could not find
a version of Java that it wanted, java1.2, that it wanted I down loaded  from
Sun j2sdk1_3_1. The rest of the installation went without any issues.
Installation was done as
root. When I run soffice from my account I get the following:
hemlock: $ /usr/local/openoffice60/program/soffice
Unable to retrieve application configuration data: Cannot locate Configuration:
Invalid user installationAbort(coredump)
Comment 1 Unknown 2001-08-11 20:54:22 UTC
Created attachment 444 [details]
truss file for soffice
Comment 2 Olaf Felka 2001-08-14 12:13:40 UTC
It's not possible to make an installation as user 'a' and use it as 
user 'b', every user has his own configuration files in his home 
directory, needed by OOo to start -> every user has to make his own installation. OOo shouldn't abort n this case, this is fixed in the next version.
Comment 3 Olaf Felka 2001-08-14 12:14:17 UTC
It's not possible to make an installation as user 'a' and use it as 
user 'b', every user has his own configuration files in his home 
directory, needed by OOo to start -> every user has to make his own installation. OOo shouldn't abort n this case, this is fixed in the next version.
Comment 4 Olaf Felka 2001-09-03 10:22:48 UTC
Seems to work.