Bug 858851 - javaws.desktop should be added to defaults.list to handle application/x-java-jnlp-file
Summary: javaws.desktop should be added to defaults.list to handle application/x-java-...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: icedtea-web
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: jiri vanek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-19 19:36 UTC by Deepak Bhole
Modified: 2014-02-05 22:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 22:48:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Deepak Bhole 2012-09-19 19:36:25 UTC
Currently there is no default association for application/x-java-jnlp-file in defaults.list. As a result, Firefox does not know how to handle jnlp files and does not show IcedTea-Web's javaws as a possible option to open the file with.

I have provenpackager status and don't mind adding the line to defaults.list myself (F16/F17/F18) if it is approved here.

This is the line that needs to be added:
application/x-java-jnlp-file=javaws.desktop;

Comment 1 Fedora End Of Life 2013-01-16 12:23:16 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Fedora End Of Life 2013-02-13 12:39:00 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Deepak Bhole 2013-02-15 21:11:49 UTC
Still present in F18.

Comment 4 Bastien Nocera 2013-02-19 13:55:23 UTC
(In reply to comment #0)
> Currently there is no default association for application/x-java-jnlp-file
> in defaults.list.

There doesn't need to be one, you just need one application handling the mime-type, which javaws doesn't seem to do.

Comment 5 Deepak Bhole 2013-02-25 18:53:14 UTC
What does javaws need to do to make that happen? The .desktop file currently has:
MimeType=application/x-java-jnlp-file;

But it doesn't seem to always work and Firefox ends up not knowing what to open JNLP files with.

Comment 6 Deepak Bhole 2013-02-25 18:54:39 UTC
Hi Bastien, please see comment #5.

Comment 7 Bastien Nocera 2013-02-26 10:07:22 UTC
(In reply to comment #6)
> Hi Bastien, please see comment #5.

Did you forget to run update-desktop-database after installing your package?

Comment 8 Deepak Bhole 2013-02-26 14:00:22 UTC
(In reply to comment #7)
> (In reply to comment #6)
> > Hi Bastien, please see comment #5.
> 
> Did you forget to run update-desktop-database after installing your package?

Nope, we run that as well in %post:
http://pkgs.fedoraproject.org/cgit/icedtea-web.git/tree/icedtea-web.spec?h=f18#n137

Whats odd is that it does sometimes work fine, and at others it doesn't (sometimes meaning if it works after an install, it always works otherwise it never works for that install).

Comment 9 Fedora End Of Life 2013-12-21 15:06:18 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 10 Fedora End Of Life 2014-02-05 22:48:07 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.