Bug 510492

Summary: webstart broken out-of-the-box in F11
Product: [Fedora] Fedora Reporter: Máirín Duffy <duffy>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 11CC: dbhole, gecko-bugs-nobody, langel, lkundrak, mjw, mjw, pfrields, stickster
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-07-09 14:28:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Máirín Duffy 2009-07-09 13:43:41 UTC 
Description of problem:

here's the free webinar / demo site i tried to open with icedtea:

https://sas.elluminate.com/site/external/jwsdetect/playback.jnlp?psid=2009-06-26.0807.C.CC38C635461B724615945F6314D636.vcr

i've got

java-1.6.0-openjdk-plugin-1.6.0.0-22.b16.fc11.x86_64
java-1.6.0-openjdk-devel-1.6.0.0-22.b16.fc11.x86_64
java-1.6.0-openjdk-1.6.0.0-22.b16.fc11.x86_64
java-1.6.0-openjdk-demo-1.6.0.0-22.b16.fc11.x86_64


I go to the site. Asks me to download a jnlp or open with icedtea. I choose open with icedtea, and nothing happens.

Download jnlp and try to run on command line:

[duffy@Aiko ~]$ javaws ~/Download/play.jnlp 
netx: No base directory (contains cache and other data)

Try /tmp as a basedir:

 javaws -basedir /tmp ~/Download/play.jnlp 

Finally it works. Success! 

So why doesn't it work through the GUI? Why doesn't it work out-of-the-box?
Comment 1 Máirín Duffy 2009-07-09 13:44:13 UTC 
browser is

firefox-3.5-0.20.beta4.fc11.x86_64
Comment 2 Paul W. Frields 2009-07-09 14:03:02 UTC 
Same behavior in firefox-3.5-1.fc11.x86_64.
Comment 3 Mark Wielaard 2009-07-09 14:28:14 UTC 
This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=507870 which does contain a workaround, but it is a very annoying bug indeed.

*** This bug has been marked as a duplicate of bug 507870 ***