Bug 691964

Summary: double-clicking on a .jar file should launch the java application
Product: Red Hat Enterprise Linux 6 Reporter: Brian Fristensky <frist>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.2CC: ccecchi, draxx31, nekohayo, tbzatek, tsmetana
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 16:08:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Brian Fristensky 2011-03-30 01:48:40 UTC
Description of problem:

Double-clicking on a Java .jar file should launch the .jar file with

java -jar

 Since the
whole point of .jar files is to be self-contained executables,
it makes sense that executing it should be the default.

Version-Release number of selected component (if applicable):


How reproducible:
Opening a .jar file in the file-roller has always been the default
in Fedora.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
The default is to open the .jar file in the file roller.

Expected results:
 Since the
whole point of .jar files is to be self-contained executables,
it makes sense that executing it should be the default.

Additional info:

Comment 1 Tomáš Bžatek 2011-03-30 12:01:21 UTC
Could you do gvfs-info on the file and check the reported MIME type?

Comment 2 Brian Fristensky 2011-04-08 15:04:45 UTC
Sorry, I thought I had posted this outut last week. Here it is:

display name: getbirch.jar
edit name: getbirch.jar
name: getbirch.jar
type: regular
size:  10363875
attributes:
  standard::type: 1
  standard::name: getbirch.jar
  standard::display-name: getbirch.jar
  standard::edit-name: getbirch.jar
  standard::copy-name: getbirch.jar
  standard::icon: application-x-java-archive, gnome-mime-application-x-java-archive, package-x-generic, application-x-generic
  standard::content-type: application/x-java-archive
  standard::fast-content-type: application/x-java-archive
  standard::size: 10363875
  standard::allocated-size: 10366976
  etag::value: 1301164748:0
  id::file: l64770:2621697
  id::filesystem: l64770
  access::can-read: TRUE
  access::can-write: TRUE
  access::can-execute: FALSE
  access::can-delete: TRUE
  access::can-trash: TRUE
  access::can-rename: TRUE
  time::modified: 1301164748
  time::access: 1301448740
  time::changed: 1301448699
  unix::device: 64770
  unix::inode: 2621697
  unix::mode: 33204
  unix::nlink: 1
  unix::uid: 501
  unix::gid: 500
  unix::rdev: 0
  unix::block-size: 4096
  unix::blocks: 20248
  owner::user: brian
  owner::user-real: Brian Fristensky
  owner::group: brian

Comment 3 draxx31 2011-11-29 08:18:44 UTC
Hello,

I have the same behaviour on Fedora 16.

It is not possible to execute a custom command for any file by doing "open with"...

Comment 4 Fedora End Of Life 2012-08-16 16:08:07 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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" (top right of this page) 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 5 Brian Fristensky 2012-08-16 16:19:56 UTC
Even in the current RHEL 6.2, .jar files still default to being opened by the file roller, rather than being executed, which I see as a usability issue. The idea is to be able to give users a one click way to run a Java program distributed as a jar.