protonscr

Steam Runtime missing some dependencies on Arch

steamclosed
ValveSoftware/steam-for-linux#12609 · opened 2026-01-02 by Xarianne · updated 2026-02-10 · 2 comments · github
1 matching comments, n / p to jump
XXarianne 2026-01-02 github

I thought this was a Proton issue, but I think it is in fact a 32 bit dependency issue, so I am posting it as an issue for Steam itself. Ubisoft Connect does not launch on Arch from Steam unless we force it to run under OpenGL using this launch variable PROTON_USE_WINED3D=1 %command. This is not a good solution as then the games run badly, if at all.

Please see the quote below to see how I arrived to this conclusion. I don't really know which dependencies are missing and I have been struggling to find out.

Mesa version used is 25.3.2 on Arch.

Okay, I think this is due to Arch and the fact that by default it uses Steam's own runtime, rather than Arch's own dependencies (recent change). Steam Runtime might be lacking some dependencies that allow the Ubisoft Launcher to work.

When using the Flatpak version of Steam it all works fine on Arch, Ubisoft connect starts out of the box, no extra launch variables. Fedora starts it as well (with any Proton version). Regata OS starts it successfully.

My version of Fedora has up-to-date mesa via the Terra repos so it is not a mesa regression from Arch having newer mesa.

So the solution on Arch would be to either try the Steam native package that is now on the AUR (but I am not spending a gazillion years compiling every time it updates), or use the Flatpak version alongside the pacman version only for Ubisoft games. I have not tested using the native version of Steam from the AUR to verify this theory, I have honestly lost interest given that I don't want to compile it every time. Given that the games I would run via Flatpak are only from Ubisoft and my system runs them from the Flatpak without any noticeable performance drop, I am just going to roll with that.

If Steam swaps to 64 bit (which it might do soon given that the Windows version is doing so), this might not even be a problem in future.

Faugus Launcher was also unsuccessful on Arch only, I think it IS because it uses the Steam runtime (I can see it being printed in the launch windows) so it doesn't try to pull extra 32 bit deps from Arch. Works fine, once again, on Fedora.

Originally posted by @Xarianne in [#6451](https://github.com/ValveSoftware/Proton/issues/6451#issuecomment-3705153474)

Kkisak-valve maintainer 2026-01-02 github

Hello @Xarianne, if there's a distro packaging issue with Arch, that needs to be reported to and evaluated by Arch's package maintainers.

XXarianne 2026-02-10 github

In case someone else has the same issue, I'm just coming here to say I had picked the wrong dependency source and it was specific to my hardware. When installing Steam, Arch asks for the source of one of its graphic stack dependencies.

I picked the wrong one a while ago and as everything worked, I did not realise I had done so. Once I finally realised this I reinstalled Steam and picked the correct source, and Ubisoft Connect started to work again.

It was user error, although other distros often don't put the user in the situation where they would have to pick the dependency for themselves in the first place, thus exposing the user to a potential point of failure.

But love it or hate it, this is Arch for you.

Launch options

Upstream links