Skip to content

Option to use Flatpaks under Linux - #1462

Open
RossBrunton wants to merge 1 commit into
ebkr:developfrom
RossBrunton:flatpak
Open

Option to use Flatpaks under Linux#1462
RossBrunton wants to merge 1 commit into
ebkr:developfrom
RossBrunton:flatpak

Conversation

@RossBrunton

@RossBrunton RossBrunton commented Oct 2, 2024

Copy link
Copy Markdown
Contributor

This adds a configuration setting "linuxUseFlatpak" which controls whether Steam should be launched as a Flatpak or not. By default this is detected automatically based on the path, but an option in the settings can override the behaviour.

If this option is enabled, we first check if we are able to read from our config directory. If not, we display an error and ask the user to give us permission. If we do, then we launch Steam through flatpak rather than the binary directly.

Closes: #1144, #1051

@CLAassistant

CLAassistant commented Oct 2, 2024

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@RossBrunton

Copy link
Copy Markdown
Contributor Author

So I did all this work, and then decided to check if someone else had done it, and it seems both @wash2 ( #798 ) and @pedroVH ( #1064 ) have done this earlier. Guess I should have checked first.

Anyway, I think hopefully this should be more sophisticated, since it doesn't assume any hardcoded paths, allows the user to configure things and shows up an error if it isn't configured correctly.

Also, full disclosure, I've only tested this on Lethal Company, and I'm super unfamiliar with typescript.

@RossBrunton
RossBrunton force-pushed the flatpak branch 2 times, most recently from 0e76749 to a9ed932 Compare February 18, 2025 22:45
@RossBrunton

Copy link
Copy Markdown
Contributor Author

Is there anything blocking this from being accepted?

@gegoxaren

Copy link
Copy Markdown

Why has this not been merged yet?

This adds a configuration setting "linuxUseFlatpak" which controls
whether Steam should be launched as a Flatpak or not. By default this
is detected automatically based on the path, but an option in the
settings can override the behaviour.

If this option is enabled, we first check if we are able to read from
our config directory. If not, we display an error and ask the user to
give us permission. If we do, then we launch Steam through flatpak
rather than the binary directly.
@ebkr

ebkr commented Jul 22, 2026

Copy link
Copy Markdown
Owner

Apologies for the huge delay on this.

The reason it took so long was two-fold.

  1. I didn't want to support Flatpak Steam without also having a Flatpak build of the manager. It's pretty intuitive that both go together. The next release will make that properly available.
  2. I don't have a Flatpak Steam installation to test this easily and it sucks having to ruin my current installation just to do so. I'll obviously take the hit at some point but this will still be further delayed for a little bit as I don't have a huge amount of storage space to dual boot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] - Flatpak steam detected but cannot "Start Modded"

4 participants