I believe you are seeing a generic javaws bug that is unfortunately a change in behavior of glibc/waitid Juergen take a look at 6188963, Hui believes you can just switch in waitpid instead of waitid. btw the 1.5 32bit JVM should also work on your machine too, but the javaws has the same issue

regards
calvin


Don Appleman wrote:

Good afternoon --

I'm new to the list, but first looked through the archives and found nothing on this issue.

I'm running Fedora core 3 on amd64, with kernel 2.6.9-1.667. There is no javaws bundled with Sun's amd64 JDK1.5.0, and the i386 javaws bundled with Sun's jdk1.4.2_06 consumes 100% CPU and never displays the Web Start dialog. This led me to blackdown.org. Love your work.

I downloaded and installed the blackdown jre (j2re-1.4.2-rc1-linux-amd64.bin), & the blackdown jdk (j2sdk-1.4.2-rc1-linux-amd64.bin). In both cases I find that, unfortunately, javaws behaves the same as Sun's javaws from their jdk1.4.2_06; that is, it appears to consume 100% of CPU, and never displays the Web Start dialog.

Has anyone else out there used javaws under Fedora for amd64? If so, what versions of the relevant software did you use, and did you have to engage in any trickery or magic to get it to work?

Much TIA.

Don Appleman




--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Reply via email to