Issue 5996 - CRITIC failure, OO refuses starting again after a few times of usage
Summary: CRITIC failure, OO refuses starting again after a few times of usage
Status: CLOSED FIXED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: All Linux, all
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: joerg.skottke
QA Contact: issues@installation
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-20 08:55 UTC by jojoax
Modified: 2003-09-08 16:53 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description jojoax 2002-06-20 08:55:47 UTC
Since weeks this OO is critical instable. 
This means not, that it crashes, but it means that it refuses 
working/starting. 
 
This is the description of the Installation: 
Network/Workstation Installation 
Suse 8.0, Java 1.3.1, KDE3/kdeprint, additional alternative Ximian Gnome 
1.4 install via Red-carpet in /opt/gnome. 
 
1. 
./setup -net >> Systemwide into /opt/OpenOffice 
 
2. 
20 Clients/ User Homes stored on Server/NFS, (Option hard, lock) 
Each User installed /opt/OpenOffice/setup and did a "Workstation Setup". 
OO is installed to local harddisk. 
 
3. 
After that, all printers were installed using spadmin. (lkdeprint --stdin 
-d drucker) 
 
So good so far. 
 
1. FIRST CRITIC BUG 
This standard setup works only a very limited time. Somtimes it has to 
reapeated 3-5 times on a working day. 
This is the German Version dialog: 
----------------------------------------------------------- 
Die Anwendung kann nicht gestartet werden. 
Der Konfigurations-Manager kann nicht erzeugt werden. 
Um Ihre Installation zu reparieren starten Sie die setup-Applikation von 
CD aus, oder aus dem Verzeichnis in dem sich die Installationspakete 
befinden" 
------------------------------------------------------------- 
Meaning in english: 
Application can not be started. 
Configuration manager can not be created. 
To Reapair your Installation, start setup from install dir. 
------------------------------------------------------------ 
Trying to re-setup form /opt/OpenOffice/setup gives: Segmentation fault. 
Trying to re-setup from Major Installdir: gives already installed, cancel.
Comment 1 jojoax 2002-06-20 12:09:50 UTC
The Java SDK Environments within the local networ/Clients are 
floating. Some Workstations are forced to user special JDK versions 
for proproetary software on this nodes. 
 
This problem is reproducable here, if the JDK is changed on the 
system ! Ugly ! 
 
i.E. I was forced to change Java from IBM-JDK-1.3.0 to Sun 1.3.1, 
after that action the OpenOffice refused to work any more !!! 
Curious. 
 
 
 
Comment 2 jojoax 2002-06-25 12:27:11 UTC
HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP  
HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP  
 
This morning I was able to work regulary all fine, afer THE DAILY 
FRESH INSTALL !! 
 
For Lunch I logged out and after relogin, I got the same error. 
 
!! THIS IS AQ VITAL CRITIC UNOPERABLE BUG, which make the WHOLE 
SYSTEM OF OPENOFFICE UNUSABLE !!! 
 
jojo@pc1:jojo $ cd OpenOffice/ 
jojo@pc1:OpenOffice $ find -mmin -79 
./user/config/registry/instance/org/openoffice/Office 
./user/config/registry/instance/org/openoffice/Office/Common.xml 
./user/psprint/pspfontcache 
./user/temp 
./user/temp/soffice.tmp 
./user/temp/soffice.tmp/sv6j7.tmp 
jojo@pc1:OpenOffice $ rm -r user/temp 
temp      template 
jojo@pc1:OpenOffice $ rm -r user/temp/* 
jojo@pc1:OpenOffice $ find -mmin -79 
./user/config/registry/instance/org/openoffice/Office 
./user/config/registry/instance/org/openoffice/Office/Common.xml 
./user/psprint/pspfontcache 
./user/temp 
jojo@pc1:OpenOffice $ l user/psprint/pspfontcache 
-rw-rw-r--    1 jojo     os         268276 Jun 25 12:05 
user/psprint/pspfontcache 
jojo@pc1:OpenOffice $ more user/psprint/pspfontcache 
jojo@pc1:OpenOffice $ rm user/psprint/pspfontcache 
jojo@pc1:OpenOffice $ /opt/OpenOffice/program/swriter 
jojo@pc1:OpenOffice $ 
jojo@pc1:OpenOffice $ rm user/psprint/pspfontcache 
rm: Entfernen von »user/psprint/pspfontcache« nicht möglich: Datei 
oder Verzeichnis nicht gefunden 
jojo@pc1:OpenOffice $ find -mmin -79 
./user/config/registry/instance/org/openoffice/Office 
./user/config/registry/instance/org/openoffice/Office/Common.xml 
./user/psprint 
./user/temp 
jojo@pc1:OpenOffice $ rm 
user/config/registry/instance/org/openoffice/Office/Common.xml 
jojo@pc1:OpenOffice $ /opt/OpenOffice/program/swriter 
jojo@pc1:OpenOffice $ /opt/OpenOffice/program/setup 
Speicherzugriffsfehler = Segfault = CORE DUMP 
jojo@pc1:OpenOffice $ 
Comment 3 Olaf Felka 2002-07-24 09:29:46 UTC
Hi Joerg,
would you please be so kind to have a look on this?
Comment 4 joerg.skottke 2002-07-30 13:25:12 UTC
The setup usually comes up if 
1. applicat.rdb is damaged or missing
2. incompatible libraries are found
3. no installation (.sversionrc .user60.rdb) has been found.

To me it looks as if one or more of the above files are damaged or
missing if the office is shut down. Another reason could be that the
files are locked by another program.

You could try to do a 

truss -f soffice 

and press

[ctrl]+c

Probably this can give us a hint, what goes wrong.
Comment 5 jojoax 2002-07-31 10:20:58 UTC
Since Version 1.0.1 this behavior was not reproduceable.   
This problem does not show up in 1.0.1.   
  
I'll check applicat.rdb.  
I'll check for "incompatible libraries"  
But for which kind of libs I have to look for ? I presume, the OO  
own libs.  
A missing .sversionrc or .user60.rdb ist certainly not the reason.  
  
IMHO the idea of a lock problem or a library problem looks like the  
best way for searching th bug.  
  
According the fact, OO is working in 1.0.1 correctly, I think this  
bug is already solved within the update.  
I close the issue, as solved in 1.0.1. 
- Jürgen  
Comment 6 thorsten.ziehm 2003-05-20 16:16:53 UTC
This task is fixed or worked in OOo 1.1 beta2.
Comment 7 thorsten.ziehm 2003-05-20 16:34:11 UTC
closed ...