http://bugs.winehq.org/show_bug.cgi?id=17315
Summary: Wine lacks an option to disable start menu/desktop icon creation Product: Wine Version: 1.1.14 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: from_wine_bugzilla@ssokolow.com
On my system, I have to set up `rm -rf ~/.local/share/applications/wine &>/dev/null` as a cronjob because I frequently add applications to non-default Wine prefixes for testing purposes and then simply delete the prefixes when I'm finished testing.
This works, but prevents me from retaining any icons from my default Wine prefix.
Deleting the Z: link to prevent otherwise trustworthy apps from innocently cluttering up the system at large keeps desktop icons in check, but it still seems like a bit of an ugly hack.
http://bugs.winehq.org/show_bug.cgi?id=17315
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #1 from Rosanne DiMesio dimesio@earthlink.net 2009-02-08 10:43:27 --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=17315
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dimesio@earthlink.net
--- Comment #2 from Rosanne DiMesio dimesio@earthlink.net 2009-02-08 10:54:02 --- I'd like this too, for pretty much the same reasons. I delete the icons manually, so I keep the ones I want, but it's still a pain to have to do that for apps I was just testing.
http://bugs.winehq.org/show_bug.cgi?id=17315
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com
--- Comment #3 from Austin English austinenglish@gmail.com 2009-02-08 11:05:28 --- Technically windows doesn't do this, so wine shouldn't have to either...
http://bugs.winehq.org/show_bug.cgi?id=17315
--- Comment #4 from Stephan Sokolow from_wine_bugzilla@ssokolow.com 2009-02-08 11:26:55 --- Technically, Windows doesn't support the kind of pseudo-virtualization that exposes this problem in the first place.
http://bugs.winehq.org/show_bug.cgi?id=17315
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|trivial |enhancement
--- Comment #5 from Austin English austinenglish@gmail.com 2009-02-08 11:34:56 --- (In reply to comment #4)
Technically, Windows doesn't support the kind of pseudo-virtualization that exposes this problem in the first place.
That's irrelevant. My point was that Windows doesn't give you a way to prevent icons from being made either.
http://bugs.winehq.org/show_bug.cgi?id=17315
--- Comment #6 from Stephan Sokolow from_wine_bugzilla@ssokolow.com 2009-02-08 11:47:52 --- Yes, but there's less need for it in Windows. It's all one desktop. To me, this is like a Windows application being able to add icons to the "All Users" desktop or Start Menu without needing administrator privileges.
http://bugs.winehq.org/show_bug.cgi?id=17315
--- Comment #7 from Rosanne DiMesio dimesio@earthlink.net 2009-02-08 13:05:12 --- (In reply to comment #3)
Technically windows doesn't do this, so wine shouldn't have to either...
You're right, of course; it's an enhancement, not a bug. It just happens to be one I've often wished for.
http://bugs.winehq.org/show_bug.cgi?id=17315
--- Comment #8 from Alexandre Julliard julliard@winehq.org 2009-02-08 16:22:19 --- You can disable winemenubuilder.exe using the libraries tab in winecfg.
http://bugs.winehq.org/show_bug.cgi?id=17315
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE
--- Comment #9 from Dmitry Timoshkov dmitry@codeweavers.com 2009-02-09 03:35:04 --- Once the bug 10277 is fixed this shouldn't be a problem anymore.
*** This bug has been marked as a duplicate of bug 10277 ***
http://bugs.winehq.org/show_bug.cgi?id=17315
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Dmitry Timoshkov dmitry@codeweavers.com 2009-02-09 03:35:21 --- Closing duplicate.
http://bugs.winehq.org/show_bug.cgi?id=17315
Stephan Sokolow from_wine_bugzilla@ssokolow.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|DUPLICATE |
--- Comment #11 from Stephan Sokolow from_wine_bugzilla@ssokolow.com 2009-02-09 12:22:09 --- This is not a duplicate of 10277 because I don't run the uninstallers. (It would take far too long and there's no guarantee of unattended operation) I simply delete the non-default wineprefixes and I'm looking for an option that will work with removing Z: to allow me to prevent standard Windows installers from stepping outside the wineprefix.
http://bugs.winehq.org/show_bug.cgi?id=17315
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |DUPLICATE
--- Comment #12 from Dmitry Timoshkov dmitry@codeweavers.com 2009-02-09 22:17:10 --- (In reply to comment #11)
This is not a duplicate of 10277 because I don't run the uninstallers. (It would take far too long and there's no guarantee of unattended operation) I simply delete the non-default wineprefixes and I'm looking for an option that will work with removing Z: to allow me to prevent standard Windows installers from stepping outside the wineprefix.
You should run the ununstallers then, there is no reason to cripple Wine to workaround your habits. Otherwise this bug is invalid.
*** This bug has been marked as a duplicate of bug 10277 ***
http://bugs.winehq.org/show_bug.cgi?id=17315
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #13 from Dmitry Timoshkov dmitry@codeweavers.com 2009-02-09 22:17:28 --- Closing duplicate.
http://bugs.winehq.org/show_bug.cgi?id=17315
--- Comment #14 from Stephan Sokolow from_wine_bugzilla@ssokolow.com 2009-02-10 01:21:16 --- Ugh. I'll just stick with deleting all Wine menu entries on a cronjob until I can get the hang of using the libraries tab as Alexandre suggested. Then I'll add a `regedit disable_menus.reg` line to my wrapper. (Least hassle)
Running uninstallers is not a suitable option because it takes too long, there's no guarantee that the uninstallers have an unattended mode, there's no guarantee that the invocation method for the uninstallers' unattended mode will be consistent, and even then, I still find it irritating that Windows applications can clutter up my otherwise beautifully organized search-based launcher with their 5+ icons per application.
http://bugs.winehq.org/show_bug.cgi?id=17315
--- Comment #15 from Austin English austinenglish@gmail.com 2009-02-10 01:22:37 --- (In reply to comment #14)
Ugh. I'll just stick with deleting all Wine menu entries on a cronjob until I can get the hang of using the libraries tab as Alexandre suggested. Then I'll add a `regedit disable_menus.reg` line to my wrapper. (Least hassle)
WINEDLLOVERRIDES="winemenubuilder.exe=d" wine foo.exe
Or add that to your .bashrc
http://bugs.winehq.org/show_bug.cgi?id=17315
--- Comment #16 from Stephan Sokolow from_wine_bugzilla@ssokolow.com 2009-02-10 01:30:42 --- Thanks. I've generally tried to avoid the need for Wine, so I haven't had much chance to get familiar with the options available outside winecfg.
-
wine-bugs＠winehq.org