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 launchers broken in latest update on Solus (0.5.3) #21
Comments
|
Debug log when I try to run any game that uses wine. Debug log when trying to open "Wine configuration"; same thing with "Wine console", "Wine registry", etc. The game debug logs are all empty. |
|
@JagdCake are you also on Solus? |
|
|
Your hastebin links are empty for me. Please provide your info using some other paste service. (I suggest paste.ubuntu.com). |
https://paste.ubuntu.com/p/dBrkDY73D4/ |
I've updated the links in the issue report to use paste.ubuntu.com |
|
|
Can't speak for JagdCake, but Wine is installed on my system, both x64 and 32bit version, from the Solus repository. |
|
Ok, when I tried to install it, I got a traceback: which is the same as lutris/lutris#2327 |
|
Ok I can reproduce the issue with 0.5.2.2 as well so idk wtf is happening. |
I do not have wine installed. |
|
I've found the commit that broke things. When I revert 8a9bec84ed48332120692827005604d963db31a0 everything works fine again. |
|
I am looking into it right now, I will ping with an update. |
|
Thank you for your checking this issue out @aTosser I agree that the Hero Lab issue is unrelated, that was a bad example, there is something else wrong with that particular game. edit: Just fyi, I've reverted that commit downstream for our Solus package, because at least @JagdCake and I run into that issue, probably more users, and I would have to hold back the update otherwise. If there is something else wrong with our setups I'll remove that temporary patch again, as soon as I figure it out. |
|
I also noticed that cabextract is not getting pulled in as a dependency for lutris. I would recheck all of the deps for packaging as this did cause a game install of mine to fail here. |
|
Remove MTGA including game files Victory. cabextract needs to be a mandatory dependency for lutris in solus packaging. There is another bug (#2288) open about cabextract on solus with a request for a gui popup for it being missing. |
|
Installing cabextract changes nothing about this issue. I see the exact same behaviour. |
|
Apologies, after installing the game about 40 times sucessfully, I decided to reset my VM and now I am consistently getting mono pagefaults after a new fresh install. I will continue to look into this. |
|
Note: I just tried it with the new version (0.5.4), with the same result unfortunately |
|
Are there any issues with the Wine build on Solus? If so, can this go on the lutris/wine bugtracker? |
|
@strycore Since this was caused by a commit to the client (8a9bec8, as mentioned above) I thought this was the right place for the bug report. After reverting those changes it works fine with the Lutris Wine build. |
|
oh, it's that. Putting back onto the releases then. I hope the Gentoo people and the Solus people get into a fight at some point. I'll be watching. |




Describe the bug
I've updated the Lutris package for the Solus repository from 0.5.2.2 to the 0.5.3 release. Soon after a user pointed out that no Wine launchers were working anymore. I found the same thing upon further testing. I'm going to use the "Hero Lab" installer script as an example.
Expected behavior
Running the script should start the installation of Hero Lab and create working entry in Lutris from which I can launch the game.
Current behavior
Setup rushes through the steps way to quickly after the inital Wine prefix setup, complains about a missing executable at the end and the entry in Lutris is non-functional
Steps to reproduce
Lutris debugging output
https://paste.ubuntu.com/p/nmsptGYB3R/
journalctl output: https://paste.ubuntu.com/p/4h7bhCWW6Y/
System information
https://paste.ubuntu.com/p/sQqJMH2HVH/
Screenshots
This happens for every Wine app. Selecting "Wine console", "Wine config", etc. does nothing either.
The text was updated successfully, but these errors were encountered: