Version: 4.0 (using KDE 3.1.9) Compiler: gcc version 3.2.2 OS: Linux (i686) release 2.4.20-gentoo-r2 When using a secure java applet that needs to install a certificate and be granted permissions (for example for reading local files) that is ignored, there is no dialog asking to accept the certificate or grant permissions. I'm using sun jdk 1.4.1.03
http://amagerbanken.net/amagerbanken/netbank.nsf/Netbank?OpenFrameset and then click "log op" (the second log link on top)
This is ***still*** driving me crazy. I tried adding a grant in ~/.kde/share/apps/kjava/kjava.policy grant codeBase "https://web2.prod.bec.dk/-" { permission java.io.FilePermission "/home/anders/WEBBANK/0001460.usf", "read, write, delete, execute"; permission java.util.PropertyPermission "user.home", "read"; }; This has the following results: 1) in the java console, i get this output: Class could not be loaded: dk.bec.signon.client.ds.web.Logon Backtrace: java.lang.ClassNotFoundException: Class:dk.bec.signon.client.ds.web.Logon at org.kde.kjas.server.KJASAppletClassLoader.findClass (KJASAppletClassLoader.java:244) at org.kde.kjas.server.KJASAppletClassLoader.loadClass (KJASAppletClassLoader.java:277) at org.kde.kjas.server.KJASAppletStub$2.run(KJASAppletStub.java:179) at java.lang.Thread.run(Thread.java:536) (without the grant, the output i get relates to missing permission) 2) In the STDERR for the konqueror process, i see Aug 3, 2003 10:45:41 AM java.util.prefs.FileSystemPreferences$3 run WARNING: Could not create system preferences directory. System preferences are unusable. Aug 3, 2003 10:46:13 AM java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode WARNING: Could not lock System prefs.Unix error code 4. Aug 3, 2003 10:46:13 AM java.util.prefs.FileSystemPreferences syncWorld WARNING: Couldn't flush system prefs: java.util.prefs.BackingStoreException: Couldn't get file lock.
i seem to have a similar (if not the same) problem in bug #65191 (i tried the kjava.policy thing, but it didn't work out: kjas: ERROR: could not parse length out of: kjas: ERROR: could not parse length out of: kjas: ERROR: could not parse length out of: ....) anyway, perhaps someone can confirm my bug as a dupe... best regards Thilo
*** This bug has been marked as a duplicate of 65602 ***