Author
Topic: aptal karga (foolish crow) (Read 72506 times)

it does work on my windows xp and fedora 4. there's one difference though, in untrusted mode (windowed) on windows, javaws displays a warning about connections to cave (localhost). it goes on to connect if user presses cancel :roll:

have you modified any configuration files ? maybe re-installing java6 may help.

on the good side, fullscreen exlusive mode is now supported on my fedora 4

No, nothing has been modified. This is my girlfriend's machine with a brand new Java6 installation (i also tried to reinstall but it didn't help). I remember a similar problem that i had with a Java6 beta and webstart (webstart couldn't access the server to load the jars). The solution was to modify some Java-config file to use an old style...i don't know...something to do with network stuff. I can't remember exactly what it was...

Did that...the Console says something about 1.5....so i assume that 1.5 is actually being used. However, the results are exactly the same.

Edit: Can't run karga with 1.5 on this machine. The exception is the same. But i did ran Karga on this machine some month ago with 1.5. I've no idea what's wrong here.... Maybe the problem comes from the fact that even when running it with 1.5, the javaws is the one from 1.6.

all my ideas about java bug were depending on the fact that karga runs with java 5 but not with 6. if that's not the case then certainly there's a problem on that machine

as direct connection works on that machine you can workaround the problem by disabling proxy usage, that is: on web start configuration panel, in general tab, in network seettings dialog, select direct connection option

No, it is a Java6 problem...just not like we thought with Java6 itself but with the webstart client. It defaults to do it's network connection like the browser does. But the browser is set to "direct connection". The webstart client doesn't seem to get it and uses a manual proxy setting instead which is present in the browser but not enabled. Java5's webstart client seemed to be able to handle this correctly, because that inactive setting is present in the browser from the first day of operation of this machine. I used it for setting up the machine and disabled it right after that.

Edit: Should be easy to try this yourself. Just enter a proxy in the browser and don't use it but "direct connection". Set the Java network setting to "from browser" and see if it happens on your machine too.