On Sat, 14 May 2005 22:26:32 +0100, Robt. W. Fletcher Jr <me DeleteThis @wa.us> wrote:
> a. what does cat ~/.opera/javapath.txt show?
I copied my .opera directory from my old home directory so originally this
file had the old location of a Java 1.4.2 install in it. I've tried
changing it to point to the 1.5 location
(/usr/java/jdk1.5.0_03/jre/lib/i386) without any luck.
> b. what does locate libjava.so show?
/usr/java/jdk1.5.0_03/jre/lib/i386/libjava.so
> On my system:
>
> ~% cat ~/.opera/javapath.txt
> /opt/blackdown-jdk-1.4.2.01/jre/lib/i386
> ~% locate libjava.so
> /opt/blackdown-jdk-1.4.2.01/jre/lib/i386/libjava.so
>
> The directory that contains libjava.so s/b in the javapath.txt
It is.
This is the exact output from using -debugjava:
opera: [java] There seems to be a preloaded version of Xt.
There is a workaround for this problem in the opera
startup script. If that workaround fails, opera will
most likely crash every time it tries to use Java.
The workaround seems to be working.
Technical explanation:
There is a problem with the order of loading Xt and
Java. If Xt is loaded before libawt (part of Java),
Java will crash when it tries to access the screen.
The workaround is based on using LD_PRELOAD to load
libawt.so first.
opera: [java] The Java enable flag will not be reset
because the OPERA_FORCE_JAVA_ENABLED environment
variable has been defined.
Thanks,
Dan.
--
Daniel Dyer
http://www.footballpredictions.net