> Because of that, Wine and associated applications (winecfg, wine uninstaller etc.) cannot be started from the desktop menu
Wine in desktop menu
--------------------
AFAIK *Wine* itself could never be started from the desktop menu. If at all this might be possible if you enable the "Virtual Desktop" in winecfg (but usually people are only interested in the Windows applications, not in seeing the Windows desktop).
There's wine.desktop, but this does neither start Wine itself, nor does it add a launcher to the menu (NoDisplay=true). It only makes native file type associations, so it tells your system that it may start e.g. an .exe *with* Wine. For security reasons wine.desktop is not "activated" in the packages, but only shipped as an example.
Quoting /usr/share/doc/wine/README.Debian.gz:
~~~~~
To enable system-wide support for .exe files execute the following
command (replace /usr/share/doc/wine with
/usr/share/doc/wine-development if you use wine-development):
$ sudo cp /usr/share/doc/wine/examples/wine.desktop /usr/share/applications/
~~~~~
> /usr/share/desktop-directories/wine-Programs.directory
> /usr/share/desktop-directories/wine-wine.directory
> Yes, these files do create a menu (sub)section for installed Wine programs.
> This is really useful for MATE, Cinnamon, XFCE and other non-GNOME/non-Unity DEs.
But on these DEs the files in ~/.local are still created by Wine, right? So it still works!?
> and Windows binaries cannot be run directly from the file manager using development version of Wine.
True, due to security reasons your system will not know how to launch e.g. an .exe, see above.
[ Quoting some previous comments with ">" ]
> Because of that, Wine and associated applications (winecfg, wine uninstaller etc.) cannot be started from the desktop menu
Wine in desktop menu ------- ------
-------
AFAIK *Wine* itself could never be started from the desktop menu. If at all this might be possible if you enable the "Virtual Desktop" in winecfg (but usually people are only interested in the Windows applications, not in seeing the Windows desktop).
There's wine.desktop, but this does neither start Wine itself, nor does it add a launcher to the menu (NoDisplay=true). It only makes native file type associations, so it tells your system that it may start e.g. an .exe *with* Wine. For security reasons wine.desktop is not "activated" in the packages, but only shipped as an example.
Quoting /usr/share/ doc/wine/ README. Debian. gz:
~~~~~ doc/wine- development if you use wine-development): doc/wine/ examples/ wine.desktop /usr/share/ applications/
To enable system-wide support for .exe files execute the following
command (replace /usr/share/doc/wine with
/usr/share/
$ sudo cp /usr/share/
~~~~~
winecfg and uninstaller in desktop menu ------- ------- ------- ------- ---- /bugs.launchpad .net/ubuntu/ +source/ wine/+bug/ 1493044. Please followup there.
-------
I just commented on that in https:/
If I start winecfg here from a terminal it has its icon.
/usr/share/ icons/hicolor/ scalable/ apps/wine. svg is/will be shipped again with src:wine 1.8.6-2 and src:wine- development 2.0~rc6-1
> launchers of the installed Windows programs are not being put in the right (Wine) category
Not sure if I understand this correctly. Maybe it's "just" working on my Debian GNOME system. Here if I install e.g. Steam for a fresh user:
Wine automatically creates the menu structure and creates an entry for Steam there.
Accordingly the following files are created:
~/.local/ share/desktop- directories: Steam.directory directory
wine-Programs-
wine-Programs.
wine-wine.directory
~/.local/ applications/ wine/Programs/ Steam/:
Steam.desktop
> /usr/share/ desktop- directories/ wine-Programs. directory desktop- directories/ wine-wine. directory
> /usr/share/
> Yes, these files do create a menu (sub)section for installed Wine programs.
> This is really useful for MATE, Cinnamon, XFCE and other non-GNOME/non-Unity DEs.
But on these DEs the files in ~/.local are still created by Wine, right? So it still works!?
> and Windows binaries cannot be run directly from the file manager using development version of Wine.
True, due to security reasons your system will not know how to launch e.g. an .exe, see above.