https://bugs.winehq.org/show_bug.cgi?id=49579
Bug ID: 49579 Summary: Running .exe from programs with GUI uses wrong prefix in Wine 5.0 Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: charivari@online.de Distribution: ---
When running an *.exe by doubleclicking on it in the fileexplorer (Thunar), Wine 5.0 will not run it in the standard prefix ~/.wine as it should, but instead in another existing prefix in ~/.local/share/wineprefixes/wine32. Winetricks shows the same behaviour, opening wine32 when told to open the standardprefix - though for some reason, it also shows wine32 among the secondary prefixes, while not showing wine at all. Running from console will produce the expected outcome of running in ~/.wine.
This did not happen in Wine 4.0, and started happening immediately after the update to Wine 5.0, without any configuration changes. I've already checked .bash-rc and .profile and made sure there's no value set for $WINEPREFIX.
While not exactly a major bug, it's a bother to work around for every single program.
OS: Linux Mint 20 Xfce Wine: 5.0-3
https://bugs.winehq.org/show_bug.cgi?id=49579
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #1 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
That looks like a file association issue. It may be caused by leftovers from third-party Wine wrappers.
- Check if there is a settings in Thunar that sets EXE file association ('Open with' configuration). - Check /usr/share/applications/mimeapps.list for possible EXE file associations (mimetype application/vnd.microsoft.portable-executable). - Check if there is a EXE file association in ~/.local/share/applications (mimetypes in desktop files).
As this is a user/system setting issue, this is probably invalid as a bug. Wine itself doesn't create or mangle EXE file associations.
Be sure to ask on the forums, if the issue persists.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=49579
charivari@online.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED
--- Comment #2 from charivari@online.de --- Thanks, solved the issue. Turns out I had a file called wine-extension-msp.desktop sitting in ~/.local/share/applications that pointed to the wineprefix. Change date from long before the upgrade to Wine 5.0. No clue where that came from (never had Winewrappers or anything like that installed, and left the file associations Wine created as-is until now) or why it did not cause issues under Wine 4.0 though.
https://bugs.winehq.org/show_bug.cgi?id=49579
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=49579
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED
--- Comment #4 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=49579
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Gijs Vermeulen gijsvrm@gmail.com --- Closing INVALID.
-
WineHQ Bugzilla