Problems with Java Web Start (java 1.4.2 - 1.5.0) on Slackware
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Problems with Java Web Start (java 1.4.2 - 1.5.0) on Slackware
Hello.
I have a problem with Java Web Start from j2sdk1.4.2_04 and j2sdk1.5.0_1 on Slackware 10 with kde and glibc upgraded to -current. When I run /usr/lib/java/jre/javaws /javaws it starts and do nothing while using all CPU power. The funny thing is that old version of Java Web Start (1.0.1 as opposed to 1.2 which shipped with j2sdk1.4.2 and j2sdk1.50 ) works just fine. I suspect it somehow related to glibc upgrade but the sad thing is that I dont remember whether it worked before my upgrades.
I'll try it but currently I have no time. Andit will screw up my bright&shiny KDE 3.3 .
If you can please try to run javaws on fully update slack-current.
Be very carefull when removepkg glibc as you may able to do just nothing after that as nearly all
programs are linked to libc (rm, bash, ls, login etc..).
I would even not try the upgradepkg --reinstall, instead I would boot from a live CD to do this
(to be sure) . It happened to me once (I solved the problem by copy the libc.so from the live
slackware CD to /lib of my root partition)
Thanks for pointing that out keefaz, cause I have no idea that would happen. BUT shouldn't pkgtool and installpkg, removepkg etc. compiled statically? So, after removing glibc and installpkg again, without logging out should be fine? Correct me if I am wrong. am still learning.
There are not binaries executables, they are plain text scripts that rely on binaries compiled
with libc (/bin/dialog, /bin/rm, /bin/mkdir, /bin/chmod, /bin/cat...)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.