Comment 10 for bug 702452

I have been working a similar problem which I put into the system as https://bugs.launchpad.net/unity/+bug/799023 - now marked as a duplicate of this bug.

I have found a workaround for the two machines I have available each with several wine applications (Dreamweaver, PaintShop, Irfanview, Notepad++ etc). The workaround is to comment out ALL the StartupWMClass=Wine lines in the .desktop files in ~/.local/share/applications which is where wine installs them in a series of subfolders.

The only exception is picasa which launches via a complex script file and in this case the picasa.desktop file has to be copied from /usr/share/applications to ~/.local/share/applications and the line StartupWMClass=Wine appended to get it to associate correctly and not show the wine icon as suggested by andypiper

A terminal command which follows should comment out all the lines starting with StartupWMClass=Wine. Copy and paste as a single long line and run from the home folder. It worked for me but I suggest backing up at least ~/.local and preferably everything first!

find $HOME/.local/share/applications -name '*.desktop' -exec sed -i 's/^StartupWMClass=Wine/#StartupWMClass=Wine/' '{}' \;

I am not sure I understand why the workaround works but hope it will give some more clues to those sorting out the problem and a short term fix for others to try. I am using a MSI Wind U100 fully with a updated 11.04, unity3d and the latest wine from the wineHQ PPA