Page 1 of 1
[SOLVED] Problem running CGoban3 with JavaWebStart
Posted: 28. Sep 2010, 03:07
by Dennola4
Hi there.
EDIT: ****this may not be a Salix issue but I contacted admin@KGS and they said:
Hi Dennis P,
Well, it doesn't seem wise to run the software with sudo...
Anyway I know nothing about Salix OS. So it's hard for me to help. Try checking the permissions on your computer.
Regards,
glue
----------------------------------------------------------------------------------------------------------------------------------------------------------
Here's the deal:
My goal is to run a working version of Cgoban3 from my machine so that I can (a) use it as a client to play on KGS and (b) use it offline to review games in Smart Go Format (SGF).
I know that my Java Web Start is working because the Web Start link on this page works:
http://panda-igs.joyjoy.net/java/gGo/
Yet on this page it does not:
http://www.gokgs.com/download.jsp
I have attempted to decipher the error messages and the sense I get (since I can't actually understand what I'm reading) is that there is a permissions problem. So I ran:
Code: Select all
sudo javaws http://files.gokgs.com/javaBin/cgoban.jnlp
....but still no good:
Code: Select all
ava.io.IOException: Cannot run program "/usr/lib/java": java.io.IOException: error=13, Permission denied
at java.lang.ProcessBuilder.start(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at com.sun.javaws.JnlpxArgs.execProgram(Unknown Source)
at com.sun.javaws.Launcher.prepareResources(Unknown Source)
at com.sun.javaws.Launcher.prepareAllResources(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.prepareToLaunch(Unknown Source)
at com.sun.javaws.Launcher.launch(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: java.io.IOException: error=13, Permission denied
at java.lang.UNIXProcess.<init>(Unknown Source)
at java.lang.ProcessImpl.start(Unknown Source)
... 13 more
Any ideas?
Re: *Help with (possible) permissions issue*
Posted: 1. Oct 2010, 20:02
by Dennola4
Update: <bioterror> was kind enough to try to solve this issue today on Salix IRC channel....
....no luck so far, but wanted to say thanks for the help.
Re: *Help with (possible) permissions issue*
Posted: 1. Oct 2010, 20:20
by Shador
Dennola4 wrote:Cannot run program "/usr/lib/java"
This seems weird as it is trying to execute what actually is a directory. Therefor it obviously has to fail.
Interestingly that problem doesn't occur on my 64-bit system, which indicates that there has to be some difference between our systems and as I can't reproduce the issue makes it harder to solve.
First of all is the error output any different when you don't run it with sudo?
I guess by the way you're using sudo you also changed sudos defaults, did you and in which way?
Which packages of jre and jdk do you have installed? And which versions?
Re: *Help with (possible) permissions issue*
Posted: 1. Oct 2010, 20:32
by rhadamanthys
Downloading the jar file
Code: Select all
wget http://files.gokgs.com/javaBin/cgoban.jar
(this url is inside the jnlp) and starting it with
seems to work here. Don't know why webstart doesn't work.
Re: *Problem running CGoban3 with JavaWS*
Posted: 2. Oct 2010, 06:29
by Dennola4
rhadamanthys: your solution works here too. Thank you.
Shador: rhadamantys's solution seems to work, but to answer your questions (in case you want to trouble-shoot why Salix is having difficulty with this WebStart link):
First of all is the error output any different when you don't run it with sudo?
No -- the output is identical.
I guess by the way you're using sudo you also changed sudos defaults, did you and in which way?
I used
visudo to change sudoers file:
Code: Select all
dennis[Desktop]$ sudo cat /etc/sudoers
# sudoers file.
#
# This file MUST be edited with the 'visudo' command as root.
# Failure to use 'visudo' may result in syntax or file permission errors
# that prevent sudo from running.
#
# See the sudoers man page for the details on how to write a sudoers file.
#
# Host alias specification
# User alias specification
# Cmnd alias specification
# Defaults specification
# Runas alias specification
# User privilege specification
root ALL=(ALL) ALL
# Uncomment to allow people in group wheel to run all commands
%wheel ALL=(ALL) ALL
# Same thing without a password
%wheel ALL=(ALL) NOPASSWD: ALL
%wheel ALL=(ALL) NOPASSWD: /usr/sbin/pppd call cdma
%wheel ALL=(ALL) NOPASSWD: /usr/sbin/ppp-off
# Samples
# %users ALL=/sbin/mount /cdrom,/sbin/umount /cdrom
# %users localhost=/sbin/shutdown -h now
Which packages of jre and jdk do you have installed? And which versions?
Code: Select all
dennis[~]$ su
Password:
root[dennis]# updatedb
root[dennis]# slocate jre jdk
/var/log/packages/jre-6u20-i586-1
/var/log/scripts/jre-6u20-i586-1
/etc/profile.d/jre.csh
/etc/profile.d/jre.sh
/usr/lib/jre1.6.0_20
/usr/share/icons/gnome-colors-common/24x24/apps/openjdk-6.xpm
/usr/share/icons/gnome-colors-common/22x22/apps/openjdk-6.xpm
/usr/share/icons/gnome-colors-common/32x32/apps/openjdk-6.xpm
/usr/share/icons/gnome-colors-common/16x16/apps/openjdk-6.xpm
/usr/share/icons/gnome-colors-common/scalable/apps/openjdk-6.xpm
/usr/lib/java/lib/servicetag/jdk_header.png
/usr/lib/perl5/vendor_perl/5.10.1/i486-linux-thread-multi/XML/Parser/Encodings/x-sjis-jdk117.enc
Hopefully these are proper answers.
Re: *Problem running CGoban3 with JavaWS*
Posted: 2. Oct 2010, 11:51
by rhadamanthys
Just for curiosity I installed the jdk package instead of jre. (32bit)
And now webstart works.
Re: *Problem running CGoban3 with JavaWS*
Posted: 2. Oct 2010, 19:40
by Dennola4
rhadamanthys wrote:Just for curiosity I installed the jdk package instead of jre. (32bit)
And now webstart works.
YES. It works now. Thank you both very much for your help.
Re: [SOLVED] Problem running CGoban3 with JavaWebStart
Posted: 2. Oct 2010, 20:33
by Shador
Interesting this might indicate a bug with the Slackware JRE package or maybe even an upstream bug in the source code deployed by Sun. I'll try to have a look at the problem when I have time, but that could take a while.