Default WINEPREFIX used when uninstalling a game?

steamclosed Steam clientProton

ValveSoftware/steam-for-linux#7075 · opened 2020-04-26 by dimaryaz · updated 2022-10-29 · 5 comments · github

Ddimaryaz 2020-04-26 github

I was uninstalling "S.T.A.L.K.E.R.: Shadow of Chernobyl", and a dialog box popped up, saying wine was updating /home/dima/.wine/ - which seems very wrong:

Screenshot from 2020-04-25 17-14-39

I also see the following in ~/.wine/system.reg:

[Software\\Wow6432Node\\Valve\\Steam\\Apps\\4500] 1587860102
#time=1d61b5fbacdaa34

The app ID and the timestamp confirm that it's from the uninstall.

Here's some output from ps when this happened:

  12874 ?        S      0:00 /home/dima/.local/share/Steam/legacycompat/iscriptevaluator.exe --get-current-step 4500
  12877 ?        Ss     0:03 /usr/bin/wineserver
  12878 ?        S      0:00 /home/dima/.local/share/Steam/legacycompat/iscriptevaluator.exe legacycompat\evaluatorscript_4500.vdf
  12881 ?        Sl     0:00 C:\windows\system32\wineboot.exe --init
  12909 ?        Ssl    0:00 C:\windows\system32\services.exe
  12913 ?        Sl     0:00 C:\windows\system32\plugplay.exe
  12921 ?        Sl     0:01 C:\windows\system32\winedevice.exe
  12925 ?        Sl     0:00 C:\windows\system32\explorer.exe /desktop
  12932 ?        Sl     0:00 C:\windows\system32\winedevice.exe
  12951 ?        Ssl    0:00 /usr/libexec/tracker-store
  13005 ?        D      0:01 C:\windows\syswow64\rundll32.exe setupapi,InstallHinfSection Wow64Install 128 \\?\Z:\usr\bin\..\share\wine\wine.inf

Nothing actually broke - but this definitely looks like a bug.

Aaeikum 2020-04-27 github

Thanks for reporting, I'll try to reproduce this. Are you using Proton as shipped by the Steam client, or some custom installation?

Ddimaryaz 2020-04-27 github

As shipped by Steam client, version 5.0-6. (Though I think I had just switched from 4.11-13 and had not restarted the client, in case that matters.)

Aaeikum 2020-04-27 github

@dimaryaz I think this is a Steam client bug. You can see in your ps output that it's invoking the system Wine, which shouldn't be possible with Proton. My guess is the Steam client failed to initialize your Proton installation. This can happen if your Proton installation is in an invalid state at Steam client startup or when first launching a game with Proton. This caused it to try to invoke the Windows binary directly. Your system probably has binfmt set up to automatically invoke Wine when a Windows executable is invoked, so it launched iscriptevaluator in your system Wine installation.

I'll point a Steam client dev at this bug to take a look.

Kkisak-valve maintainer 2022-09-24 github

Hello @dimaryaz, are you still experiencing this issue on an up to date system?

Kkisak-valve maintainer 2022-10-29 github

Closing pending feedback.

Nothing extracted yet.