During a self update from the Epic Game Launcher I get the following error message:
According to the error description, .Net Framework 3.5 should be installed.
The EGL is currently running with the Wine version ‘lutris-6.0-rc1-x86_64’.
How can I install the dotnet35 there?
[OS: Linux Mint Mate 20.0, Wine-System-Version: 4.9-(Staging)]
I have the same problem.
I installed dotnet35 and dotnet35sp1 using winetricks, but it does not change a thing.
maybe we need to include some library to the list in the wine config?
btw, running it on a wine prefix lutris6.0rc1.
any advice?
If i try to update Lutris-Wine-Version with winetricks:
WINEPREFIX="/media/volker/Spiele-L/Lutris - Games/epic-games-store" WINE=~/.local/share/lutris/runners/wine/lutris-6.0-rc1-x86_64/bin/wine ~/.local/share/lutris/runtime/winetricks/winetricks dotnet35
or for the 64-bit-Version:
WINEPREFIX="/media/volker/Spiele-L/Lutris - Games/epic-games-store" WINE=~/.local/share/lutris/runners/wine/lutris-6.0-rc1-x86_64/bin/wine64 ~/.local/share/lutris/runtime/winetricks/winetricks dotnet35
i get this same warning:
Executing mkdir -p /media/volker/Spiele-L/Lutris - Games
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
Using winetricks 20201206-next - sha256sum: 266989baf124f2f3eda6b480a4d42a19407c93da70db1bc27d25b7a2ed118e62 with wine-6.0rc1.r0.gd7b71f0b ( TkG Staging Esync Fsync ) and WINEARCH=win64
Executing w_do_call dotnet35
Executing mkdir -p /media/volker/Spiele-L/Lutris - Games
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
Executing load_dotnet35
warning: This package (dotnet35) is broken in wine-6.0rc1.r0.gd7b71f0b. Broken since 5.12. See https://bugs.winehq.org/show_bug.cgi?id=49690 for more info. Use --force to try anyway.
BTW: The last block is interesting. So, I’m waiting for Lutris-wine-6.0rc2. Perhaps it is the same bug in Lutris-wine-6.0rc1.