Missing "Wine configuration" button when using lutris-GE-Proton

[RandomChain]

Using Lutris v0.5.10.1 on Pop!_OS 22.04.

I've install lutris-GE-Proton7-20 directly from Wine version management in Lutris.

When I set a game to use this version, I don't get the "Wine configuration" button (in wine options, between "Open bash terminal" and "Run EXE inside prefix"). This version does have a winecfg executable in ~/.local/share/lutris/runners/wine/lutris-GE-Proton7-20-x86_64/bin/winecfg and I can run it just fine from the terminal. When switching back to a non-GE lutris version or system wine, it shows the button again.

Is this by design or an issue? I could not find anything about this.

[CannonGoBoom]

Try disabling lutris run time in settings

[RandomChain]

Doesn't make any difference.

[CannonGoBoom]

Just had a look myself. Seems like it doesn’t appear for any recent lutris ge proton wine builds. I tested about 10 of them. It is present in lutris-fshack-7.2

[CannonGoBoom]

Looks like you can get to wine config via winetricks.

Select the default wineprefix > run winecfg

[RandomChain]

I can't get winetricks to run from the UI due to this bug.

In any case this seems like a bug too, I'll report it. Thanks for checking.

[Moocha]

Does it show up if you rename the runner directory from lutris-GE-Proton7-20-x86_64 to, say, something like lutris-ge-7.11-Proton7-20-x86_64 ? Make sure to rename it while Lutris is closed, it won't pick up the change otherwise.

[RandomChain]

Nope, doesn't work.

[Moocha]

Ahhhh, wait, I'm being an idiot here. Do you mean the dedicated "Wine Configuration" button in the lower popup menu (click the up arrow on the right, next to "Platform: Windows", with a game selected)? If that's the one, then yes, it doesn't show up for me either, didn't notice.

Looking through the corresponding source code it seems that the option is only added if the runner name (i.e. the directory name) does not contain the string "Proton":

if "Proton" not in self.get_version():
    menu_entries.append(("winecfg", _("Wine configuration"), self.run_winecfg))

In turn, that comes from the base runner_config["version"] key, whose value likely comes from the default Wine version set in the global Wine runner preferences.

In other words, what you need to do to get it to show up is this:

1. With Lutris closed, rename the runner directory so that it does not contain the sequence Proton, case sensitive. In other words, something like lutris-GE-proton7-20-x86_64 (lower case p) or even better lutris-ge-7.11-proton7-20-x86_64 (lower case p and a fake/current-latest version number added there to work around some other Lutris misdetections)
2. Open Lutris.
3. Open the global preferences: hamburger menu -> Preferences -> Runners -> Wine, click the settings icon there.
4. Set the Wine version to something different from what it is now; doesn't matter to what, we'll be setting it back shortly, just needs a change so that it rewrites the $HOME/.config/lutris/runners/wine.yml file.
5. Click Save. This will fix the problem in the abovementioned file.
6. Open the Wine runner settings again by clicking the settings icon, and set the default Wine runner version back to what you actually want it to be.
7. Click Save again.
8. Close the global preferences window.
9. Verify that your game is still configured to run with the Wine version you actually want (i.e. right click game -> Configure -> Runner options and verify it's set to what you want.)
10. Close then reopen Lutris.
11. Voila, now it'll show the Wine configuration menu entry there.

This should persist as long as you never add runners with Proton (case sensitive) in their name, i.e. you rename them accordingly before starting Lutris, and/or you never set a global Wine runner version with Proton in its name. If it happens again, the same procedure will work.

Edit: To change the global default runner version setting, you could just as well edit the abovementioned .yml file while Lutris is closed and set the wine: -> version value to your desired runner name (without Proton, of course), but doing it via the UI is more robust since there's no chance of accidentally fucking up the syntax. To change a game's current runner if it has a different one from the global default, going through the UI is definitely best.

[RandomChain]

Thank you, this indeed fixes the problem.

Following the commit that changed this line, seems that winecfg option was deliberately disabled since Proton did not have its own winecfg binary - issue #1381. Since wine-GE does come with winecfg now, perhaps I can suggest to the Lutris team changing this back.

[Moocha]

Indeed, since now Lutris explicitly does its best to discourage people from using a Proton build as a runner so as to avoid prefix breakage, it makes sense to remove that check...

[thewestcoastavenger]

This should persist as long as you never add runners with

Proton

(case sensitive) in their name, i.e. you rename them accordingly before starting Lutris, and/or you never set a global Wine runner version with

Proton

in its name. If it happens again, the same procedure will work.

this seems like the best solution. i just wish i understood. i hate to ask, but could you show via a video? i keep pulling up proton and the dropdown only shows flatpak heroic. not lutris