https://bugs.winehq.org/show_bug.cgi?id=37772
Bug ID: 37772 Summary: Updating configuration in fresh 64 bit prefix: mscoree error Product: Wine Version: 1.7.33 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: t0mcat@gmx.de Distribution: ---
Created attachment 50307 --> https://bugs.winehq.org/attachment.cgi?id=50307 Terminal output at first wine / wineboot / winecfg call
Creating a new 64 bit prefix leads to mscoree (.NET) errors. The file mscoree.dll is present in ...\syswow64... directory. To me, it's unclear, whether Mono works or not. Calling wine uninstaller --remove '{E45D8920-A758-4088-B6C6-31DBB276992E}' results in an error message ("Could no match application.").
(1) Package wine-mono is installed on the Linux system. Manual Mono installation using msiexec /i /usr/share/wine/mono/wine-mono-4.5.4.msi gives no serious error messages.
(2) Installation of .NET 2.0 just after prefix initialization (no manual Mono installation) fails ("Product already installed."). Same happens after installing and uninstalling Mono.
https://bugs.winehq.org/show_bug.cgi?id=37772
Michael t0mcat@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Mint
https://bugs.winehq.org/show_bug.cgi?id=37772
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |mscoree
--- Comment #1 from Rosanne DiMesio dimesio@earthlink.net --- AFAICT, wine-mono does not get installed to a 64 bit wineprefix unless you specifically force wine64 when creating the it (wine64 wineboot).
I don't know if that's intended behavior or not (or a regression?), but it is confusing, as the default wineprefix created with just wineboot on a 64 bit system is a 64 bit wineprefix, and there is no message in the console indicating that mono isn't being installed (the err:mscoree:LoadLibraryShim messages are normal on wineprefix creation).
https://bugs.winehq.org/show_bug.cgi?id=37772
Vincent Povirk madewokherd@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #2 from Vincent Povirk madewokherd@gmail.com --- The LoadLibraryShim messages during prefix creation have been around for a while, and they happen in the part of the process before wine-mono is installed. They don't hurt anything, so unless your claim is that there should be no fixme/err messages during prefix creation, this bug is invalid.
Any other issues should be filed as separate bugs.
MSI did change its behavior, so 64-bit installs are no longer visible to 32-bit processes. To install it, see it in wine uninstaller, or remove it, you must use wine64. You can see the same thing with wine gecko (64-bit gecko install doesn't show up when running 32-bit wine uninstaller), but since gecko has different versions for 32-bit and 64-bit it's not as noticeable there.
https://bugs.winehq.org/show_bug.cgi?id=37772
Michael t0mcat@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |---
--- Comment #3 from Michael t0mcat@gmx.de --- Rosanne, tried wine64 wineboot and explicit WINEARCH="win64" - the behavior doesn't change. I had to install mono manually using msiexec.
https://bugs.winehq.org/show_bug.cgi?id=37772
--- Comment #4 from Rosanne DiMesio dimesio@earthlink.net --- Exactly what behavior doesn't change? If you mean you think it wasn't installed, how are you determining that? The console output on wineprefix creation won't be any different. If you ran uninstaller, did you do it with wine64? You need to, as Vincent said, or it won't see the installed wine-mono. The same is true of regedit.
https://bugs.winehq.org/show_bug.cgi?id=37772
Michael t0mcat@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #5 from Michael t0mcat@gmx.de --- Vincent, Rosanne, thanks for pointing out wine64! From http://wiki.winehq.org/Wine64 it wasn't clear to me that command wine in 64 bit prefix doesn't imply 64 bit operation but wine64 should be used.
Running wine uninstaller --remove '{E45D8920-A758-4088-B6C6-31DBB276992E}' after wineboot gave an error message and running Digital Photo Professional 4 (64 bit) failed, too, giving an impression that Mono installation failed.
By the way, is there a way to determine what .Net framework version is covered by a Mono installation?
Rerun with wine64. Everything makes sense. We can close this bug.
https://bugs.winehq.org/show_bug.cgi?id=37772
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Bruno Jesus 00cpxxx@gmail.com --- Closing invalid bugs.
-
wine-bugs＠winehq.org