Comment 21 for bug 635223

I tried to figure out the ramifications of this and it seems to be pretty tangled up. Giving a high risk of breakage if we rush it at this late point in the cycle.

Here's what I know:

 * The following modules are based on the assumption that they deal with desktop ids: zeitgeist, zeitgeist-fts-extension, zeitgeist-gio, unity, libunity, unity-place-applications (perhaps also unity-place-files)

 * bamf and the launcher also breaks on Wine apps: When running a Wine app I get a generic Wine icon (the wineglass one) in the launcher with title "Wine Windows Program Loader". Clicking on focuses the app all right. If I persist the Wine icon in the launcher (wing off "Keep in launcher") and close the app, I can not launch the app again, but get the error dialog: "The file 'wine' is not marked as executable. If this was downloaded or copied from an untrusted source, it may be dangerous to run. For more details, read about the executable bit."

So pretty much everything in Unity except the panel has to be audited in order to provide a smooth experience here.

Solution:
 * If my analysis above turns out to be over dramatic we can maybe land it as an SRU if the desktop team agrees

 * If my analysis turns out to contain about the right amount of drama we can land the required workarounds in Natty

 * Personally I'd prefer that Wine apps start following the xdg menu spec to the letter, in which case it ought to "just work". This is definitely out of scope for maverick, but could be a target for Natty, but afaik, this is really out of our hands. We could engage upstream here.