Bug 6746

Summary:	Google chrome reports IcedTea as "out of date" when running Runescape. Firefox - applet crashes.
Product:	Mageia	Reporter:	Lee Forest <lee8oi>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	luigiwalser, shlomif
Version:	2
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	icedtea-web-1.2-4.mga2.src.rpm	CVE:
Status comment:

Description Lee Forest 2012-07-11 03:48:28 CEST

Description of problem:
When loading Runescape in Chrome it reports IcedTea as 'out of date'. Loading runescape in Firefox caused the applet to crash without error. Rebuilding IcedTea source package fixed crash in Firefox. But chrome is still reporting it as out of date.

Version-Release number of selected component (if applicable):
google-chrome 21.0.1180.15 beta
Firefox 10.0.5

How reproducible:


Steps to Reproduce:
1. visit runscape.com in firefox or chrome.
2. try to play the game

David Walser 2012-07-11 03:50:11 CEST

CC: (none) => luigiwalser
Source RPM: (none) => icedtea-web-1.2-4.mga2.src.rpm

Comment 1 Lee Forest 2012-07-11 03:52:23 CEST

Well...technically all java apps not just Runescape but that's the game I used to test.

Comment 2 Shlomi Fish 2012-07-11 14:44:56 CEST

(In reply to comment #1)
> Well...technically all java apps not just Runescape but that's the game I used
> to test.

Hi!

I am able to run the RuneScape applet fine in Firefox on Mageia Linux 2 x86-64 with updates_testing enabled and the Mageia shipped Firefox 10.0.5 ESR/etc. I was able to register a character and start playing.

Regards,

-- Shlomi Fish

CC: (none) => shlomif

Comment 3 Manuel Hiebel 2012-07-11 17:58:50 CEST

works fine here too, lee, have you old lib of testing or what ?

Comment 4 Lee Forest 2012-07-11 22:22:43 CEST

It works on and off for me. Works aside from the issue with Chrome beta showing icedtea as out of date. But I'm guessing that's their problem not yours. Sorry. I was having problems and was told to file a bug report. Maybe it's something in my home config files messing with things. Sorry.

Status: NEW => RESOLVED
Resolution: (none) => INVALID