[Bug 57202] New: steam client stops working on wine 8.19+ on Slackware 15.0 due to mono 8.10 update
https://bugs.winehq.org/show_bug.cgi?id=57202
Bug ID: 57202 Summary: steam client stops working on wine 8.19+ on Slackware 15.0 due to mono 8.10 update Product: Wine Version: 8.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: steampunque8@gmail.com Distribution: ---
Created attachment 77100 --> https://bugs.winehq.org/attachment.cgi?id=77100 last step of bisect for steam client launch failure
I recently tried to run steam client on upstream wines and found that the client will not start on any wine version 8.19 or above. I bisected the problem to the update to mono 8.1.0. The last stage of bisect is attached. When starting the client a ton of processes get created and then "Maximum number of clients reached" messages get spammed infinitely on the console.
OS: Linux 5.15.140 Dist: Slackware 15.0 64 CPU: 9900k GPU: RTX 4070
I found a workaround to the problem to shut off mono as follows:
export WINEDLLOVERRIDES="mscoree="
This workaround seems OK since I don't think steam client itself relies on mono but I am not sure some of the apps it launches wont.
Any tips or ideas what might be happening here would be appreciated. No issues with the older wine versions up to 8.18 ran steam with mono enabled fine so I am pretty sure some update in mono 8.10 is triggering the problem. There is a good chance this is related to Slackware 15.0 distribution and has nothing to do with wine or mono issue but I don't know where to start looking for the breakage.export WINEDLLOVERRIDES="mscoree="
https://bugs.winehq.org/show_bug.cgi?id=57202
Esme Povirk madewokherd@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |mscoree CC| |madewokherd@gmail.com
--- Comment #1 from Esme Povirk madewokherd@gmail.com --- Is this still a problem with Wine 9.17?
Can you get a log with WINEDEBUG=mscoree WINE_MONO_TRACE=x ?
https://bugs.winehq.org/show_bug.cgi?id=57202
Esme Povirk madewokherd@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Regression SHA1| |9c1ffb545f350743e71cdfcc0da | |e5e98324d10ee
https://bugs.winehq.org/show_bug.cgi?id=57202
--- Comment #2 from tjb steampunque8@gmail.com --- (In reply to Esme Povirk from comment #1)
Is this still a problem with Wine 9.17?
Can you get a log with WINEDEBUG=mscoree WINE_MONO_TRACE=x ?
Well this problem just got strange. I reverted to 9.0rc3, 9.5, and 9.13 and got solid fails on all those. Then I started 9.17 and got a fail on it too. Then I set
export WINEDEBUG=mscoree export WINE_MONO_TRACE=x
and launched, and it worked. Then I commented those out, restarted, and it still works. Then I went back to 9.13, started and got fail. Then I did the exports again and 9.13 started and worked.
Same thing happens with 9.5. I install it, start steam, it fails, then I do those two exports and it starts working.
I am not sure what to make of this. Its possibly a signature of an uninitialized variable somewhere. But I'm locked out from getting the traces if it always starts when the traces are turned on.
https://bugs.winehq.org/show_bug.cgi?id=57202
--- Comment #3 from tjb steampunque8@gmail.com --- Created attachment 77119 --> https://bugs.winehq.org/attachment.cgi?id=77119 trace of steam start fail wine 9.17
https://bugs.winehq.org/show_bug.cgi?id=57202
--- Comment #4 from tjb steampunque8@gmail.com --- (In reply to Esme Povirk from comment #1)
Is this still a problem with Wine 9.17?
Can you get a log with WINEDEBUG=mscoree WINE_MONO_TRACE=x ?
Got the trace. To get it I had to have the two variables turned on right after doing the wine install.
The fail pattern seems to be failure after first install, but then when launching again it doesn't seem to fail, it is not related to turning on the trace variables but just the fact that a second start after wine upgrade is being done.
https://bugs.winehq.org/show_bug.cgi?id=57202
--- Comment #5 from tjb steampunque8@gmail.com --- (In reply to Esme Povirk from comment #1)
Is this still a problem with Wine 9.17?
Can you get a log with WINEDEBUG=mscoree WINE_MONO_TRACE=x ?
Further testing shows this problem can be replicated reliably with all wines from 8.19 through 9.17 as follows:
1) Install the wine version
2) Start the steam client as the first program to be run after the install. The updating wine diaglogue box will appear.
3) An infinite number of maximum number of clients reached messages will spam to the console and steam will not load.
4) Manually kill all processes in the steam client.
5) start steam again. No updating diaglogue box will appear, no spam messages will appear and the steam client should start.
I'm pretty sure my bisect is valid, i.e. mono 8.10 and above was the trigger for this type of behavior. It does appear the problem can be worked around through a simple manual kill and restart of the client, though I am not sure if it will stay working or randomly start happening again as in the past I am pretty sure I was able to get constant failure even after manually killing wine and restarting (though not 100% certain on that point).
https://bugs.winehq.org/show_bug.cgi?id=57202
--- Comment #6 from Esme Povirk madewokherd@gmail.com --- The only thing Wine Mono related in that log is the upgrade. That's worth checking.
Can you try this: Run "wine uninstaller" and uninstall Wine Mono in the GUI, then run "wine regsvr32 mscoree" to reinstall it. I want to see if that fails in a similar way.
If that's not it, WINEDEBUG=+process might also give some info.
https://bugs.winehq.org/show_bug.cgi?id=57202
--- Comment #7 from tjb steampunque8@gmail.com --- (In reply to Esme Povirk from comment #6)
The only thing Wine Mono related in that log is the upgrade. That's worth checking.
Can you try this: Run "wine uninstaller" and uninstall Wine Mono in the GUI, then run "wine regsvr32 mscoree" to reinstall it. I want to see if that fails in a similar way.
If that's not it, WINEDEBUG=+process might also give some info.
The problem only happens when steam is started however. Other programs start just fine.(In reply to Esme Povirk from comment #6)
The only thing Wine Mono related in that log is the upgrade. That's worth checking.
Can you try this: Run "wine uninstaller" and uninstall Wine Mono in the GUI, then run "wine regsvr32 mscoree" to reinstall it. I want to see if that fails in a similar way.
If that's not it, WINEDEBUG=+process might also give some info.
Yes, it failed the same way when I tried to uninstall mono. It goes into an infinite loop printing max number of clients reached. The uninstaller said mono version was 8.0.0, but a 9 version was loaded in the trace I captured.
This problem only showed when I was starting steam from a fresh upgrade though. I could start other programs from a fresh install without the hangup/infinite loop.
https://bugs.winehq.org/show_bug.cgi?id=57202
--- Comment #8 from tjb steampunque8@gmail.com --- (In reply to tjb from comment #7)
(In reply to Esme Povirk from comment #6)
The only thing Wine Mono related in that log is the upgrade. That's worth checking.
Can you try this: Run "wine uninstaller" and uninstall Wine Mono in the GUI, then run "wine regsvr32 mscoree" to reinstall it. I want to see if that fails in a similar way.
If that's not it, WINEDEBUG=+process might also give some info.
The problem only happens when steam is started however. Other programs start just fine.(In reply to Esme Povirk from comment #6)
The only thing Wine Mono related in that log is the upgrade. That's worth checking.
Can you try this: Run "wine uninstaller" and uninstall Wine Mono in the GUI, then run "wine regsvr32 mscoree" to reinstall it. I want to see if that fails in a similar way.
If that's not it, WINEDEBUG=+process might also give some info.
Yes, it failed the same way when I tried to uninstall mono. It goes into an infinite loop printing max number of clients reached. The uninstaller said mono version was 8.0.0, but a 9 version was loaded in the trace I captured.
This problem only showed when I was starting steam from a fresh upgrade though. I could start other programs from a fresh install without the hangup/infinite loop.
Just verified that again. trying to start steam after an upgrade goes into the fail mode. I started other programs (one 32, one 64) and they start fine first launch after a wine upgrade.
https://bugs.winehq.org/show_bug.cgi?id=57202
--- Comment #9 from Esme Povirk madewokherd@gmail.com --- Do you have Steam in its own prefix?
https://bugs.winehq.org/show_bug.cgi?id=57202
--- Comment #10 from tjb steampunque8@gmail.com --- (In reply to Esme Povirk from comment #9)
Do you have Steam in its own prefix?
Yes, I added the prefix before wine uninstall.
https://bugs.winehq.org/show_bug.cgi?id=57202
--- Comment #11 from Esme Povirk madewokherd@gmail.com --- Might be something weird going on with that prefix then and not related to Steam itself.
https://bugs.winehq.org/show_bug.cgi?id=57202
--- Comment #12 from tjb steampunque8@gmail.com --- (In reply to Esme Povirk from comment #11)
Might be something weird going on with that prefix then and not related to Steam itself.
Prefix is fine before mono 8.10+ was added. I'll check with a new prefix and see if mono 8.10 broke the old prefix. There was a similar breaking change to an EA client prefix due to a DLL update. Old prefixes (created with wines with mono <8.10) start fine on the other programs though.
-
WineHQ Bugzilla