© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Another reason this is a bug is due to the way nautilus will handle files that are not executable but have the correct extension.
For example, on my system I've set up an association for jar files to be executed by the jvm. This is great if the jar file is intended to be executed. It works just like I requested above. Unfortunately it does the same thing for jar files that are not intended to be executed and don't have the execute bit set. What should happen in this case is that the file should be opened by the archive manager. Not all jar files are suitable for direct execution by the JVM. The way to differentiate them on systems with binfmt-misc installed is by looking at the execute bit.