⚠ Steam flatpak support #27
Comments
|
Sorry, I'm personally not interested in flatpak, so I won't spend my time on it, |
|
reopening because I got some more requests |
|
Yes, wondering how difficult this would be... I'd like to take a look, but might be a while until I can investigate. I'll report back anything I do find. |
|
Nice, thanks @podiki :) |
|
feel free to reopen |
|
reopening for an upcoming sticky issue |
|
I created a manifest, available at https://github.com/TheEvilSkeleton/flatpaks/tree/com.valvesoftware.Steam.Utility.steamtinkerlaunch. Adding Line 7994 is the following: |
|
Nice, thanks for the attempt! Looks like you're missing yad, which is required for the gui. |
|
That's odd. It's the first thing I build: https://github.com/TheEvilSkeleton/flatpaks/blob/7665a7234da1a4b1ee7080f6876332bf4dd56280/com.valvesoftware.Steam.Utility.steamtinkerlaunch.yaml#L16 |
|
Just chipping in to try and help, is this syntax correct? https://github.com/TheEvilSkeleton/flatpaks/blob/7665a7234da1a4b1ee7080f6876332bf4dd56280/com.valvesoftware.Steam.Utility.steamtinkerlaunch.yaml#L23 It seems like another modules block is being defined? At least I can't see that syntax elsewhere in the file. |
|
Thanks for trying to help @sonic2kk |
That's normal. Everything residing under If I type Which means Running
I'm guessing everything looks fine on yad's side? |
|
Ah, likely it is |
|
stdout of $PATH within steamtinkerlaunch might be interesting as well - if possible when started from steam (would help to see if it basically is sane and your path needs to be added or if it is removed from somewhere) |
Not even. It's empty: Flatpak remaps I manually appended |
|
Here's the log when starting Jurassic World Evolution 2: Click to expandGranted, I'm launching the game from another drive. |
|
this is what I meant in the previous post. steamtinkerlaunch initially checks multiple dependencies, including yad and write the corresponding path into a auto-created config. for unknown reasons your configs were filled with empty vars (I guess either distro or flatpak related, because this was fixed/improved several times already). Hard to tell how this can even happen without logs. |
|
|
|
Okay, it looks like emptying that directory did make it work and launch, but steamtinkerlaunch still crashes within a second. I checked through the terminal output, I get the following error: I checked if |
|
Oops, I forgot to update the manifest. Let me try it with the latest commit. |
|
either way, xdg-mime should be a dependency (and needs a better check in |
|
Has anyone here experienced issues running MO2? I created a separate issue for it (@frostworx mentioned it above), but we weren't able to solve it. I've attached two logs files that were created when attempting to start MO2 directly through the steamtinkerlaunch.log I'd appreciate any help you could provide. |
|
Just to be clear that the above was out outright ignored, it's believed the issue is related to STL Flatpak being unable to catch the Proton version used to launch MO2. Is there a way that the STL Flatpak could bundle some extra STL utility dependencies such as Perhaps another solution would be for STL to detect if it's running in a Flatpak and download dependencies to Just an idea I had off the back of a ticket a user of STL Flatpak raised. |
|
Just as a general FYI if issues do crop up and commits are made to try and fix them Pull Requests can be made to the beta branch of the Flatpak repo: https://github.com/flathub/com.valvesoftware.Steam.Utility.steamtinkerlaunch/tree/beta A short explanation of what it's meant to be fixing with a link to the issue would be good to include. Basically just need to update the git commit (currently at line 50) of com.valvesoftware.Steam.Utility.steamtinkerlaunch.yml And update the latest version of com.valvesoftware.Steam.Utility.steamtinkerlaunch.metainfo.xml The Flathub build bot usually builds PRs as they happen, and provides a link to install for quick testing. Otherwise the PR will have to be merged manually and it'll appear on the beta branch once it's published. How to install beta versions is outlined here: #540 (comment) If the beta build is confirmed to fix whatever the issue was you can post in the PR to that effect and it can be merged to stable for everyone to enjoy. Hopefully this all makes sense and helps the Flatpak version get better 😸 Any information about build status is available on Flathubs builds page: https://buildbot.flathub.org/ |
|
Just a heads up that some software center frontends like KDE Discover will list the Flathub Beta under the sources list, if Flathub Beta is enabled and if the app has a Beta available. Other software frontends might do this but I can vouch that KDE Discover does this (installed Firefox Flatpak Beta on my Steam Deck this way and other software this way on my desktop) EDIT: Just updated the Installation Wiki with notes on how to use the Beta branch, and I also updated the Flatpak wiki with information about using, reporting issues with and contributing to SteamTinkerLaunch Flatpak Beta. If I missed anything, got anything wrong, or anything else please feel free to amend where necessary 😃 |
|
With 907a03b I have attempted to add a warning logs, echoes and a yad dialog if STL detects itself running in Flatpak on a Steam Deck. I am not sure yet if this will work, not even sure if Flatpak STL can actually run the If it works, hopefully it will resolve the problem of Steam Deck users erroneously trying to install SteamTinkerLaunch from Discover, despite the warnings on the wiki and Discover page that this is not correct usage. |
|
Probing
I will point out that if you try to run STL on a Flatpak without Steam Flatpak running you'll never make it that far though because it'll complain that
I doubt stubbing |
|
Oh gosh I'm so sorry, I saw this reply when I got off work a couple of days ago but I completely forgot to reply (was preoccupied with adding HedgeModManager support to SteamTinkerLaunch)
Ooooooh thank you for the info here, I had no idea. But it makes sense, there is no need to bundle I'm not trying to "offload" this problem onto the Flatpak side but is there any way to check for a "missing dependency" with a Flatpak and warn? Like is there a way you could check if a user has Flatpak Steam installed? Since as you mention Flatpak STL is an extension for Flatpak Steam. But maybe this isn't possible. The "real" solution is for users to read the note on the Discover page and the wiki docs instead of blindly installing Flatpaks 😉 |
|
There is no way that Flatpak says something strictly relies on a parent that I can see. Even when you're specifically putting in the info that it requires a parent runtime like Steam. Whilst I was originally fleshing out the files it's something I spent a while trying to figure out, too. Just Flatpak quirks, I guess 🤷 |
|
Hey @HanPrower, I'm planning on releasing SteamTinkerLaunch v12 soon (in a few days or so). But this isn't a strict schedule or anything, so I'm just giving you a heads-up in case you want to test out the latest git and ensure everything is ok on your side. If there are any problems we can ensure those are fixed for v12, and of course I won't release if there are any critical issues that need fixing. I had hoped to give more notice on this but I've been a bit busy this time of year so sorry about that! If you need more time to test please by all means I can put release off 🙂 Thanks! |
|
So I got around to updating the beta branch of the Flatpak and it seems to work fine. I don't do much advanced stuff with it though day-to-day, so we'll just have to see when v12 is released 🤷 I don't really foresee anything breaking unless it's very specific to paths, or accessing software on the wider system. |
|
No worries, it's not feasible to test "everything" but as long as there isn't anything immediately broken I'm also happy with that :-) Thanks so much for testing! It'll probably be after the holidays that I get around to releasing v12 when I have more time to help debug any issues that come in, I don't want to release it and disappear for a week or two 😅 Great stuff :-) |
|
For some reason I can't get STL flatpak version to list all the proton versions I install. for example proton6.3 does not show in the list. Very odd. protonup versions don't show either. |
|
There may be some cached files that need clearing. I believe the Flatpak also uses |
Yep that fixed it. Thanks. |
I'm still experiencing this |
Is Steam Flatpak running whilst you try to use STL? |
|
Yes, but my issue has been resolved. I installed all steam runtimes and SDKs, reinstalled steam and STL, as well as rebased to uBlue NVIDIA and it works flawlessly now. However, big thanks for your concern. |
|
I tried with both the normal version and the beta and I was unable to use stl as a compatibility option, or run it while steam was running without the bwrap error. What did work was flatpak run --command="/app/utils/steamtinkerlaunch/bin/steamtinkerlaunch" com.valvesoftware.Steam compat add |
|
Manually running @HanPrower Please let me know if anything needs changed on my side for this - hopefully I didn't inadvertently break anything. |
No, nothing has changed. On a couple of occasions now it seems that when STL fails to run correctly it's the user's specific environment that's got issues, such as changing a Flatpak's permissions. |
|
So I installed STL while Flatpak steam was launched and installing Starfield, but It still gives me the missing sh error. I even ran it with the Compat option, (which i have no idea what that does tbh...) but I only got another error. Is this still an on going issue or am I missing something? flatpak run --command="/app/utils/steamtinkerlaunch/bin/steamtinkerlaunch" com.valvesoftware.Steam compat add |
|
This "missing sh" error is very vague, you should provide technical details such as a log and other debugging efforts you've went through. Did you maybe not restart Steam after running this command? I would assume you have to if you didn't, and honestly, you should have Steam closed when installing compatibility tools. If the output you provided is from a command to install SteamTinkerLaunch, did you perhaps miss this issue on the SteamTinkerLaunch Flatpak repo, which was also discussed above? flathub/com.valvesoftware.Steam.Utility.steamtinkerlaunch#110 If this is a wrong assumption, how did you install SteamTinkerLaunch Flatpak? Failing all of this, you may want to provide at the very least more technical information about the problem and the troubleshooting steps you have done so far. Attaching a log (not pasting text please) would be a good step if things still aren't working. Keep in mind that the Flatpak version may not have the latest SteamTinkerLaunch version, which was only reported by one user to work with Starfield. AFAIK no other users have tested, and none with Flatpak STL. Modding in general with Flaptak STL is also not really very reliable from what I have seen. Vortex is buggy as hell under Wine especially since v1.8.0, and results with modding games installed with Flatpak Steam seem to be poor (#821). So this is just a courtesy forewarning that modding Starfield under Linux is probably not a good idea, and even less so to attempt modding with Flatpak Steam games, unless you're experienced and can try troubleshooting yourself.
Please keep in mind that SteamTinkerLaunch is for experienced Linux users and is a tinker tool, if you're not experienced with tinkering or using compatibility tools in general, you may not have a great experience.
There is no ongoing issue per-se, this issue is open for Flatpak users to offer improvements and technical suggestions (initially this issue was opened to discuss the feasibility and implementation approach for STL Flatpak). If you're referring to the |
|
After three and a half years and awesome work by the community, the Flatpak is in a state were this issue is likely no longer necessary. We can probably just have dedicated Flatpak questions here or on the Flatpak repo (which didn't exist when this issue was opened). Closing this also means we won't ping users who commented ages ago and didn't unsubscribe. I think this mega issue has served its purpose well enough :-) Thank you to everyone who commented, from now on we can use separate issues though. |
and others
Currently there is no easy way to stl use in flatpaked version of Steam. That shouldn't be hard, here is example of other addon: https://github.com/flathub/com.valvesoftware.Steam.Utility.protontricks
The text was updated successfully, but these errors were encountered: