Subject: | |
From: | |
Reply To: | |
Date: | Sat, 4 Jul 2009 00:58:33 +0100 |
Content-Type: | TEXT/PLAIN |
Parts/Attachments: |
|
|
On Fri, 3 Jul 2009, Panagiotis Kritikakos wrote:
> Hi,
>
> On SL5.2 there is a missing link for the fonts to be used by JRE 1.6.0_11.
> The directory /usr/lib/jvm/java-1.6.0-sun-1.6.0.11/jre/lib/fonts points to
> /usr/share/fonts/java which actually doesn't exist. However, the 1.5.0_16 JDK
> installation uses /usr/java/jdk1.5.0_16/jre/lib/fonts which contains all the
> right fonts. Altering JAVA_HOME to JDK 1.5.0_16 and launching the Java
> application again, it displays the fonts correctly. The quick workaround to
> get it working with 1.6.0_11 is to copy the existing JDK1.5.0_16 fonts
> directory under /usr/share/fonts/java.
>
> Is there a Java fonts package missing that causes that?
At least on sl53 if I run "yum provides /usr/share/fonts/java" it tells me
that the java-1.6.0-sun-compat package provides it, and doing rpm -qlp on
the latest version of that (1.6.0.13-1.sl5.jpp I think), shows (for i386
in this case):
$ rpm -qlp 53/i386/updates/security/java-1.6.0-sun-compat-1.6.0.13-1.sl5.jpp.i586.rpm | grep /usr/share/fonts/java/
/usr/share/fonts/java/LucidaBrightDemiBold.ttf
/usr/share/fonts/java/LucidaBrightDemiItalic.ttf
/usr/share/fonts/java/LucidaBrightItalic.ttf
/usr/share/fonts/java/LucidaBrightRegular.ttf
/usr/share/fonts/java/LucidaSansDemiBold.ttf
/usr/share/fonts/java/LucidaSansRegular.ttf
/usr/share/fonts/java/LucidaTypewriterBold.ttf
/usr/share/fonts/java/LucidaTypewriterRegular.ttf
/usr/share/fonts/java/XftCache
/usr/share/fonts/java/encodings.dir
/usr/share/fonts/java/fonts.alias
/usr/share/fonts/java/fonts.cache-1
/usr/share/fonts/java/fonts.dir
/usr/share/fonts/java/fonts.scale
but in fact those are all symlinks into the /usr/java/jdk1.6.0_13/... tree
which seems to be provided by the jdk-1.6.0_13-fcs package...
Those also seem to be present in the 52 security update trees and hence
yum repos. So if nothing else you seem to be missing a security update to
jdk1.6.0_13 though in fact _14 is current... (but it isn't a security
update) :-)
My copy of the 52 security updates trees seems to have no 1.6.0.11 version
in it (it has older and newer ones), so maybe that happened to be a
particularly bad version you have...
-- Jon
|
|
|