Bug 120565 - OpenOffice fails to start
OpenOffice fails to start
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Dan Williams
Depends On:
  Show dependency treegraph
Reported: 2004-04-10 17:30 EDT by Paul F. Johnson
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-04-25 17:53:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Contents of the openoffice-install-log (1.40 KB, text/plain)
2004-04-13 04:34 EDT, Paul F. Johnson
no flags Details

  None (edit)
Description Paul F. Johnson 2004-04-10 17:30:38 EDT
Description of problem:
OpenOffice cannot be started from the gnome menu or from the command
line (terminal window)

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Open a terminal window
2. Type oowriter
3. Click on the gnome menu, go to office, click on any OO.org component
Actual results:
Installation of OpenOffice.org 1.1.1 failed:
/usr/lib/ooo-1.1/program/setup -R:/etc/openoffice/autoresponse.conf -v
-nogui >& ~/.openoffice-install-log'

Expected results:
oowriter starts

Additional info:
The version from OpenOffice.org works fine.
Comment 1 Dan Williams 2004-04-13 00:39:29 EDT
can you paste in the output of ~/.openoffice-install-log?

Comment 2 Paul F. Johnson 2004-04-13 04:34:36 EDT
Created attachment 99354 [details]
Contents of the openoffice-install-log

Hope this helps
Comment 3 Dan Williams 2004-04-13 09:54:52 EDT
Could you perhaps remove the ~/.sversionrc file in your home directory
and try to run OOo again?
Comment 4 Paul F. Johnson 2004-04-18 05:45:11 EDT
That's done the trick - OOo is back and happy. Is it worth on the
install script removing the .sversionrc files from the users on the

Note You need to log in before you can comment on or make changes to this bug.