Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12239 - OpenOffice expects java to be in /opt/java
Attached to Project:
Arch Linux
Opened by Nicolas Bigaouette (big_gie) - Tuesday, 25 November 2008, 17:51 GMT
Last edited by Allan McRae (Allan) - Wednesday, 26 November 2008, 02:56 GMT
Opened by Nicolas Bigaouette (big_gie) - Tuesday, 25 November 2008, 17:51 GMT
Last edited by Allan McRae (Allan) - Wednesday, 26 November 2008, 02:56 GMT
|
DetailsDescription:
OpenOffice seems to expect java to be in /opt/java but openjdk6 is installed in /usr/lib/jvm/java-1.6.0-openjdk. When installing a java extension (languagetool: http://www.languagetool.org/ ) an error is reported, stating a java runtime can't be initialized. When run from the command line, and trying to install the extension, I get: [Java framework]sunjavaplugin.so could not load Java runtime library: file:///opt/java/jre/lib/amd64/server/libjvm.so. As a workaround, I've made a symbolic link from openjdk6's libjvm.so where openoffice is looking for it: > sudo mkdir -p /opt/java/jre/lib/amd64/server/ > sudo ln -s /usr/lib/jvm/java-1.6.0-openjdk/jre/lib/amd64/server/libjvm.so /opt/java/jre/lib/amd64/server/ Else I can't install the extension. Now I can install it and run it. Additional info: * package version(s) local/openoffice-base 3.0.0-3 |
This task depends upon
It's simply some unflexibility from the extension. Nothing we will change for OpenJDK6.
http://nbigaouette.inrs-emt.homelinux.net/linux/arch/ooorg/oopenoffice_java.png
The openjdk was not selected here... weird. After selecting it and reinstalling the extension, I don't have any error anymore.
The bug can be closed now... :) Thanx guys.