I am having the same issue - am trying to install glorious eggroll's custom proton script.
I still have this bug. The per-game checkbox setting works fine, so suspect perhaps that has a working custom Proton check that could be used for the global equivalent?
Same here, on Manjaro 64bit, the Advances tickbox keeps disabling...
Having native or manjaro steam changes nothing. The custom protons are recognized though, but i cannot use them.
They also aren't available on individual games
I am having this problem as well.
I'm on Manjaro KDE 64 bit.
Same, having issues on both PoP_OS 20 and Manjaro.
It was working for me a day or so ago, strange.
Had the same issue on the steam Clear Linux flatpak.
Same issue on Ubuntu 20.04 with GloriousEggroll Proton-5.9-GE-3-ST as well as Proton-5.11-GE-3-MF
It was working for me a day or so ago, strange.
Same with me. It worked one day and the other day this issue occoured
Had a Steam client update, same bug.
Still not working. Would like to play some games that only work in GE.
Is there going to be a proton next update before this is fixed?
The proton setting does become unchecked for me BUT it still works and selects that proton as the default for all.
Click on (i) button under games banner to check which tool is selected for it.
This is still a thing. On gentoo here non-flatpak.
Still an issue on Arch and its derivatives. Attempted to set proton ge as well as proton tkg globally and both unchecked the ability to use proton for all titles.
This is still a problem. Valve, is this checkbox so hard to fix that it is still an issue after two years?
Still a problem here. I'm on Manjaro using steam-manjaro
A current workaround is by manually editing the config file, as per the STL wiki (change "Proton-stl" to the name of whatever you want to use).
Still a problem here. I'm on Arch
Still a problem on Arch
Experiencing this on openSUSE Tumbleweed. The tip from @MythicSpirit doesn't seem to work because Proton GE is already set correctly for "0" for me. It looks like it's just the UI not rendering it correctly.
"CompatToolMapping"
{
"0"
{
"name" "Proton-7.1-GE-2"
"config" ""
"Priority" "75"
}
"252950"
{
"name" "Proton-6.20-GE-1"
"config" ""
"Priority" "250"
}
"566440"
{
"name" "Proton-6.20-GE-1"
"config" ""
"Priority" "250"
}
…
}
Can confirm this is not working on Fedora 35 either. I am using non-flatpak steam.
Issue occurs on a fresh arch install. Used the archinstall tool that came with the iso.
Still an issue on a fresh install of Arch.
I am having this issue on EndeavourOS. I guess the workaround is to set default Proton and just tell each game individually to use custom Proton versions.
I am having this issue on EndeavourOS. I guess the workaround is to set default Proton and just tell each game individually to use custom Proton versions.
I'm having the same issue on endeavour as well and your workaround works but did you ever find a fix ?
I am having this issue on EndeavourOS. I guess the workaround is to set default Proton and just tell each game individually to use custom Proton versions.
I'm having the same issue on endeavour as well and your workaround works but did you ever find a fix ?
No official fix that I know of at this point
Still an issue, using Arch
still an issue on arch after 3 years almost 4...

Still and issue, currently on Nobara.
Experiencing this issue, except my box is remaining ticked, the setting is not reflected, and I'm on Experimental.
Garuda.

Still a problem, Steam Flatpak, Manjaro.
This might finally have been fixed in the new UI? The box appears to be ticked for me and the "run with" box retains a selection.
Closing as fixed in the 2023-09-11 Steam client update.
proton 6.20-ge-1x1 2022-01proton 7.1-ge-2x1 2022-01proton nextx1 2020-09proton 5.11-ge-3x1 2020-07proton 5.9-ge-3x1 2020-07
Your system information
Please describe your issue in as much detail as possible:
Hello, selecting a custom proton version that has been installed into
~/.steam/root/compatibilitytools.din the Advanced settings of the Steam Play tab unchecks "Enable Steam Play for all other titles".This seems to be a UI bug since the client still considers the option to be enabled. For non-whitelisted games the custom proton is indeed used :
There's no problem when selecting an official proton.
Steps for reproducing this issue: