Although I've installed Sun's Java VM I'm still not getting Java pages to
work.

The reult of running Opera with -debugjava is:-

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 have failed. Java will be disabled.
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] Disabling java due to potential problems. If you know
what you are doing, you can set the environment variable
OPERA_FORCE_JAVA_ENABLED to '1' to override this.
The actual problems should be described above.

Does anyone have any suggestions on what to do next, I'm quite new to
Linux.

Running Opera 7.54 under Mandrake 10.1

Andy J.

From:	Steven V. Gunhouse
Subject:	Re: No Java
Date:	Thu, 06 Jan 2005 21:46:33 GMT

On Thu, 06 Jan 2005 21:22:10 -0000, Andy J. wrote:

> Although I've installed Sun's Java VM I'm still not getting Java pages
> to work.
>
> The reult of running Opera with -debugjava is:-
>
> 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 have failed. Java will be disabled.
> 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] Disabling java due to potential problems. If you know
> what you are doing, you can set the environment variable
> OPERA_FORCE_JAVA_ENABLED to '1' to override this.
> The actual problems should be described above.
>
> Does anyone have any suggestions on what to do next, I'm quite new to
> Linux.
>
> Running Opera 7.54 under Mandrake 10.1
>
> Andy J.

Do you have either lesstif or OpenMotif installed? What version of Java do
you have?

--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

From:	Robt. W. Fletcher Jr
Subject:	Re: No Java
Date:	Sat, 15 Jan 2005 22:29:29 -0800

Felixk Karpfen writes:

> And there was the problem - now fixed.
>
> However, it raises another issue.
>
> Quite a few files in my /home/felixk/.opera directory currently belong
> to root. That might be related to the routines that I needed to use to
> transport Opera to my (new) Debian box. The list reads:
>
> [felixk@carrot felixk]$ ls -l .opera/ | grep root
> -rw-r--r-- 1 root root 155694 Dec 17 10:41 OperaOld.adr
> -rw-r--r-- 1 root root 21 Dec 17 10:41 cookies4.dat.bak
> -rw-r--r-- 1 root root 29904 Dec 17 10:41 default.zip
> -rw-r--r-- 1 felixk root 1 Jan 13 19:53 javapath.txt
> -rw-r--r-- 1 root root 333 Dec 17 10:41 notes.adr
> -rw-r--r-- 1 root root 321 Dec 17 10:41 notes.adr.bak
> -rw-r--r-- 1 root root 200521 Dec 17 10:41 op_ok.adr
> -rw-r--r-- 1 root root 19734 Dec 17 10:41 opcacert.dat
> -rw-r--r-- 1 root root 55217 Dec 17 10:41 opcacrt6.dat
> -rw-r--r-- 1 root root 27 Dec 17 10:41 opcert6.dat
> -rw-r--r-- 1 root root 12 Dec 17 10:41 opera.gif
> -rw-r--r-- 1 root root 11495 Dec 17 10:41 opera.ini
> -rw-r--r-- 1 root root 1212 Dec 17 10:41 opera.reg
> -rw-r--r-- 1 root root 358 Dec 17 10:41 opera.win
> -rw------- 1 root root 17006 Dec 17 10:41 opera6.ini.01.bk
> -rw------- 1 root root 15502 Dec 17 10:41 opera6.ini_june30.bk
> -rw------- 1 root root 1024 Jan 13 19:53 oprand.dat
> -rw-r--r-- 1 root root 58 Dec 17 10:41 opssl.dat
> -rw-r--r-- 1 root root 76 Dec 17 10:41 opssl6.dat
>
> Do any of these changing?

bash-2.05b$ man chown
bash-2.05b$ cd ~/
bash-2.05b$ chown felixk:users -R .opera

Note, I assume felixk is in the group users. If you don't know, do the
following:

bash-2.05b$ cd
bash-2.05b$ touch foo
bash-2.05b$ ls -al foo
bash-2.05b$ rm foo
--
-rwf

From:	Robt. W. Fletcher Jr
Subject:	Re: No Java
Date:	Thu, 06 Jan 2005 14:53:40 -0800

"Andy J." writes:

>> Do you have either lesstif or OpenMotif installed? What version of
>> Java do you have?
>>
>
> I have no idea what they are but 'which lesstif' and 'which
> OpenMotif' come back negative and unless Mandrake installs them by
> default (I haven't) I'd say no. As for Java, Java Runtime
> Environment 1.4.2_06.

[snip]

> application/x-java-bean -
> application/x-java-bean -
> /usr/java/j2re1.4.2_06/plugin/i386/ns4/libjavaplugin.so

1. Opera does not use the Java plugins, remove the
/usr/java/j2re1.4.2_06/plugin/i386/ns4/ directory from the plugin
search path.

2. Try adding /usr/java/j2re1.4.2_06/lib/i386 as the JavaPath (alt p ->
Multimedia). Then stop Opera and re-start it.

3. Then try to bring of the Java console (alt t a j)

--
-rwf

From:	Andy J.
Subject:	Re: No Java
Date:	Thu, 06 Jan 2005 23:14:33 -0000

RWF, I thank you. I'd never have figured that out on my own. Thanks
too, Steven.
I originally installed Java to use Limewire but as it was there I though
I'd link
it to Opera......... SHould have realised it wasn't going to be
straightforward.

Andy J.

From:	Eirik Byrkjeflot Anonsen
Subject:	Re: No Java
Date:	Mon, 17 Jan 2005 09:47:18 +0100

"Robt. W. Fletcher Jr" writes:

> Felixk Karpfen writes:
>
>> And there was the problem - now fixed.
>>
>> However, it raises another issue.
>>
>> Quite a few files in my /home/felixk/.opera directory currently belong
>> to root. That might be related to the routines that I needed to use to
>> transport Opera to my (new) Debian box. The list reads:
>>
>> [felixk@carrot felixk]$ ls -l .opera/ | grep root
>> -rw-r--r-- 1 root root 155694 Dec 17 10:41 OperaOld.adr
>> -rw-r--r-- 1 root root 21 Dec 17 10:41 cookies4.dat.bak
>> -rw-r--r-- 1 root root 29904 Dec 17 10:41 default.zip
>> -rw-r--r-- 1 felixk root 1 Jan 13 19:53 javapath.txt
>> -rw-r--r-- 1 root root 333 Dec 17 10:41 notes.adr
>> -rw-r--r-- 1 root root 321 Dec 17 10:41 notes.adr.bak
>> -rw-r--r-- 1 root root 200521 Dec 17 10:41 op_ok.adr
>> -rw-r--r-- 1 root root 19734 Dec 17 10:41 opcacert.dat
>> -rw-r--r-- 1 root root 55217 Dec 17 10:41 opcacrt6.dat
>> -rw-r--r-- 1 root root 27 Dec 17 10:41 opcert6.dat
>> -rw-r--r-- 1 root root 12 Dec 17 10:41 opera.gif
>> -rw-r--r-- 1 root root 11495 Dec 17 10:41 opera.ini
>> -rw-r--r-- 1 root root 1212 Dec 17 10:41 opera.reg
>> -rw-r--r-- 1 root root 358 Dec 17 10:41 opera.win
>> -rw------- 1 root root 17006 Dec 17 10:41 opera6.ini.01.bk
>> -rw------- 1 root root 15502 Dec 17 10:41 opera6.ini_june30.bk
>> -rw------- 1 root root 1024 Jan 13 19:53 oprand.dat
>> -rw-r--r-- 1 root root 58 Dec 17 10:41 opssl.dat
>> -rw-r--r-- 1 root root 76 Dec 17 10:41 opssl6.dat
>>
>> Do any of these changing?
>
> bash-2.05b$ man chown
> bash-2.05b$ cd ~/
> bash-2.05b$ chown felixk:users -R .opera
>
> Note, I assume felixk is in the group users. If you don't know, do the
> following:
>
> bash-2.05b$ cd
> bash-2.05b$ touch foo
> bash-2.05b$ ls -al foo
> bash-2.05b$ rm foo

Well, not all of them need to be writable by the user, but it's
probably better if they are... (Although making them unwritable
certainly ensures that you won't accidentally change any settings...)

eirik

From:	Robt. W. Fletcher Jr
Subject:	Re: No Java
Date:	Tue, 11 Jan 2005 00:28:54 -0800

Eirik Byrkjeflot Anonsen writes:

>
> You don't need any of libXm, motif or lesstif to have java in opera.

Are you sure about that?

1. started Opera (no pages opened)

2. java was enabled.

3. attached gdb to the running Opera pid

~% gdb /usr/local/lib/opera/8.0-20050104.1/opera 17863
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
(no debugging symbols found)...Using host libthread_db library "/lib/libthread_d b.so.1".

Attaching to program: /usr/local/lib/opera/8.0-20050104.1/opera, process 17863
Reading symbols from /opt/blackdown-jdk-1.4.2.01/jre/lib/i386//libawt.so...
(no debugging symbols found)...done.
Loaded symbols for /opt/blackdown-jdk-1.4.2.01/jre/lib/i386//libawt.so

[snip]

Reading symbols from /opt/blackdown-jdk-1.4.2.01/jre/lib/i386/libXm.so.3...
done.
Loaded symbols for /opt/blackdown-jdk-1.4.2.01/jre/lib/i386/libXm.so.3
Reading symbols from /usr/X11R6/lib/libXp.so.6...done.

[snip]

Loaded symbols for /lib/libncurses.so.5
Reading symbols from /usr/X11R6/lib/libXcursor.so.1...done.
Loaded symbols for /usr/X11R6/lib/libXcursor.so.1
Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/xomGeneric.so.2...
done.
Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/xomGeneric.so.2
0xffffe410 in ?? ()
(gdb)

My java comes with libXm.so.3 -- which is clearly loaded.

--
-rwf

From:	Eirik Byrkjeflot Anonsen
Subject:	Re: No Java
Date:	Tue, 11 Jan 2005 09:00:47 +0100

"Robt. W. Fletcher Jr." writes:

> Felixk Karpfen writes:
>
>> * Andy J. [2005-01-06]:
>> >> Do you have either lesstif or OpenMotif installed? What version of Java
>> >> do you have?
>> >>
>>
>> Since I have had similar problems (and similar error messages) since I
>> upgraded to Opera 7.50, I venture to break in on this thread.
>>
>> I currently have Java Runtime Environment 1.4.2_01 on my box and was
>> told that it has a bug and an upgrade of J2RE is needed.
>>
>> Since I use Java very rarely and it worked in mozilla, I put that
>> task on the back-burner.
>>
>> I have since changed my OS to Debian Sarge. No change. Jave still works
>> in mozilla but not in Opera. But now I no longer have lesstif (I do
>> have lesstif1 installed by default).
>>
>> But there are now many further options (listed below).
>>
>> So I request guidance about which, if any, of the listed packages need to be
>> present before Java will work in conjunction with Opera.
>>
>> The options are:
>>
>> felixk@carrot felixk]$ aptitude search lesstif
>> v amaya-lesstif -
>> p imaze-lesstif - Multiplayer network maze game like MidiMaze
>> v lesstif -
>> p lesstif-bin - user binaries for LessTif
>> p lesstif-dev - development library and header files for LessTif 1.2
>> p lesstif-doc - documentation for LessTif
>> i A lesstif1 - OSF/Motif 1.2 implementation released under LGPL
>> p lesstif2 - OSF/Motif 2.1 implementation released under LGPL
>> p lesstif2-dev - development library and header files for LessTif 2.1
>> v lesstifg -
>> v lesstifg-dbg -
>> v lesstifg-dev -
>> p vim-lesstif - Vi IMproved - LessTif Version
>>
>> In the above list "i A" means installed by default, "p" means
>> available for install and "v" means virtual package.
>>
>> All advice will be gratefully received.
>
>
> I have Sun's java 1.4.2_01 version on my RedHat 7.1 system and it
> works 'fine' with Opera 8.0b1.
>
> Please do the following from an xterm:
>
> ~% cat ~/.opera/javapath.txt
> /usr/java/j2re1.4.2_01/lib/i386
> ~% locate libXm.so
> /usr/X11R6/lib/libXm.so.2
> /usr/X11R6/lib/libXm.so.2.1
> ~% uname --all
> Linux localhost.localdomain 2.4.20-28.7 #1 Thu Dec 18 11:31:59 EST 2003 i686 unknown
> ^P~% opera --version
> Opera 8.0 Beta 1. Build 913 for Linux. Qt library 3.0.5
> ~% opera --debugjava &
> [1] 1028
> ~% 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.
>
>
>
> Then enter . I get:
>
> opera: [Java] Adding '/usr/java/j2re1.4.2_01/lib/plugin.jar' to classpath.
>
> and the java console appears.
>
> F12 should show that Enable Java is selected.
>
> Note if locate libXm.so returns nothing, then you are also unable to
> run any plugins in Opera. If libXm.so.{1 or 2 or 3} is not on your
> system then I 'suspect' the lesstif2 package is a good candidate to
> install.
>

You don't need any of libXm, motif or lesstif to have java in opera.

You will need one of them for plug-in support, in which case it
shouldn't really matter which. To test if you have the necessary
libraries for plug-in support, try to execute the files
"operamotifwrapper", "operamotifwrapper-1", "operamotifwrapper-2",
"operamotifwrapper-3" and "operamotifwrapper-4". If any one of them
prints a message about being a helper application for opera, then you
have what you need. The operamotifwrappers are currently typically
found in /usr/lib/opera/plugins (or wherever opera is looking for
plugins), but the plan is to move it into the same directory as the
opera binary itself (/usr/lib/opera/).

eirik

From:	Andy J.
Subject:	Re: No Java
Date:	Thu, 06 Jan 2005 22:18:32 -0000

> Do you have either lesstif or OpenMotif installed? What version of Java
> do you have?
>

I have no idea what they are but 'which lesstif' and 'which OpenMotif' come
back negative and unless Mandrake installs them by default (I haven't) I'd
say no. As for Java, Java Runtime Environment 1.4.2_06.

Tools -> Advanced -> Plug-Ins gives:-

NS4PluginProxy
application/x-opera-nsplugin -
/usr/lib/opera/plugins/libnpp.so

NS4PluginProxy
application/x-opera-nsplugin -
/home/andrew/lib/opera/plugins/libnpp.so

PD%08h«Ÿ@ Plug-in 1.4.2_06-b03
application/x-java-applet -
application/x-java-applet -
application/x-java-applet -
application/x-java-applet -
application/x-java-applet -
application/x-java-applet -
application/x-java-applet -
application/x-java-applet -
application/x-java-applet -
application/x-java-applet -
application/x-java-applet -
application/x-java-applet -
application/x-java-applet -
application/x-java-applet -
application/x-java-bean -
application/x-java-bean -
application/x-java-bean -
application/x-java-bean -
application/x-java-bean -
application/x-java-bean -
application/x-java-bean -
application/x-java-bean -
application/x-java-bean -
application/x-java-bean -
application/x-java-bean -
application/x-java-bean -
application/x-java-bean -
application/x-java-bean -
/usr/java/j2re1.4.2_06/plugin/i386/ns4/libjavaplugin.so

Andy J.

From:	Felixk Karpfen
Subject:	Re: No Java
Date:	10 Jan 2005 19:26:00 GMT

* Andy J. [2005-01-06]:
>> Do you have either lesstif or OpenMotif installed? What version of Java
>> do you have?
>>

Since I have had similar problems (and similar error messages) since I
upgraded to Opera 7.50, I venture to break in on this thread.

I currently have Java Runtime Environment 1.4.2_01 on my box and was
told that it has a bug and an upgrade of J2RE is needed.

Since I use Java very rarely and it worked in mozilla, I put that
task on the back-burner.

I have since changed my OS to Debian Sarge. No change. Jave still works
in mozilla but not in Opera. But now I no longer have lesstif (I do
have lesstif1 installed by default).

But there are now many further options (listed below).

So I request guidance about which, if any, of the listed packages need to be
present before Java will work in conjunction with Opera.

The options are:

felixk@carrot felixk]$ aptitude search lesstif
v amaya-lesstif -
p imaze-lesstif - Multiplayer network maze game like MidiMaze
v lesstif -
p lesstif-bin - user binaries for LessTif
p lesstif-dev - development library and header files for LessTif 1.2
p lesstif-doc - documentation for LessTif
i A lesstif1 - OSF/Motif 1.2 implementation released under LGPL
p lesstif2 - OSF/Motif 2.1 implementation released under LGPL
p lesstif2-dev - development library and header files for LessTif 2.1
v lesstifg -
v lesstifg-dbg -
v lesstifg-dev -
p vim-lesstif - Vi IMproved - LessTif Version

In the above list "i A" means installed by default, "p" means
available for install and "v" means virtual package.

All advice will be gratefully received.

Felix Karpfen
--
Felix Karpfen
Public Key 72FDF9DF (DH/DSA)

From:	Tullio Chersi
Subject:	Re: No Java
Date:	Mon, 10 Jan 2005 20:55:45 +0100

Felixk Karpfen wrote:
> * Andy J. [2005-01-06]:
>
>>>Do you have either lesstif or OpenMotif installed? What version of Java
>>>do you have?
>>>
>
>
> Since I have had similar problems (and similar error messages) since I
> upgraded to Opera 7.50, I venture to break in on this thread.
>
> I currently have Java Runtime Environment 1.4.2_01 on my box and was
> told that it has a bug and an upgrade of J2RE is needed.
>
> Since I use Java very rarely and it worked in mozilla, I put that
> task on the back-burner.
>
> I have since changed my OS to Debian Sarge. No change. Jave still works
> in mozilla but not in Opera. But now I no longer have lesstif (I do
> have lesstif1 installed by default).
>
> But there are now many further options (listed below).
>
> So I request guidance about which, if any, of the listed packages need to be
> present before Java will work in conjunction with Opera.
>
> The options are:
>
> felixk@carrot felixk]$ aptitude search lesstif
> v amaya-lesstif -
> p imaze-lesstif - Multiplayer network maze game like MidiMaze
> v lesstif -
> p lesstif-bin - user binaries for LessTif
> p lesstif-dev - development library and header files for LessTif 1.2
> p lesstif-doc - documentation for LessTif
> i A lesstif1 - OSF/Motif 1.2 implementation released under LGPL
> p lesstif2 - OSF/Motif 2.1 implementation released under LGPL
> p lesstif2-dev - development library and header files for LessTif 2.1
> v lesstifg -
> v lesstifg-dbg -
> v lesstifg-dev -
> p vim-lesstif - Vi IMproved - LessTif Version
>
> In the above list "i A" means installed by default, "p" means
> available for install and "v" means virtual package.
>
> All advice will be gratefully received.
>
> Felix Karpfen
Java 1.4.2 works with my Opera 8.0b1 although I also have Java 1.5.0
plugins in Mozilla 1.73 and Firefox 1.0. But Opera does not use a Java
plugin and therefore OpenMotif (which I have) is unimportant as far as
Java is concerned. As I wrote in another post, the skychart applet at
www.skyandtelescope.com works always in Opera and randomly in both
Mozilla and Firefox. See also the notice on the skyandtelescope site.
Tullio

From:	Robt. W. Fletcher Jr.
Subject:	Re: No Java
Date:	10 Jan 2005 12:56:01 -0800

Felixk Karpfen writes:

> * Andy J. [2005-01-06]:
> >> Do you have either lesstif or OpenMotif installed? What version of Java
> >> do you have?
> >>
>
> Since I have had similar problems (and similar error messages) since I
> upgraded to Opera 7.50, I venture to break in on this thread.
>
> I currently have Java Runtime Environment 1.4.2_01 on my box and was
> told that it has a bug and an upgrade of J2RE is needed.
>
> Since I use Java very rarely and it worked in mozilla, I put that
> task on the back-burner.
>
> I have since changed my OS to Debian Sarge. No change. Jave still works
> in mozilla but not in Opera. But now I no longer have lesstif (I do
> have lesstif1 installed by default).
>
> But there are now many further options (listed below).
>
> So I request guidance about which, if any, of the listed packages need to be
> present before Java will work in conjunction with Opera.
>
> The options are:
>
> felixk@carrot felixk]$ aptitude search lesstif
> v amaya-lesstif -
> p imaze-lesstif - Multiplayer network maze game like MidiMaze
> v lesstif -
> p lesstif-bin - user binaries for LessTif
> p lesstif-dev - development library and header files for LessTif 1.2
> p lesstif-doc - documentation for LessTif
> i A lesstif1 - OSF/Motif 1.2 implementation released under LGPL
> p lesstif2 - OSF/Motif 2.1 implementation released under LGPL
> p lesstif2-dev - development library and header files for LessTif 2.1
> v lesstifg -
> v lesstifg-dbg -
> v lesstifg-dev -
> p vim-lesstif - Vi IMproved - LessTif Version
>
> In the above list "i A" means installed by default, "p" means
> available for install and "v" means virtual package.
>
> All advice will be gratefully received.

I have Sun's java 1.4.2_01 version on my RedHat 7.1 system and it
works 'fine' with Opera 8.0b1.

Please do the following from an xterm:

~% cat ~/.opera/javapath.txt
/usr/java/j2re1.4.2_01/lib/i386
~% locate libXm.so
/usr/X11R6/lib/libXm.so.2
/usr/X11R6/lib/libXm.so.2.1
~% uname --all
Linux localhost.localdomain 2.4.20-28.7 #1 Thu Dec 18 11:31:59 EST 2003 i686 unknown
^P~% opera --version
Opera 8.0 Beta 1. Build 913 for Linux. Qt library 3.0.5
~% opera --debugjava &
[1] 1028
~% 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.

Then enter . I get:

opera: [Java] Adding '/usr/java/j2re1.4.2_01/lib/plugin.jar' to classpath.

and the java console appears.

F12 should show that Enable Java is selected.

Note if locate libXm.so returns nothing, then you are also unable to
run any plugins in Opera. If libXm.so.{1 or 2 or 3} is not on your
system then I 'suspect' the lesstif2 package is a good candidate to
install.

--
-rwf

From:	Felixk Karpfen
Subject:	Re: No Java
Date:	13 Jan 2005 20:37:13 GMT

* Robt. W. Fletcher Jr. [2005-01-10]:
> Felixk Karpfen writes:
> I have Sun's java 1.4.2_01 version on my RedHat 7.1 system and it
> works 'fine' with Opera 8.0b1.
>
> Please do the following from an xterm:
>
> ~% cat ~/.opera/javapath.txt
> /usr/java/j2re1.4.2_01/lib/i386

Crashed at Square One.
[felixk@carrot felixk]$ cat .opera/javapath.txt
=Blank line=
Empty file.

It appears to be a permissions problem.

Opera validates the entered path, but does not write it to file
(despite pressing the "Apply" button). Next time that I open
"Preferences->Multimedia" the Java path is empty when Opera is run from
"user".

Currently j2re is owned by "root" and all files have permissions of
"755".

This only happens in Debian. Redhat 7.1 had no such problem. It gave
the same output to "opera --debugjava" as that listed below:
> ~% opera --debugjava &
> [1] 1028
> ~% 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.
>
Felix Karpfen
--
Felix Karpfen
Public Key 72FDF9DF (DH/DSA)

From:	Robt. W. Fletcher Jr
Subject:	Re: No Java
Date:	Thu, 13 Jan 2005 15:07:36 -0800

Felixk Karpfen writes:

> * Robt. W. Fletcher Jr. [2005-01-10]:
>> Felixk Karpfen writes:
>> I have Sun's java 1.4.2_01 version on my RedHat 7.1 system and it
>> works 'fine' with Opera 8.0b1.
>>
>> Please do the following from an xterm:
>>
>> ~% cat ~/.opera/javapath.txt
>> /usr/java/j2re1.4.2_01/lib/i386
>
> Crashed at Square One.
> [felixk@carrot felixk]$ cat .opera/javapath.txt
> =Blank line=
> Empty file.
>
> It appears to be a permissions problem.
>
> Opera validates the entered path, but does not write it to file
> (despite pressing the "Apply" button). Next time that I open
> "Preferences->Multimedia" the Java path is empty when Opera is run from
> "user".
>
> Currently j2re is owned by "root" and all files have permissions of
> "755".
>
> This only happens in Debian. Redhat 7.1 had no such problem. It gave
> the same output to "opera --debugjava" as that listed below:

I'm not familiar with Debian, so ...

Do the following from an xterm.

~% locate libjava.so
/opt/blackdown-jdk-1.4.2.01/jre/lib/i386/libjava.so
~% locate libawt.so
/opt/blackdown-jdk-1.4.2.01/jre/lib/i386/libawt.so

The directory /opt/blackdown-jdk-1.4.2.01/jre/lib/i386 is what I add
as the java path (alt t p -> Multimedia -> Java Path. I then select
Enable Java and click on Validate Java path. Opera says 'The Java path
seems to specify a valid directory' I click OK and then exit Opera
.

cat ~/.opera/javapath.txt shows the directory.

Please run a 'user' only.

You initially talked about upgrading to Opera 7.50. Download
either 7.54u or 8.b1 and test it from the download directory. Note:
the following assumes the download directory is /tmp

cd /tmp
tar -zjpf opera-8.0 ... tar.bz2

or
tar -xzpf opera-8.0 ... tar.gz
cd opera-8.0 ... en/
./opera --debugjava &

uname --all
Linux localhost 2.6.10-gentoo-r4 #1 Mon Jan 10 12:07:55 PST 2005 i686 Celeron (Mendocino) GenuineIntel GNU/Linux
opera --version
Opera 8.0 Beta 1. Build 913 for Linux. Qt library 3.0.5

--
-rwf

From:	Tullio Chersi
Subject:	Re: No Java
Date:	Fri, 14 Jan 2005 03:28:44 +0100

Robt. W. Fletcher Jr wrote:
> Felixk Karpfen writes:
>
>
>>* Robt. W. Fletcher Jr. [2005-01-10]:
>>
>>>Felixk Karpfen writes:
>>>I have Sun's java 1.4.2_01 version on my RedHat 7.1 system and it
>>>works 'fine' with Opera 8.0b1.
>>>
>>>Please do the following from an xterm:
>>>
>>>~% cat ~/.opera/javapath.txt
>>>/usr/java/j2re1.4.2_01/lib/i386
>>
>>Crashed at Square One.
>>[felixk@carrot felixk]$ cat .opera/javapath.txt
>>=Blank line=
>>Empty file.
>>
>>It appears to be a permissions problem.
>>
>>Opera validates the entered path, but does not write it to file
>>(despite pressing the "Apply" button). Next time that I open
>>"Preferences->Multimedia" the Java path is empty when Opera is run from
>>"user".
>>
>>Currently j2re is owned by "root" and all files have permissions of
>>"755".
>>
>>This only happens in Debian. Redhat 7.1 had no such problem. It gave
>>the same output to "opera --debugjava" as that listed below:
>
>
>
> I'm not familiar with Debian, so ...
>
> Do the following from an xterm.
>
>
> ~% locate libjava.so
> /opt/blackdown-jdk-1.4.2.01/jre/lib/i386/libjava.so
> ~% locate libawt.so
> /opt/blackdown-jdk-1.4.2.01/jre/lib/i386/libawt.so
>
>
> The directory /opt/blackdown-jdk-1.4.2.01/jre/lib/i386 is what I add
> as the java path (alt t p -> Multimedia -> Java Path. I then select
> Enable Java and click on Validate Java path. Opera says 'The Java path
> seems to specify a valid directory' I click OK and then exit Opera
> .
>
> cat ~/.opera/javapath.txt shows the directory.
>
> Please run a 'user' only.
>
> You initially talked about upgrading to Opera 7.50. Download
> either 7.54u or 8.b1 and test it from the download directory. Note:
> the following assumes the download directory is /tmp
>
>
> cd /tmp
> tar -zjpf opera-8.0 ... tar.bz2
>
> or
> tar -xzpf opera-8.0 ... tar.gz
> cd opera-8.0 ... en/
> ./opera --debugjava &
>
>
> uname --all
> Linux localhost 2.6.10-gentoo-r4 #1 Mon Jan 10 12:07:55 PST 2005 i686 Celeron (Mendocino) GenuineIntel GNU/Linux
> opera --version
> Opera 8.0 Beta 1. Build 913 for Linux. Qt library 3.0.5
>
Opera 8.0 Beta 1. Build 913 for Linux. Qt library 3.3.1
This is what I get on my SuSE Linux 9.1 with Sun Java 1.4.2 working.
Tullio

From:	Eirik Byrkjeflot Anonsen
Subject:	Re: No Java
Date:	Fri, 14 Jan 2005 09:31:16 +0100

Felixk Karpfen writes:

> * Robt. W. Fletcher Jr. [2005-01-10]:
>> Felixk Karpfen writes:
>> I have Sun's java 1.4.2_01 version on my RedHat 7.1 system and it
>> works 'fine' with Opera 8.0b1.
>>
>> Please do the following from an xterm:
>>
>> ~% cat ~/.opera/javapath.txt
>> /usr/java/j2re1.4.2_01/lib/i386
>
> Crashed at Square One.
> [felixk@carrot felixk]$ cat .opera/javapath.txt
> =Blank line=
> Empty file.
>
> It appears to be a permissions problem.

Stupid question, but given the way you've written this, I just have to
ask:

You have made sure that opera has write permission to
..opera/javapath.txt?

>
> Opera validates the entered path, but does not write it to file
> (despite pressing the "Apply" button). Next time that I open
> "Preferences->Multimedia" the Java path is empty when Opera is run from
> "user".

Definitely sounds like opera is not storing your preference in
..opera/javapath.txt.

>
> Currently j2re is owned by "root" and all files have permissions of
> "755".

That's ok. But if the path is not in .opera/javapath.txt, it's not
likely to work in any case.

Also, remember that you have to restart opera to get this to work
after the correct path has been entered into .opera/javapath.txt.

>
> This only happens in Debian. Redhat 7.1 had no such problem. It gave
> the same output to "opera --debugjava" as that listed below:
>> ~% opera --debugjava &
>> [1] 1028
>> ~% 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.
>>

That's odd though. This is not what I'd expect to see when
..opera/javapath.txt is empty. I'd expect the workaround to fail, and
thus java to be disabled on startup.

But maybe the opera startup script (/usr/bin/opera) finds java
somewhere (it does try to autodetect it...), and uses that instead.
And that java fails to work for some mysterious reason...

eirik

From:	Felixk Karpfen
Subject:	Re: No Java
Date:	15 Jan 2005 22:21:35 GMT

* Eirik Byrkjeflot Anonsen [2005-01-14]:
> Felixk Karpfen writes:
>
>> * Robt. W. Fletcher Jr. [2005-01-10]:
>>> Felixk Karpfen writes:
>>> I have Sun's java 1.4.2_01 version on my RedHat 7.1 system and it
>>> works 'fine' with Opera 8.0b1.
>>>
>>> Please do the following from an xterm:
>>>
>>> ~% cat ~/.opera/javapath.txt
>>> /usr/java/j2re1.4.2_01/lib/i386
>>
>> Crashed at Square One.
>> [felixk@carrot felixk]$ cat .opera/javapath.txt
>> =Blank line=
>> Empty file.
>>
>> It appears to be a permissions problem.
>
> Stupid question,

There is no easy cure for stupidity - alas.

> but given the way you've written this, I just have to
> ask:
> You have made sure that opera has write permission to
> .opera/javapath.txt?

And there was the problem - now fixed.

However, it raises another issue.

Quite a few files in my /home/felixk/.opera directory currently belong
to root. That might be related to the routines that I needed to use to
transport Opera to my (new) Debian box. The list reads:

[felixk@carrot felixk]$ ls -l .opera/ | grep root
-rw-r--r-- 1 root root 155694 Dec 17 10:41 OperaOld.adr
-rw-r--r-- 1 root root 21 Dec 17 10:41 cookies4.dat.bak
-rw-r--r-- 1 root root 29904 Dec 17 10:41 default.zip
-rw-r--r-- 1 felixk root 1 Jan 13 19:53 javapath.txt
-rw-r--r-- 1 root root 333 Dec 17 10:41 notes.adr
-rw-r--r-- 1 root root 321 Dec 17 10:41 notes.adr.bak
-rw-r--r-- 1 root root 200521 Dec 17 10:41 op_ok.adr
-rw-r--r-- 1 root root 19734 Dec 17 10:41 opcacert.dat
-rw-r--r-- 1 root root 55217 Dec 17 10:41 opcacrt6.dat
-rw-r--r-- 1 root root 27 Dec 17 10:41 opcert6.dat
-rw-r--r-- 1 root root 12 Dec 17 10:41 opera.gif
-rw-r--r-- 1 root root 11495 Dec 17 10:41 opera.ini
-rw-r--r-- 1 root root 1212 Dec 17 10:41 opera.reg
-rw-r--r-- 1 root root 358 Dec 17 10:41 opera.win
-rw------- 1 root root 17006 Dec 17 10:41 opera6.ini.01.bk
-rw------- 1 root root 15502 Dec 17 10:41 opera6.ini_june30.bk
-rw------- 1 root root 1024 Jan 13 19:53 oprand.dat
-rw-r--r-- 1 root root 58 Dec 17 10:41 opssl.dat
-rw-r--r-- 1 root root 76 Dec 17 10:41 opssl6.dat

Do any of these changing?

SNIP

>
>>
>> This only happens in Debian. Redhat 7.1 had no such problem. It gave
>> the same output to "opera --debugjava" as that listed below:
>>> ~% opera --debugjava &
>>> [1] 1028
>>> ~% opera: [java] There seems to be a preloaded version of Xt.
>>> There is a workaround for this problem in the opera
>
>
> That's odd though. This is not what I'd expect to see when
> .opera/javapath.txt is empty. I'd expect the workaround to fail, and
> thus java to be disabled on startup.

It did.

As flagged, the above output was only achieved in RedHat - which,
presumably had the correct read permissions.

After fixing up the file ownership and following the advice in the email
from Robt. W. Fletcher I now get:

[felixk@carrot felixk]$ opera --debugjava &
[1] 3147

[felixk@carrot felixk]$ opera: [java] There seems to be a preloaded
version of X t.

There is a workaround for this problem in the opera
startup script. If that workaround fails, opera will..

SNIP

[felixk@carrot felixk]$

[felixk@carrot felixk]$ opera: [Java] Adding
'/home/felixk/j2re1.4.2_01/lib/plugin.jar' to classpath.

Problem solved. The java "clock demo" now works in Opera 7.50.

Many thanks to both for the help.

Felix Karpfen
--
Felix Karpfen
Public Key 72FDF9DF (DH/DSA)

From:	Eirik Byrkjeflot Anonsen
Subject:	Re: No Java
Date:	Tue, 11 Jan 2005 10:33:57 +0100

"Robt. W. Fletcher Jr" writes:

> Eirik Byrkjeflot Anonsen writes:
>
>>
>> You don't need any of libXm, motif or lesstif to have java in opera.
>
> Are you sure about that?
>
> 1. started Opera (no pages opened)
>
> 2. java was enabled.
>
> 3. attached gdb to the running Opera pid
>
> ~% gdb /usr/local/lib/opera/8.0-20050104.1/opera 17863
> GNU gdb 6.0
> Copyright 2003 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "i686-pc-linux-gnu"...
> (no debugging symbols found)...Using host libthread_db library "/lib/libthread_d b.so.1".
>
> Attaching to program: /usr/local/lib/opera/8.0-20050104.1/opera, process 17863
> Reading symbols from /opt/blackdown-jdk-1.4.2.01/jre/lib/i386//libawt.so...
> (no debugging symbols found)...done.
> Loaded symbols for /opt/blackdown-jdk-1.4.2.01/jre/lib/i386//libawt.so
>
> [snip]
>
> Reading symbols from /opt/blackdown-jdk-1.4.2.01/jre/lib/i386/libXm.so.3...
> done.
> Loaded symbols for /opt/blackdown-jdk-1.4.2.01/jre/lib/i386/libXm.so.3
> Reading symbols from /usr/X11R6/lib/libXp.so.6...done.
>
> [snip]
>
> Loaded symbols for /lib/libncurses.so.5
> Reading symbols from /usr/X11R6/lib/libXcursor.so.1...done.
> Loaded symbols for /usr/X11R6/lib/libXcursor.so.1
> Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/xomGeneric.so.2...
> done.
> Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/xomGeneric.so.2
> 0xffffe410 in ?? ()
> (gdb)
>
> My java comes with libXm.so.3 -- which is clearly loaded.
>

Yes, so you do not have to install libXm yourself... Which was the
main issue here...

Technically, Java's standard user interface library is based on libXm,
but this is usually not of concern to the end user. (Though it's a
source of endless problems for developers...)

eirik