-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No games can run with Proton 5.13 or higher #642
Comments
This is because of pressure-vessel not working in Flatpak. Related : flatpak/flatpak#3797 |
Hm, what it's trying to call? |
With |
Yep, it's trying to run something on host:
Adding |
Tried to add |
Now it's trying to access host's ld.so.cache from inside the sanbox, could be allowed with |
Now with |
Errors and crash while launching Deep Rock Galactic with Proton 5.13-2 Same game with 5.0.9 |
5.13 doesn't work with any game here |
No need for individual reports. It's quite clear pressure-vessel doesn't work with this flatpak. |
So what's the recommended solution for this? Should we just sit still and wait for a fix or is there something that we have to manually do to circumvent the issue? |
@smcv may be more of an expert on this. I don't really have any good answers. |
BTW you can try my proton flatpak build https://github.com/gasinvein/proton-flatpak. It's built on on top of FD.o SDK from source, so doesn't need Steam Runtime at all. Some minor features are still missing (e.g. bundled fonts), but it should work in most cases. |
IMHO this native flatpak proton build is awesome and would be great if this treasure available for everyone on Flathub. I would say an urgent need to push it on Flathub now since now nothing works with Valve's Proton 5.13 with Steam flatpak build. Also in terms of disk space:
|
At the moment there are no good answers: making complex things work together takes time. It's in progress. Proton 5.0 is still available and still works the way it always did. Proton 5.13 is the first version to run Proton in a container with a different runtime environment, instead of as a child process of Steam. The code required to make this work is fairly elaborate, and is not currently compatible with Flatpak: the pressure-vessel runtime tool should eventually work with the Steam Flatpak app, but at the moment it can't. Solving this needs new code in both Flatpak and pressure-vessel (flatpak/flatpak#3797 is the Flatpak side). This is exactly the same problem as not being able to run native Linux games under the "Steam Linux Runtime" compatibility tool from inside the Flatpak app (it's the same container launcher being used), except that the arrangements for Proton add an extra layer of complication, because native Linux games don't run arbitrary setup commands before running the actual game but Proton games do. The container setup used for Proton 5.13 has other limitations that we hope will be solved in future, even without Flatpak being in the picture: controller hotplug doesn't work, primusrun almost certainly doesn't work (I haven't actually tried but I'm fairly sure it won't), it currently requires a valid
Yes, please be patient. The solution for this will not be in this app, it will be in Flatpak and in pressure-vessel. Please don't ask for progress reports, that will only make it take longer.
What you're seeing here is an early prototype of making pressure-vessel work from inside Flatpak. We don't really expect people to give it full host access, and in future it shouldn't need to break down the security boundary between container and host like this, but we have to teach it to walk before we can make it run. If you are not comfortable with letting Steam execute arbitrary code on the host, don't configure it with For people who don't care whether there is a sandbox bypass going on, I think there are some environment variables we can set to tell pressure-vessel to put its sockets in a directory that is shared by the host and the Flatpak sandbox, which might make this work. I'll check what they are when I'm back at work next week. However, launching pressure-vessel from Flatpak is completely unsupported - what you're seeing there is early development code that we don't really expect to work. Letting Steam see the host graphics stack in |
If this feature is not ready yet, why not make it opt-in? |
What access does --filesystem=host-os grant? Is it access to all files on the system? |
Make sure to at maximum give host-os:ro. It is not a good idea to give unlimited write access to things. |
Thanks I was more wondering what it allowed the application to see if I enable that. Is it just system directories such as /usr /etc or is it everything? |
Sorry, how Valve deploy Proton 5.13 is not my decision. Proton 5.13 was compiled with a newer library stack than the standard Steam Runtime 1 'scout' (which is mostly from 2012 and is really showing its age), so it needs to be run using a newer runtime. The newer Steam Runtime 2 'soldier' is only available as a container, partly because otherwise it would not be possible to run it on systems with older glibc, and partly because continuing to patch random libraries to look at If people want to do unofficial builds like https://github.com/gasinvein/proton-flatpak against the freedesktop.org SDK instead of against soldier, you're welcome to do so, but Valve are not going to support the result. The only runtime environments they intend to support are scout and soldier (and to some extent also Steam Runtime 1½ 'heavy', which was a stopgap for Steam's embedded web browser, but heavy is not a full runtime environment and honestly I'm surprised it works as well as it does). |
In principle, yes, this is good advice. In practice there's usually no difference, because none of the files selected by |
For people who don't care about the sandbox security boundary and want to experiment with this, you can try this procedure:
As I said above, this is very early development code. It currently requires opening big enough holes in the security boundary to drive a tank through, and it's completely unsupported. The plan is that new code in both pressure-vessel and Flatpak will make all those workarounds and security holes unnecessary, by making everything work automatically - but that hasn't been implemented yet. It's in the queue... |
Thanks, that's in the ballpark of an explanation I was hoping to see by pinging you. :) |
Latest Proton 5.13 community build packaged and available on Flathub now. 🎉 You can install it via GNOME Software/Discover (KDE) or via CLI:
and select Proton community build in Steam: Thanks @gasinvein and flathub community for their work. ❤️ |
Thank you! I assume this doesn’t use pressure-vessel right? |
@TheGreatestJannet Yes, it's built against freedesktop-sdk instead of steam runtime. |
Personally, I find flatpak nicer to use for proton purposes because of the separately packaged protons. Means I don't have to manually chase updates for third party versions or wait for steam to download them outside my regular update schedule. The packaged proton versions, especially the gloriouseggroll one, are well worth mentioning externally, even if they aren't required anymore. |
Sure, why not. This issue anyway is more about making the official Proton runtime work since that gets picked up automatically. |
While resolved, I think this issue should stay pinned for visibility. Maybe even edit @tim77's original post again to indicate the resolution (i.e. you need flatpak 1.12+ to run Proton). |
Hello, Unfortunately, I still can't get this to work. I'm on Guix using flatpak version With proton version
With Proton version
I'd appreciate any help. Thanks. |
@minikN Did you just update flatpak? If so, reboot or manually restart |
EDIT: with |
Guess I'm misunderstanding something in generel (sorry I'm new to flatpak), because I don't have an |
It's usually installed in |
|
Reboot didn't help unfortunately. Is this relevant? |
Yes, it is. It's exactly why I suspected that the old flatpak-portal is still running. |
No idea if I have it set up already. I'm not able to find any information specific to Guix apart from just installing the packages. The only processes that seem to be related are
|
Don't confuse |
@gasinvein So after some digging around I found the #!/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/bash
export XDG_DATA_DIRS="/gnu/store/py9ak4g4cvikpcblj2ksw8l9agsjpn1m-shared-mime-info-1.15/share:/gnu/store/3374zddwfb0m8711k2jrvhwr1s2fkvq3-glib-2.62.6/share:/gnu/store/kksi41cjrrabsxsmpk8asj5grinlnd23-gsettings-desktop-schemas-3.34.0/share${XDG_DATA_DIRS:+:}$XDG_DATA_DIRS"
export GIO_EXTRA_MODULES="/gnu/store/yi78ngl21120hzm9vivdj0mmx57sxr02-glib-networking-2.62.2/lib/gio/modules:/gnu/store/w6cb40sia4cfb9glmilcqpig8qysik5y-dconf-0.36.0/lib/gio/modules${GIO_EXTRA_MODULES:+:}$GIO_EXTRA_MODULES"
exec -a "$0" "/gnu/store/gffkm7yimvkdn4spzw0lgrz62l15nzv6-flatpak-1.12.1/libexec/.flatpak-portal-real" "$@" So i started it manually via
It's the same error now with the community version of Proton. |
This error is unrelated: prefix upgrade has failed due to missing |
Actually I'd love to fix it right away :) |
Well, if this games' wine prefix is expendable, just remove or rename the |
@gasinvein Everything works now. Testes with 2 games. Thanks! |
Consider reporting this to you distribution. If |
I am really sorry to amend to this already too long discussion but, time has passed, and I still can't run Steam embedded Protons versions. Flatpak community builds works but not the defaults versions. Steam run with: Here the full log: https://paste.sr.ht/~stacyharper/130066d6a9ad8db61e71466759b322ee8992dac4 I am trying to use Proton Experimental here but other version fails with similar logs. This is from Alpine Linux Edge. Someone could help me on that ? |
This is an issue tracker, not a support forum, and the issue that is tracked here was resolved in Flatpak 1.12.x. If you are already using Flatpak 1.12.x, please open a separate issue with details of how your system is set up. The key line from your log is probably this one:
If I understand correctly, Alpine Linux is a musl-based distribution? Flatpak and Steam are both designed with glibc in mind, so it is not necessarily surprising if not everything is working as you would expect on musl. |
TLDR: you need new
flatpak 1.12.1+
version to run official Proton. Or as workaround install community build of Proton which doesn't use pressure vessel https://github.com/flathub/com.valvesoftware.Steam.CompatibilityTool.Proton#installation.Game information
Distribution name and version where applicable
Fedora release 32 (Thirty Two)
Flatpak info
Flatpak 1.8.2
nvidia-455-28
default
host
Problem description
After Proton 5.13 update in Steam games won't work with this new Proton version.
Terminal output log: steam-proton5.13.log
Does this issue reproduce with native Steam
Have not tested
The text was updated successfully, but these errors were encountered: