Skip to content
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

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

Open
DreamingCuttlefish opened this issue Jan 1, 2024 · 6 comments · May be fixed by #1462
Open

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

DreamingCuttlefish opened this issue Jan 1, 2024 · 6 comments · May be fixed by #1462
Labels
bug Minor issue

Comments

@DreamingCuttlefish
Copy link

Describe the bug
I am attempting to use r2modman with the flatpak version of steam on linux. I can install mods but when I click "Start Modded" nothing happens.

To Reproduce
Steps to reproduce the behavior:

  1. Go to r2modman
  2. Click on "Start Modded" with a game
  3. Observe the game not opening

Expected behavior
I expected the game to open from steam

Additional Context
I realize this might not be able to be resolved on the r2modman side, but providing instructions to get it working with flatpak steam would be helpful. It seems this might be because of the steam flatpak's sandbox. Perhaps instructions could be added somewhere on github?

@DreamingCuttlefish DreamingCuttlefish added the bug Minor issue label Jan 1, 2024
@tacobell1896
Copy link

Are you unable to launch the vanilla version of the game too?

@DreamingCuttlefish
Copy link
Author

Are you unable to launch the vanilla version of the game too?

I can't launch it in vanilla either from the launcher. What does work is installing steam in distrobox, opening it, and then using r2modman. This makes sense because distrobox steam isn't sandboxed.

@SyrusDrake
Copy link

SyrusDrake commented Jan 3, 2024

I have the same issue. Oddly enough, I was able to launch unmodded before I had to reinstall r2modman to solve a different issue. Now I can't launch either way. So I'm not entirely sure if it's really a Steam problem?

Edit: This reddit post seems to offer a solution/workaround?

@DreamingCuttlefish
Copy link
Author

I was able to get it to work with the steam launch command in the "help" section after adding "xdg-config/r2modmanPlus-local" file permission in flatseal for steam. Listing this somewhere could be helpful.

@JohnTheCoolingFan
Copy link

I have the same problem playing Lethal Company. I've managed to work around this by having r2modman manage and download mods and I put the necessary files manually.

Do you think a "permanently install mods" is a good feature idea? Wanted to open a feature request but then noticed this issue.

@RossBrunton RossBrunton linked a pull request Oct 2, 2024 that will close this issue
@s3rvant
Copy link

s3rvant commented Feb 17, 2025

I was able to get it to work with the steam launch command in the "help" section after adding "xdg-config/r2modmanPlus-local" file permission in flatseal for steam. Listing this somewhere could be helpful.

I've tried this as well however does not work on my end. I'm running Kubuntu 24.04 with Steam via Flatpak and r2modman via .deb install (appimage gave error). I've ensured BepInEx bash scripts are executable and added various r2modman directories to Flatseal including the one quoted above. I've also updated Valheim properties to launch using the launch command on r2modman help tab and restarted Steam to ensure all settings should be in place. I can launch the game via Steam however it launches without mods.

I've also asked for help on the Valheim and Thunderstore Discord servers though so far no other ideas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Minor issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants