Red Hat Bugzilla – Bug 478469
UNO Runtime Environment broken when Openoffice 3 installed
Last modified: 2008-12-30 18:10:57 EST
Created attachment 327971 [details]
Image showing YUM 'upgrading' to broken version of UNO
Description of problem:
When you have successfully installed Openoffice 3 from Openoffice's website, YUM flashes up that you have an update in the form of openoffice.org-ure-1:30.0.0-9.10.fc10 (x86_64). Just to let you know that if you install this update, then you break Openoffice.org, as a 'newer' installer is included in RPMS that OOO ship with OOO3.
Version-Release number of selected component (if applicable):
Everytime you upgrade from openoffice.org-ure-1.4.0-9358.rpm to openoffice.org-ure-1:3.0.0-9.10.fc10 which is flagged up by YUM.
Steps to Reproduce:
1. Remove Openoffice 2.4 using YUM. Make sure that you remove the UNO component at this time.
2. Install the RPMS and Desktop-intregration modules
3. YUM 'updates' the RPM to the broken version.
Openoffice starts with
/opt/openoffice.org3/program/soffice.bin: error while loading shared libraries: libuno_sal.so.3: cannot open shared object file: No such file or directory
Openoffice should start as normal.
This is easy to fix: go back to the RPM installers and reinstall the shipped UNO module using rpm -Uvh --force openoffice.org-ure-1.4.0-9358.x86_64.rpm
> 2. Install the RPMS and Desktop-intregration modules
2. Install the Openoffice 3 RPMS and Desktop-intregration modules
You're effectively mixing repositories where two different rpms exist with the same name.