Red Hat Bugzilla – Bug 134727
[RHEL3 update] missing requires for oo.org-i18n
Last modified: 2007-11-30 17:07:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
The main OO.org package is missing a dep for OO.org-i18n. If i18n
isn't installed openoffice doesn't run.
If a user has never run openoffice it fails when setting up there
preferences. If they have run openoffice before it sig 11s and gives a
nice stack trace.
This is rather anoying since it breaks all new installs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Do a fresh install of RHEL 3 WS U3
2. Try to run openoffice
Actual Results: openoffice crashes one way or another
Expected Results: it should start properly
This bug is considered a show stopper for deploying RHEL and NCSU.
Kinda hard to be productive when the office suite doesn't work. :-)
I'd attach the stack trace that OO.org prints out, but it is simply
that the openoffice.org-i18n package is missing.
Ummmm, 1.1.2-x isn't supported on RHEL3 yet. The latest version of
OOo on RHEL3 is 1.1.0-16.14.EL.
Are you saying that you've tried to compile the most current OOo (from
Fedora Core 3 test 2) on RHEL3?
This affects openoffice.org-1.1.0-16.14.EL as well. I was just looking
at the most recent version openoffice in rhn when I selected a version
Oh, and we're not trying to run the 1.1.2-x series.
Ok, in that case, can somebody get a backtrace for me?
Created attachment 104804 [details]
OO stack trace
Here you are...one stack trace from OO
Any chance of this getting fixed any time soon?
Yes, we're going to have a fix for U5.
*** Bug 141695 has been marked as a duplicate of this bug. ***
openoffice.org-1.1.2-19.2.EL3 has been built for U5 and takes care of this problem.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.