http://bugs.winehq.org/show_bug.cgi?id=31194
Bug #: 31194 Summary: there should be setting to disable winemenubuilder altogether and forever Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: et.junk@ethome.sk Classification: Unclassified
Although i understand need for desktop integration with various DEs, this little fucker is consistently stealing file associations for me every update. There are no priorities to set or anything. Also i really don't care, i use wine only to run occasionally stubborn windows software.
I use several file managers which respect this mime crap registration and thus wine is making my computer unusable (talk about instant slowdown and 100% CPU usage, wondering what happened) everytime i want to work with any file with more common extension. Crappy wine software is started instead of native application.
There should be big fat checkbox "Disable desktop integration completely" on "Desktop Integration" tab in winecfg dialog application to disable winemenubuilder completely and forever.
This setting should be checked by default upstream, e.g. integration disabled (so direct upstream users like archlinux, don't have to mess with this setting ever to make their association work again after each and possibly frequent update).
Pressing "Apply" button in winecfg when state changes from unchecked to checked should remove all the winebuilder mime crap, zilliards of *.desktop files and other "necessary" desktop integration tidbits.
When winemenubuilder is invoked as a part of whatever process and this setting is enabled it should kill itself immediately, best before doing anything damaging.
Most importantly this setting must be preserved during updates. Also, as ws said above, it should be disabled by default, so users are not subjected to this crap, when they decide to create new wine profile for example eg ~/.wine equivalent, unless distribution changes this by specific tweak.
http://bugs.winehq.org/show_bug.cgi?id=31194
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh@gmail.com
--- Comment #1 from Jerome Leclanche adys.wh@gmail.com 2012-07-11 05:26:02 CDT --- It should be more obvious, but you can go in winecfg -> libraries and override "winemenubuilder" = disabled.
http://bugs.winehq.org/show_bug.cgi?id=31194
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |1.5.8
http://bugs.winehq.org/show_bug.cgi?id=31194
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE
--- Comment #2 from Rosanne DiMesio dimesio@earthlink.net 2012-07-11 08:11:10 CDT --- Duplicate of bug 19182.
Adding export WINEDLLOVERRIDES="winemenubuilder.exe=d" to .bashrc will disable winemenubuilder for all wineprefixes, without needing to bother with winecfg. The only problem is that winetricks does not respect .bashrc settings, but that's a winetricks bug.
*** This bug has been marked as a duplicate of bug 19182 ***
http://bugs.winehq.org/show_bug.cgi?id=31194
--- Comment #3 from Artem S. Tashkinov t.artem@mailcity.com 2012-07-11 09:35:06 CDT --- (In reply to comment #2)
Duplicate of bug 19182.
Adding export WINEDLLOVERRIDES="winemenubuilder.exe=d" to .bashrc will disable winemenubuilder for all wineprefixes, without needing to bother with winecfg. The only problem is that winetricks does not respect .bashrc settings, but that's a winetricks bug.
*** This bug has been marked as a duplicate of bug 19182 ***
Desktop shortcuts will still be created regardless this hack.
http://bugs.winehq.org/show_bug.cgi?id=31194
--- Comment #4 from Rosanne DiMesio dimesio@earthlink.net 2012-07-11 10:37:30 CDT --- (In reply to comment #3)
Desktop shortcuts will still be created regardless this hack.
Those are not created by winemenubuilder. See bug 3548.
http://bugs.winehq.org/show_bug.cgi?id=31194
--- Comment #5 from Austin English austinenglish@gmail.com 2012-07-11 14:59:21 CDT --- (In reply to comment #2)
Duplicate of bug 19182.
Adding export WINEDLLOVERRIDES="winemenubuilder.exe=d" to .bashrc will disable winemenubuilder for all wineprefixes, without needing to bother with winecfg. The only problem is that winetricks does not respect .bashrc settings, but that's a winetricks bug.
*** This bug has been marked as a duplicate of bug 19182 ***
It certainly should. I suppose there could be some weirdness if your main shell isn't bash (it invokes /bin/sh), but testing locally it works when used in an interactive shell (not sure about non-interactive shells though, e.g., from your DE's menu).
http://bugs.winehq.org/show_bug.cgi?id=31194
--- Comment #6 from Rosanne DiMesio dimesio@earthlink.net 2012-07-11 21:17:52 CDT --- (In reply to comment #5)
It certainly should. I suppose there could be some weirdness if your main shell isn't bash (it invokes /bin/sh), but testing locally it works when used in an interactive shell (not sure about non-interactive shells though, e.g., from your DE's menu).
You're right. I hadn't tested winetricks wmp10 with just the .bashrc setting in quite awhile; I just did, and it's fixed.
http://bugs.winehq.org/show_bug.cgi?id=31194
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Jerome Leclanche adys.wh@gmail.com 2012-07-19 07:43:46 CDT --- Closing
http://bugs.winehq.org/show_bug.cgi?id=31194
Sylvain Petreolle spetreolle@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |spetreolle@yahoo.fr