.desktop file security adds shebang

[typo]

Michael Pyne wrotes: ( http://lists.freedesktop.org/archives/xdg/2009-February/010209.html )
> If the file is made executable automatically it is given a "#!/usr/bin/env
> xdg-open" header as well if it did not already have a #! header so that
> running the file from the command line will do the right thing.

The feature "runnig a .desktop file from command line" has nothing in common with the ".desktop file security". If you want to use the shebang for .desktop files, you have to use it in all .desktop files and to specify it in the Desktop Entry Specification. But the shebang mechanism is old style and not cross-plattform. What about using these files with the Windows CMD? You are able to execute windows executables from the command line although they are no native executables and although they have no shebang. So why don't do the same detection with desktop entries?

Implement this in order to fix this bug:
* Only set execution bit in order to activate an desktop entry (no shebang)
* Implement execution of desktop entries from command line

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Tanks in advance.

[Fabio Marconi (fabiomarconi)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage .

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[Fabio Marconi (fabiomarconi)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Fabio Marconi (fabiomarconi)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!