Talk:Steam/Client troubleshooting

path?
In

I do believe that current path is steamapps not SteamApps

--Kreyren (talk) 04:05, 21 September 2018 (UTC)

No Friends List/No Store Loading
In order to resolve this, run steam with "GSETTINGS_BACKEND=memory steam" or edit the desktop file with the "env GSETTINGS_BACKEND=memory steam %U" in the Exec= section.

--ShrtSwrd (talk) 11:07, 30 May 2019 (EST)

Vulkan support in Mesa for Windows games?
After installing games-util/steam-launcher and games-util/steam-client-meta from anyc's steam-overlay, Windows games (or rather the wine install bundled with the Proton Steam client) would still not launch until I compiled in Vulkan support to Mesa as per this wiki page. If there is no objection I'll add a troubleshooting item here for those tyring to get Windows games running, since it is arguable that people looking for assistance might consider it a client or game issue.--Diem (talk) 23:02, 28 March 2020 (UTC)


 * Following Maffblaster's comment on the Steam talk page, I have added this troubleshooting item--Diem (talk) 17:19, 12 April 2020 (UTC)

bwrap (bubblewrap) issues
When using Proton > 5.0, if you get

bwrap: No permissions to creating new namespace, likely because the kernel does not allow non-privileged user namespaces. On e.g. debian this can be enabled with 'sysctl kernel.unprivileged_userns_clone=1'.

emerge bubblewrap to make this error go away

Now I'm getting the following, but it could be because I've installed Steam in a chroot.

pressure-vessel-wrap[29587]: E: Cannot run bwrap: wait status 256 pressure-vessel-wrap[29587]: E: Diagnostic output: bwrap: Failed to make / slave: Invalid argument

--Pistos (talk) 06:13, 3 June 2021 (UTC)

The issue is fixed by mounting the chroot folder to itself first followed by the rest (dev, sys, proc, ...), e.g.:

$CHRD="/my/chroot/" mount -o bind $CHRD $CHRD mount --rbind /dev $CHRD/dev [...] --Intrus (talk) 00:17, 27 July 2021 (UTC)

For unknown reasons, I don't get that "bwrap: Failed to make" error any more, whether or not I do the self bind mount like you suggested. However, I still can't run Proton > 5.0. It just exits the game right away, without any helpful error output in the console.

Pistos (talk) 22:01, 16 September 2021 (UTC)

Solved: In addition to bind mounting the chroot dir to itself, I needed to bind the X11 socket into the chroot, too:

mount --bind /tmp/.X11-unix "${chroot_dir}/tmp/.X11-unix"

See https://github.com/ValveSoftware/steam-runtime/issues/465 for more details.

Pistos (talk) 23:13, 18 September 2021 (UTC)