Hide Forgot
Description of problem: .jar apps open in archive manager instead of the Java runtime in Nautilus. How reproducible: Steps to Reproduce: 1. Get a .jar executable from somewhere 2. Find it in Nautilus 3. Double click it Actual results: It opens in file-roller. Java runtime isn't found even in "Open with" options. One has to create a .desktop file manually or run the app in command line, resulting in a bad user experience. Expected results: It should run in the Java runtime, or at least Java runtime should be in the "Open with" list. Additional info:
Hi! this is not going to happen. Each jar should have launcher. Otherwise it is correct that it is considered archive. Executing any arbitrary jar from network is not only dangerous (as any other executable binary...) but the ar even do not need to be execute-able (to be execute-able it must have mainclass in manifest). There is a lot of closed bugs on this topic. And imho the universe still did not changed.
s/ar/jar
Hi, Unfortunately I found only one bug report about that and even that was not exactly closed, but left to expire due to the release going end of life. It is sometimes really difficult to search bug trackers. How excatly is running an app via a launcher any safer than running it directly? And does Fedora's Nautilus refuse to run native binaries, too? I haven't yet tested the later and do not at this moment have a Fedora machine on hand.
And where exactly is defined that each .jar "should" have a launcher? According to Oracle (1), Java apps are supposed to be ran by double-clicking the .jar or launching them from command line via java -jar. Instead, they talk about assoicating .jar files with JRE. 1) https://netbeans.org/kb/articles/javase-deploy.html
Okay, I checked it out, Fedora seems to not run native apps neither from Nautilus, so now it makes sense to me. Closing.
Sorry for this commend flood. It seems that Nautilus won't run the apps in /bin, but will happily run, say, AppImages once they have correct permissions. Running native code or .desktop files is not any safer than running Java applications.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora 'version' of '24'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 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 this bug is closed as described in the policy above. 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.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.