Proton 5.13 beta: known issues

[Plagman]

• ~Selecting Proton 5.13 for a game and launching it will only download "Proton 5.13" and not "Steam Linux Runtime - Soldier", resulting in no games launching properly. This can be avoided by either installing both by hand or restarting Steam after the initial launch.~
• Controller hot-plugging doesn't work
• System-wide Vulkan layers like MangoHUD or vkBasalt don't work
• Using a custom per-game driver (like with VK_ICD_FILENAMES or LIBGL_DRIVERS_PATH) doesn't work
• User hooks like LD_PRELOAD (like for MangoHUD OpenGL) don't work
• ~Doesn't work on a GNOME Wayland desktop (needs https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508)~
• ~Steam "Force Quit" feature doesn't work~

[serebit]

Also #4266, there's an issue with connecting to X on some computers.

[clarfonthey]

As mentioned in #4278, the release requires enabling the kernel.unprivileged_userns_clone kernel flag:

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'.

This is not acceptable -- this flag is for a feature that has not been fully vetted for security and has been disabled in several security-conscious distros. The best info I could find is in this article: https://lwn.net/Articles/673597/

Personally, I think that requiring user namespaces gains absolutely no value for Proton or the steam runtime and should not be required.

[Oschowa]

This mutter MR makes games work in a gnome wayland session when using the new runtime: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508

[raneon]

* Doesn't work on a Wayland desktop

The games I've tried on Plasma Wayland worked fine. The issue referred probably to Gnome, see Oschowa's comment.

[NTMan]

This mutter MR makes games work in a gnome wayland session when using the new runtime: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508

Thanks, with this MR the issue Doesn't work on a Wayland desktop was gone.

[sfjuocekr]

I would like to add here that the cursor behavior has changed as well, I noticed this in Among Us as my mouse cursor was super super tiny on my 4K screen.

Going back to 5.0.9 uses the cursor from my window manager as expected.

[sysms]

I also want to chime in here to say that Proton 5.13 won't run on Debian 10 (Buster) due to some missing symbols in libraries:

/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so: undefined symbol: g_type_ensure Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_new Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so

Also it seems to have some problems with directories with spaces in their names ("Datei oder Verzeichnis nicht gefunden" means "File or directory not found"):

pressure-vessel-launch[7045]: Failed to start command: Failed to change to directory '/usr/local/games/SteamLibrary/steamapps/common/Streets Of Kamurocho' (Datei oder Verzeichnis nicht gefunden)

[smcv]

due to some missing symbols in libraries

Those warnings about gvfs modules are harmless, please ignore them. We know why they happen. They'll be fixed eventually, but because they're only cosmetic, it is not a high priority.

Also it seems to have some problems with directories with spaces in their names

The spaces are not the problem. The problem is that the game is in /usr/local, and the container runtime system replaces /usr with the read-only Steam Runtime, so the game isn't visible to the container. Workaround: use a different library directory below /home, /srv, /media or some other non-/usr directory.

[TTimo]

Selecting Proton 5.13 for a game and launching it will only download "Proton 5.13" and not "Steam Linux Runtime - Soldier", resulting in no games launching properly. This can be avoided by either installing both by hand or restarting Steam after the initial launch.

Fixed in Steam beta client >= Oct 21.

[nutta-git]

Network issues with Proton 5.13-1
system-info:
https://gist.github.com/nutta-git/ffccb825c1906774297247eb0d4e2f31
related:
https://github.com/ValveSoftware/Proton/issues/4001#issuecomment-709665083
https://github.com/ValveSoftware/Proton/issues/175#issuecomment-710733727
https://github.com/ValveSoftware/Proton/issues/1509#issuecomment-709639388

[Ammako]

Proton 5.13 doesn't seem to set up wine prefixes properly for me. There are several folders in user folder that don't get created. This results in certain games misbehaving because they can't find for instance the My Documents folder, which they need to write to and read from, and the games don't (can't?) create those directories by themselves if they are missing.

So far I know that Fable - The Lost Chapters and Final Fantasy XIV fail to run if My Documents folder is not present. You would have to manually create that folder after installing the game before it works (that, or use an older version of Proton.)

[Lepidos]

It also does not work along side amdgpu-pro

4288

[TTimo]

• Doesn't work on a GNOME Wayland desktop (needs https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508)
• Steam "Force Quit" feature doesn't work

Fixed in Steam beta client >= Oct 22 (make sure to switch 'Steam Linux Runtime - Soldier' to 'client_beta' branch for test).

[wwmm]

Did anyone test proton 5.13 with a xbox controller? I tried now in Monster Hunter World and a few functions are mapped to the wrong keys.

[wwmm]

Enabling the xbox configuration support in Steam's general controller settings fixed it. For some reason that was not needed in the previous versions.

[nicman23]

modorganizer2's (v2.2.2.1) vfs does not work with 5.13 - works with 5.0

there are no errors but it silently fails.

[l33tlinuxh4x0r]

I would like to add here that the cursor behavior has changed as well, I noticed this in Among Us as my mouse cursor was super super tiny on my 4K screen.

Going back to 5.0.9 uses the cursor from my window manager as expected.

I too use a 4k monitor and have noticed the tiny cursor in games. It doesn't effect games with a custom cursor though... just games that use the system cursor.

EDIT: I was wrong. All cursors are smaller then normal.

[Leopard1907]

It seems like Optimus systems are also borked with Proton 5.13, due to runtime.

http://us.download.nvidia.com/XFree86/Linux-x86_64/455.38/README/primerenderoffload.html

Which means you're on Intel all the time.

While i don't have a setup that needs DRI_PRIME ( Mesa stack ) , likely it is borked too. It is used for device selection for both GL and VLK.

[jyfletcher]

@Leopard1907 Seems to be borked for me with 5.13-1. Setting DRI_PRIME=1 still uses the integrated GPU instead of the discrete GPU.

[raneon]

I've noticed that Proton 5.13 doesn't work when I change the user to nobody. This happens as my Steam library is stored on my NFS server.

[yuiiio]

I think there are two issues with proton 5.13 and steam runtime soldier.

The changes in proton 5.13 have changed the preferred gpu for dxvk, so the following options should work for games that use dxvk. (Previously, of igpu and dgpu, dgpu was preferred.)
DXVK_FILTER_DEVICE_NAME="GTX 1050" %command%

Also previously, to use dgpu in vulkan games like doom 2016,
I was using options like VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/nvidia_icd.json", but with the steam runtime soldier won't work. (It worked by Editing _v2-entry-point to disable soldier.)

[jyfletcher]

@yuiiio Thanks for this! Setting DXVK_FILTER_DEVICE_NAME works for me with 5.13.-1 where setting DRI_PRIME would not.

[Cheaterman]

That's kind of a big deal, thanks @yuiiio !

[MischievousTomato]

I used this guide for setting up proton 5.0-9, but it doesnt work with 5.13-1 at all, since it was released.
https://community.chakralinux.org/t/how-to-use-steams-proton-to-launch-any-non-steam-apps/8236
I get the error described in #4269

[clarfonthey]

re: comments in the other issue that closed, which repo should an issue for not requiring kernel.unprivileged_userns_clone go? Is that a runtime issue or a Proton issue?

[kisak-valve]

Hello @clarfonthey, that's a pressure vessel issue. See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898446.

[clarfonthey]

Hi @kisak-valve, I don't think that the flag should be required even if Debian changes their position on it. I filed ValveSoftware/steam-runtime#297 to track this.

[wwmm]

I've tried to set the cpu affinity for a game through taskset -c 0,1,2,3 %command% and it did not work. Is this happening for the same reason as

Using a custom per-game driver (like with VK_ICD_FILENAMES or LIBGL_DRIVERS_PATH)

?

[Ammako]

kernel.unprivileged_userns_clone = 0 on LMDE here (debian base), and I've never had issues running games using Proton 5.13-1. Am I missing something? Does it depend on kernel version?

[clarfonthey]

@Ammako that should go into the new ticket.

[smcv]

Regarding kernel.unprivileged_userns_clone, see https://github.com/ValveSoftware/steam-runtime/issues/297#issuecomment-722331070.

[oliverklee]

On my system (Kubuntu Linux with Plasma), Proton 5.13-1 does not automatically disable the Compositor when running Elder Scrolls Online (306130, #556) in full-screen mode, while Proton 5.0-10 does, resulting in screen tearing (and possible slightly worse performance). I've also checked this by testing whether desktop transparency effects (that require the Compositor to be enabled) are still active when running ESO is full-screen mode.

[nutta-git]

Network issues with Proton 5.13-1
system-info:
https://gist.github.com/nutta-git/ffccb825c1906774297247eb0d4e2f31
related:
#4001 (comment)
#175 (comment)
#1509 (comment)

Updating Issue as Proton 5.13-2 RC was released. The network issues are still present with RC.
Sysinfo: https://gist.github.com/nutta-git/9d5c15cbfa6543510f359663e13c6fb3
Logs:
thedivision-365590.log
titanfall2-1237970.log
pathofexile-238960.log
monsterhunterw-582010.log

[GloriousEggroll]

This method allows vulkan layers, overlays, etc to work while still running inside the container:

https://www.reddit.com/r/linux_gaming/comments/jc2b77/mangohud_workaround_for_proton_513/gbx4cz6/?utm_source=reddit&utm_medium=web2x&context=3

[mindinsomnia]

I think there are two issues with proton 5.13 and steam runtime soldier.

The changes in proton 5.13 have changed the preferred gpu for dxvk, so the following options should work for games that use dxvk. (Previously, of igpu and dgpu, dgpu was preferred.)
DXVK_FILTER_DEVICE_NAME="GTX 1050" %command%

Also previously, to use dgpu in vulkan games like doom 2016,
I was using options like VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/nvidia_icd.json", but with the steam runtime soldier won't work. (It worked by Editing _v2-entry-point to disable soldier.)

Thankyou so much for the suggestion to use DXVK_FILTER_DEVICE_NAME=, I just tried it and now Proton 5.13 works for me. Previously it didn't work for any game it seems that uses DirectX 10 or 11 (but did for DX9 games). It also worked fine if I used the Proton launch command PROTON_USE_WINED3D. I've verified Vulkan is setup and working fine on my PC, so it wasn't that.

I have a laptop with RTX 2060 and naturally an onboard Intel GPU as well, so I guess the issue was that it was defaulting to the Intel GPU and not the RTX 2060? Is there some kind of permanent solution for this?

[mercuriete]

@mindinsomnia
I recommend you to set the environmental variables inside
/etc/environment
And then reboot
Its not an elegant solution but It make permanent until you delete the entry.

[mindinsomnia]

@mindinsomnia
I recommend you to set the environmental variables inside
/etc/environment
And then reboot
Its not an elegant solution but It make permanent until you delete the entry.

Thanks for the suggestion!
Do you (or anyone following this discussion) know if this issue is related to Proton or DXVK or something screwy with my setup?

[Arceliar]

The changes in proton 5.13 have changed the preferred gpu for dxvk, so the following options should work for games that use dxvk. (Previously, of igpu and dgpu, dgpu was preferred.)
DXVK_FILTER_DEVICE_NAME="GTX 1050" %command%

I just wanted to confirm that this fixed my blank screen issue with 5.13, and to note that this environment variable (and instructions -- basically use vulkaninfo to find out your deviceName) is documented in the dxvk repository. It wasn't clear to me if the change in default behavior was caused by proton or dxvk, but either way, the current behavior doesn't seem ideal.