Red Hat Bugzilla – Bug 230940
openoffice.org-core was not installed despite being a rpm requirement
Last modified: 2007-11-30 17:11:58 EST
Description of problem:
After installing OpenOffice with pirut, it doesn't startup because
/usr/lib/openoffice.org/program/soffice doesn't exists. I get the following
[william@localhost ~]$ export LANG=en_US.UTF-8
[william@localhost ~]$ oowriter
/usr/bin/oowriter: line 2: /usr/lib/openoffice.org/program/soffice: No such file
/usr/bin/oowriter: line 2: exec: /usr/lib/openoffice.org/program/soffice: cannot
execute: No such file or directory
I installed the following packages:
[william@localhost ~]$ rpm -qa | grep -i openoffice
Steps to Reproduce:
1. Just execute oocalc, oodraw, ooimpress, oomath or oowriter
The system is up to date as of today.
Doh! it seems that pirut didn't install the openoffice.org-core package and that
seems to be the real problem. I am installing it right now with yumex to check
if that is true (I'll confirm later).
So the real bug is: why the packages listed in the original bug report didn't
depend on openoffice.org-core package?? I checked the information section for
those packages in pirut and it says that they requires it but I don't know why
the package didn't got installed.
I just installed the Live CD and after applying the updates I proceeded to
install more software that I needed, openoffice being among them.
Another thing: why yumex says that openoffice.org-core package depends on:
- tomcat5-jsp-2.0-api.i386 0-5.5.17-6jpp.2 - u
- tomcat5-servlet-2.4-api.i386 0-5.5.17-6jpp.2 - u
among others... that sounds a bit weird to me.
Noe that I installed openoffice.org-core package this error doesn't happen any
more but still openoffice doesn't start.
I type oowriter in the terminal and it stays there doing nothing, no disk
activity, no CPU activity.
Looking at 'ps aux' output I get the following:
william 2456 0.0 0.2 4620 1144 pts/0 S+ 21:18 0:00 /bin/sh
william 2464 0.2 0.5 41116 3016 pts/0 Sl+ 21:18 0:00
william 2485 1.8 5.4 60940 27968 pts/0 Sl+ 21:18 0:00 /usr/bin/gij
-classpath /usr/lib/openoffice.org/program JREProperties
Look at /usr/bin/gij ... Why is it running a Java interpreter? OpenOffice isn't
written in Java, right?
Conclusion: I can't still get OO.o to run properly.
rpm -qR openoffice.org-writer|grep core
openoffice.org-core = 1:2.2.0-9.2
as do the other packages, so the rpms are correct in that they require -core.
How on earth they got installed without -core getting installed baffles me.
There is no problem with the requirements of the packages themselves.
openoffice.org-core requires bsh (beanshell) bsh requires bsf, bsf requires
tomcat-foo-api. It's not a direct requirement of OOo, but a requirement of a
requirement. This is a correct requirement from OOo, it needs bsh to be complete.
the failure to start is gij bug #226959
Right, it seems an RPM problem, I reported another bug to sendmail:
sendmail depends on hesiod and despite being in the requirements it doesn't get
installed causing errors during sendmail start up. So I guess this is the same
rpm bug bitting openoffice.
What version of yum did you have installed when installing these packages?
Can you see if this still happens with yum 3.1.4 which will be in rawhide tomorrow?
/me scratch head/
How do I test this if openoffice is already installed? should I just uninstall
every openoffice package and try installing again?
As a preliminary test with software versions specified in comment #6 I tried to
remove openoffice.org-core alone. With RPM (rpm -e openoffice.org-core) it says
that there is a bunch of packages that depends on it (Test OK). With yum (yum
remove openoffice.org-core) it offers to remove the dependencies too (Test OK).
Jeremy, I think this is fixed in Test3. Right now I am running the Live CD and
I yum install the writer component and it pulls all the required components
So, it's fine by me if you mark this bug report as fixed.
DAMN!!! This bug isn't fixed in Fedora 7 Test 4 Live CD.
I wanted to re install the whole system from scratch with the Live CD and while
adding new apps to my shiny new system I ran into this problem again:
openoffice.org-package isn't installed despite being a requirement.
As noted in comment #3 all open office applications (calc, writer, etc) requires
explicitly the openoffice.org-core = 1:2.2.0-14.6
I haven't "fixed" it yet but I suppose installing the package manually will fix
the problem. BTW, I used pirut to install openoffice.org among other apps.
Please! someone at red hat reproduce and fix this bug since OO.o is a very
important package. It's very easy, just:
1) Install a clean system with a Fedora Live CD
2) update to latest rawhide
3) run pirut
4) install OO.o
5) run oowriter
See??? doesn't work.
Created attachment 153878 [details]
Seems a pirut specific issue
I just re-reinstalled my system (again) and try installing openoffice writer
with yum. It resolve dependencies in the right way so it seems a pirut bug.
I just did an install of the live CD and installed ooo-writer with pirut...
Can you look closely at the dependency screen and see what it tells you it's
going to install?
This is weird. pirut _does work_ now, I just did a "yum remove
tomcat5-servlet-2.4-api" which removes the following dependencies:
I then run pirut through the Applications menu and select only
"openoffice.org-writer". it now shows openoffice.org-core packaged as one of
the deps. I remember clearly that the first time I reinstalled my system a
couple of days ago I installed open office from pirut and the -core package _did
not_ showed up as a dep. I then proceeded with the installation to find the
same problem as expected: oowriter won't run because the soffice binary wasn't
Then I reinstalled my system an repeat the installation with yum, it worked
fine. What can I do?? I don't want to reinstall this OS again... may be I'll
try later with a virtual machine.
Sorry Jeremy... regarding the previous comment, pirut said that it was going to
install openoffice.org-core package but now I realize that it didn't.
I am now trying to reinstall the system again from scratch and try to reproduce
this problem. I'll comment later about this.
Made several tests and it seems to work fine for me now.