Red Hat Bugzilla – Bug 502318
Runescape claims openjdk won't run its signed applet
Last modified: 2010-05-27 09:05:02 EDT
Description of problem:
Attempting to run Runescape. Runescape claims it can't run the signed version of the applet. This worked perfectly in Fedora 10 -- I was able to use the signed applet as well as their 3D mode.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install openjdk-plugin
2. Goto runescape.com via firefox
3. Click on "Free Users click here to play"
4. Runescape.com responds with:
" You are seeing this page because we could not start RuneScape on your computer in 'signed' mode. This means that you did not (or were not able to) grant permission to RuneScape to run as it normally does. To avoid seeing this page again, please ensure that you accept the pop-up security warning that appears a few seconds after loading the game. If this pop-up does not appear, try rebooting your machine and make sure you click 'Yes' when asked if you want to trust the RuneScape applet."
runescape works, but in unsigned mode
runescape working in signed mode
Created a new user to make sure it wasn't anything screwed up with my firefox setup. New user also could not run the signed applet.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
The same problem exists with the following versions:
When I run firefox in bash, I get this output at the same time that I get the page that says "You are seeing this page because we could not start RuneScape on your computer in 'signed' mode. This means that you did not (or were not able to) grant permission to RuneScape to run as it normally does.":
java.lang.RuntimeException: Failed to handle message: handle 67154749 Thread[Thread-1,5,main]
Caused by: java.lang.NullPointerException
at java.security.AccessController.doPrivileged(Native Method)
... 2 more
Please ignore my last message with the RuntimeException - I tried to run Runescape on another Fedora 11 machine with the same versions, and I got the signed mode complain page but no errors appeared on the bash window!
How could we debug this?
Created attachment 347717 [details]
stderr from firefox with ICEDTEAPLUGIN_DEBUG=true
I started firefox with the following command and navigated to Runescape until the signed mode complain page appeared. I attached the stderr.
ICEDTEAPLUGIN_DEBUG=true firefox > /tmp/out.txt 2> /tmp/err.txt
Thanks for the log. I am not really sure why it is not working on your side. Every time I try to load it, it works for me.
Can you also post the Java logs? They would be quite helpful... to get the java logs, run the same way you did before (with ICEDTEAPLUGIN_DEBUG=true from the terminal) .. the java logs then end up in ~/.icedteaplugin/java.std* files.
Created attachment 347847 [details]
Here is the ~/.icedteaplugin/java.stderr
The ~/.icedteaplugin/java.stdout file is empty.
When you ran it to get those logs, did it still fail? The logs seem to indicate that it worked and was then closed properly..
Hi Juhani. Please ignore Comment #9. I have identified the problem. It will be fixed upstream shortly. Thanks!
Has the patch for this bug been submitted?
I'm also having this problem and was curious on the status of the fix you mentioned.
The patch has been committed upstream. We are working on the Fedora side packages and hope to have it up soon.
Runescape appears to be happy with Fedora 11 + updates now.
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: