New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wine Mono not installed #89
Comments
Thanks for reporting this issue. Did you happen to already confirm that this issue also exists in upstream Proton -- Proton 9 (Beta 16)? If it doesn't work in upstream Proton but in GE, then there must be a patch somewhere in GE's build that fixes your problem and that this not a problem with the launcher but a possible regression upstream. If that's the case, you can configure umu to use GE-Proton by passing |
It works fine with Proton 9 beta 16 (i just downloaded the 9 beta from steam) |
That's strange, because Wine Mono is included in UMU-Proton. To confirm, you still experience this problem in a new Wine prefix? If the previous prefix was created from a different Proton or Wine build, then things are likely to break. For instance, transitioning from UMU-Proton -> GE-Proton, I've observed that I am always displayed a prompt about how Wine could not find Wine Mono, and my protonfixes applied to that prefix would be reset/overwritten |
If you change versions and use the same prefix you -will- as R1ka said hit wine mono install request because different proton versions use different versions of mono. Please double check this on a clean prefix using UMU-Proton |
yes i made it generate a new folder for the prefix |
this is what i did and the output |
okay i think i know what the issue is, the default prefix of UMU-Proton is missing some stuff, which the ge one has.
if i generate it manually with wineboot from umu-proton it will also work fine, but not when umu-proton uses the default prefix to generate it |
The issue is with UMU-Proton, and the version of The wine version built with UMU-Proton uses |
So if I understand it correctly, the wine submodule needs to be updated and then it should work fine? |
When I use umu-run to launch a .NET Framework 4.8 application with UMU-Proton, so just not setting the PROTONPATH env it will not work and wine will log the error
00e4:err:mscoree:CLRRuntimeInfo_GetRuntimeHost Wine Mono is not installed
.If I set the PROTONPATH to my installed GE-Proton9-2 it works fine. No idea if this is an issue on my end, but since GE-Proton seems to work I think it might be an issue with UMU-Proton.
Im using the latest umu-launcher commit at the moment of writing this.
The text was updated successfully, but these errors were encountered: