-
Notifications
You must be signed in to change notification settings - Fork 80
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
vcrun2019 sha256sum mismatch #61
Comments
A SHA256 checksum is a method for verifying the integrity of files. If the checksum fails it is because the downloaded file was corrupted somehow. This doesn't seem to be a issue with this project:
My guess is there may be something wrong with your system libraries responsible for handling compression. That can cause both problems described - if the Winetricks download uses any form of compression it could could corrupt files. You won't be able to get much help here. I recommend you go to the Lutris project and report the extraction bug there, maybe they'll be able to find the cause. You should also go to Manjaro forums to see if other people have had the same problem as you. |
Thanks for your help, I've managed to fix it. I think the problem was caused because winetricks hasn't been updated with the hashes for the latest version of the vcrun2019 x86 and x64 installers. To get around this issue I downloaded the older versions of the installers that winetricks was expecting from the internet archive, and put them in the winetricks cache (/home/user/.cache/winetricks/vcrun2019 IIRC). I then ran your installer again and it worked, after a few tries. This didn't fix the freezing issue during the extraction. Should I close the issue? |
@chappjo I'm running into the same problem. Could you provide the link to the Internet Archive versions you downloaded? |
Thank you @chappjo. I followed the same steps as you and successfully got Mod Organizer 2 installed. |
Since the affected user found a solution, I'll close this issue. If someone corrects me and confirms the bug is on the installer's side I'll reopen it. |
Reopening the issue because many users are reporting this. While there's nothing I can do on my end (at least that I know of), it serves as reference for people who come across the problem. |
The way i worked around this was to use a git compiled version of winetricks and change the reference in modorganizer2.yaml (should be around line 318) from the lutris version to the git version (in my case /usr/bin/winetricks) |
That's what I ended up doing. It may be reasonable to try to fallback to the system version of Winetricks if the Lutris one fails. |
The reason the Lutris version is used by default is that it will be the most up to date one in most systems. The SHA updated was merged into the master branch of Winetricks in May 20th but the latest release is from April 12th. Falling back to system wouldn't do much in situations like this one. |
|
This did not change the issue on my end: sudo winetricks --self-update |
@rockerbacon perhaps have two installers? One pointing to Edit: Delete winetricks located in |
Update on this: I've opened issue #2981 on Lutris to see if they're willing to update their provided version of Winetricks. I'd open a pull request but they removed it from the main project in version 5.5 and I can't seem to find it anywhere else. If things remain as-is for much longer I'll default to system Winetricks and instruct users to update at the game selection menu. |
I think this would be the more preferred method. Even in lutris I have it set to use system libs by default but yet even lutris (obviously) fails at this. |
A recent Lutris release should have fixed the problem. See the Lutris issue for details. |
can confirm that it is still happening. Trying @chappjo 's fix did not work. Neither did --self-update EDIT: using $HOME/.local/share/lutris/runtime/winetricks/winetricks --self-update appears to let me install. Having another issue which I will investigate on its own |
It does appear that the "$HOME/.local/share/lutris/runtime/winetricks/winetricks --self-update" command now works again, I was able to re-install MO2 without issue this time. Thanks to whoever on the winetricks team updated the checksum! |
Sorry but there's gotta be a better way for you folks. Not even running
Linux right now on my main PC, but good lord...
…On Friday, October 9, 2020, KorgiSilvercloud ***@***.***> wrote:
It does appear that the "$HOME/.local/share/lutris/runtime/winetricks/winetricks
--self-update" command now works again, I was able to re-install MO2
without issue this time. Thanks to whoever on the winetricks team updated
the checksum!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKJ7EMRDRJXKRGTUVNKKALLSJ26LTANCNFSM4NHUWHIQ>
.
--
Merc
mercster@gmail.com
Yeah.
|
Can confirm that it's still a problem. Running winetricks --self-update doesn't work, but "$HOME/.local/share/lutris/runtime/winetricks/winetricks --self-update" does work. I guess this means that Lutris is using their own version of winetricks instead of the system's version. I'm betting they do this for dependency reasons. Which means every time winetricks updates, this problem will crop up again. This should probably be put somewhere a bit more prominent so newbies can figure out the workaround easier, since it will be a recurring problem as long as Lutris decides to use their own version of winetricks instead of using the system's. Maybe a note on the page that says 'if you have an error about a checksum mismatch, check this thread for workaround'? |
Thanks for the fix, installation succeeded after running this command. |
After running
|
@pblack476 while it is slightly related to this issue tracker the actual issue is over at lutris. Incorrect issue tracker |
Check #158 |
I've asked lutris admins to update winetricks version in runtime. |
For those still having problems with the vcrun2019 and dotnet40 install for Mod Organizer 2, enter this: sudo winetricks --self-update Then enter (I install my WINE bottles in /opt, you may have yours elsewhere so adjust accordingly): $ WINEPREFIX=/opt/WineBottles/ModOrg2 winetricks vcrun2019 dotnet40 The above solved my problem completely. Smooth install on Fedora. |
This is happening again in October 23 2021, I contributed a fix in Winetricks/winetricks#1837 which you can copy locally to make this work. |
i found the actual simple solution!! run these commands on your terminal.
you're good to go! |
gg to necro an old issue @Rahat-M By default lutris doesn't use system installed winetricks as it uses its own. It wasn't until after that it no longer bundled in winetricks. So that "solution" doesn't work. Especially now since this repo no longer uses lutris @rockerbacon please close this issue - as it no longer applies to the current state. |
I'm new to GitHub, so sorry if I make any basic mistakes.
Description:
After running the command:
"lutris -i "$HOME/Downloads/modorganizer2.yml"
Lutris starts up, and I go through the installation procedure, I set the install directory to /home/user/games/mod-organizer-2, then I selected Skyrim, and then steam with proton. After this the program goes through extracting/downloading some files. A little while later it fails and I get an error message:
"Error while installing winetricks, please run Lutris from a terminal and check the logs"
In the terminal, the last line reads:
"sha256sum mismatch! Rename /home/user/.cache/winetricks/vcrun2019/vc_redist.x86.exe and try again."
I tried renaming it, and trying again. As well as downloading my own vc_redist.x86.exe from here, and putting it in the "/home/user/.cache/winetricks/vcrun2019/" folder (I did rename it to match the same case).
Notes
I have run Skyrim from steam before, and I have set it's proton version to 5.0-7.
This happened before and after I installed winetricks.
I don't have SKSE installed.
My package manager says everything is up to date.
I have another issue with the program freezing partway though extracting the files. To get around this I have to try installing it 2-4 times before it completes successfully.
System:
Manjaro
More of the log:
The text was updated successfully, but these errors were encountered: