ProtonUp installing ProtonGE into wrong directory for steam #463
Comments
|
Is Although looking at the code I would expect that it would also detect Can you check if the launchers dropdown contains any other detected Steam installations as well? |
|
I appreciate your reply.
So, yes and yes. Contents of Contents of
While I understand that this is the default behaviour and probably desired behaviour in most cases, it does not change the fact that using this path does not work for me, only placing them in So, trying something out to prove the point.
I am aware that the de facto location of Known changes to the location of
Symlink or not should not matter. My installed versions of ProtonGE are symlinks themselves and they work fine for Steam.
A side effect of this issue is also that setting a compatibility tool for a game installed by ProtonUp-QT via ProtonUp-QT causes the game to crash during startup as the installed compatibility tool does not exist from the Steam client's point of view. Let me repeat that this is an somewhat old, that is pre |
|
ProtonUp-Qt does not to my knowledge only choose one or choose any "default" install location. It should list all known valid Steam installations in the dropdown. I think you have entirely misunderstood me, I was trying to illustrate why ProtonUp-Qt was picking up this installation, I was not trying to say anything about "desired" picking of a Steam installation. You should remove leftover Steam installations if the one you mentioned is indeed a leftover, as good practice so that tools can pick the correct one.
Again, I think you have misunderstood. What I meant by this is that ProtonUp-Qt will attempt to filter out duplicates. For example if it picks up three Steam installations, but one is a symlink, listing three Steam installations in the dropdown would be redundant. ProtonUp-Qt tries to only detect valid, unique Steam installations. That's where symlinks come in. I was not referring to GE-Proton symlinks or symlinks of other compatibility tools, but symlinks that Steam itself creates for its installations (i.e. on Arch-based distros, typically I don't understand the crashing thing you're referring to, could you provide more details? Also, sorry if I misunderstood your reply or missed it, but does ProtonUp-Qt list both Steam installations in the dropdown? It should be able to detect both of both contain the VDF files listed. If does not pick one or the other if I remember correctly, you should be able to see both |
|
Thank you for clarifying.
I do not believe this is a leftover installation as such more that a consequence of how the steam installer has been packaged by Ubuntu years ago before Valve provided their own.
If I install a version of e.g. ProtonGE via ProtonUp-QT and via ProtonUp-QT set the previously installed version of ProtonGE as default for a steam game, then the same steam game fails to launch until the changes are reverted.
No, only I have made an issue at https://github.com/ValveSoftware/steam-for-linux/issues, trying to determine which location is in fact the correct one and having asked for official documentation on the matter. Will post the response here if I get a usable one from Valve but what I gather from it so far is that there is an order of precedence across a list of folders and environment variables that should be considered. |
|
@sonic2kk So, I deleted the Now both ProtonUp-QT now detects If I manually create a symbolic link in However, I do not think this explains why ProtonUp-QT failed to detect the "steam root" which Steam itself detected earlier but at this point I do not care about that part any more. Now, I promised to convey some information from another thread about "officially supported folders" and the order of precedence, so here goes: ValveSoftware/steam-for-linux#6310 and based on that it seems that Regards |
|
I tried to replicate your setup. In my case, ProtonUp-Qt was able to detect it. I'm not quite sure why it didn't work in your case. $ mkdir -p .steam/compatibilitytools.d
$ mkdir -p .steam/config
$ touch .steam/config/config.vdf
$ touch .steam/config/libraryfolders.vdf
$ ln -s ~/.steam .steam/root
$ ll .steam/
drwxrwxr-x 4 david david 4096 Okt 5 10:55 ./
drwxr-x--- 34 david david 4096 Okt 5 10:55 ../
drwxrwxr-x 2 david david 4096 Okt 5 10:55 compatibilitytools.d/
drwxrwxr-x 2 david david 4096 Okt 5 10:55 config/
lrwxrwxrwx 1 david david 7 Okt 5 10:55 root -> /home/david/.steam/
Yes, that is true. ProtonUp-Qt has a list of known install locations. It first resolves all symlinks, then removes duplicates and finally adds them to a list if the path exists. Finally, it will check whether the path Is it possible that it will resolve
So what you did is you downloaded ProtonGE to a folder like That is actually an interesting usecase, related to #117 and #162. We might want to take a look at it. |
|
Thank you for your reply. Sorry about not replying sooner, real life happened as it often does for all of us.
I wouldn't worry too much about it. As already mentioned, the problem is no longer present after wiping my steam install and all relevant config directories.
Yes, pretty much that. Similar to current setup outlined below (this is after the wipe, though)
Regards. |
Please fill out following when reporting a new bug:
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
aettings -> compatabilityExpected behavior
Installed version available via Steam
Desktop (please complete the following information):
PC
Flatpak via Flathub
Additional context
ProtonUp installs the runtimes into
~/.steam/steam/compatibilitytools.d/but on my system all other runtimes need to be installed into~/.steam/root/compatibilitytools.d/where~/.steam/rootis a symbolic link to~/.steam, so effectively~/.steam/compatibilitytools.d/. This is how is has always been without any tampering on my part.Way back Steam was installed via the steam-installer package provided by Ubuntu:
Terminal output
The text was updated successfully, but these errors were encountered: