Steam client version (build number or date): Oct 13, 2021
Distribution (e.g. Ubuntu): Linux Mint
Opted into Steam client beta?: No
Have you checked for system updates?: No
#### Please describe your issue in as much detail as possible:
I've installed the Proton version of Euro Truck Simulator 2 despite it having a native Linux build, because I checked reports in protondb.com and multiple people reported the native version not running very well while Proton did. However, I've since ran into people who run the native version of ETS2 without major issues, and it compelled me to switch to the Native version due to feeling/worrying that, if nobody uses the native ports of games and instead just use Proton, then the developers may never feel compelled to continue developing for the Linux version due to its low usage, and I wanted to do my part.
I chose to uninstall the game before disabling Force Steam Compatibility for it, partly because I was uncertain how it'd work out if I just disabled it normally without reinstalling it, and partly because I also was running the game on an outdated version (1.39) via the game's Beta Options menu and I was also intending to migrate to the current version (1.42), and I felt it'd be best to do both of them in one shot. However, doing that after uninstalling the game seemed to make Steam not realize that Proton was turned off, and thought it was still in Windows mode. As such, Steam downloaded the Windows binaries for ETS2 instead of the Linux ones, which my computer obviously couldn't execute, leading to an error whenever I tried to launch ETS2. I navigated to the problematic directory, and found out that not only was there no /bin/linux_x64, but instead /bin/win_x64. I tried deleting the bin folder and validating game files, but Steam just downloaded the Windows binaries again.
In the end, I had to re-enable forcing the compatibility tool, and then disabling it yet again for Steam to realize Proton was not active, and then it finally downloaded the Linux binaries, allowing me to launch the game properly. It is thankfully an easy bug to fix, but it could very easily provoke a scare as it may not be the most intuitive of actions to take given the circumstances.
What I expected should happen: Disabling Steam Play Proton while the game was uninstalled should make it install the Linux version when reinstalling.
What did happen: Steam did not notice that Proton was disabled, and installed the Windows version of the game instead, which naturally couldn't be executed within the Linux system.
#### Steps for reproducing this issue:
Install a game with Steam Play Proton enabled.
Uninstall it.
Disable Steam Play for that game while it is uninstalled.
Reinstall it.
Steam will download the Windows version of the game, preventing it from being played in Linux.
#### Your system information
#### Please describe your issue in as much detail as possible:
I've installed the Proton version of Euro Truck Simulator 2 despite it having a native Linux build, because I checked reports in protondb.com and multiple people reported the native version not running very well while Proton did. However, I've since ran into people who run the native version of ETS2 without major issues, and it compelled me to switch to the Native version due to feeling/worrying that, if nobody uses the native ports of games and instead just use Proton, then the developers may never feel compelled to continue developing for the Linux version due to its low usage, and I wanted to do my part.
I chose to uninstall the game before disabling Force Steam Compatibility for it, partly because I was uncertain how it'd work out if I just disabled it normally without reinstalling it, and partly because I also was running the game on an outdated version (1.39) via the game's Beta Options menu and I was also intending to migrate to the current version (1.42), and I felt it'd be best to do both of them in one shot. However, doing that after uninstalling the game seemed to make Steam not realize that Proton was turned off, and thought it was still in Windows mode. As such, Steam downloaded the Windows binaries for ETS2 instead of the Linux ones, which my computer obviously couldn't execute, leading to an error whenever I tried to launch ETS2. I navigated to the problematic directory, and found out that not only was there no /bin/linux_x64, but instead /bin/win_x64. I tried deleting the bin folder and validating game files, but Steam just downloaded the Windows binaries again.
In the end, I had to re-enable forcing the compatibility tool, and then disabling it yet again for Steam to realize Proton was not active, and then it finally downloaded the Linux binaries, allowing me to launch the game properly. It is thankfully an easy bug to fix, but it could very easily provoke a scare as it may not be the most intuitive of actions to take given the circumstances.
#### Steps for reproducing this issue: