ebkr
[BUG] - Launches 2nd instance of Steam
Describe the bug When the Steam client is running, and using r2modman for the first time during the Steam session, after clicking "Start modded" to play REPO, the Steam client goes offline and a 2nd instance is opened.
To Reproduce Steps to reproduce the behavior:
- Launch the Steam client.
- Launch r2modman
- Click "Start modded" in r2modman to launch REPO
- The Steam client will go offline and a 2nd instance will be opened.
Expected behavior When clicking "Start modded" the game should be launched without opening a 2nd instance of the Steam client first, and the Steam client should not go offline.
Additional context This happens only the first time the "Start modded" option is used for REPO. Clicking "Start modded subsequently, does not trigger this issue.
OS: Fedora 42 workstation with KDE Plasma r2modman version: v3.2.0, rpm from the build folder GPU: nVidia GTX 1080ti Proton version: hot fix and 9.0.4
How do you have Steam installed? Is it from the Software application, and if so, is it from Flathub or a different source?
I also experience this same behavior with the same OS. I am using the flatpak, flathub, version of steam. I've always thought it was just how the interaction works with the flatpak.
- I don't play repo, this happens when I play modded valheim from the launcher.
Upvote, same thing here with KDE Plasma, CachyOS (Arch Linux), Flatpak Steam, happening with RoR2.
r2modman does not currently support auto launching of flatpak steam. If you click launch modded it runs steam on the system and not from the flatpak instance. This is why 2 steams are able to open.
If you want to launch games inside the flatpak automatically without having to pass the arguments manually everytime you can find a temporary solution I made here: https://github.com/ebkr/r2modmanPlus/issues/1051#issuecomment-3664174846
r2modman does not currently support auto launching of flatpak steam. If you click launch modded it runs steam on the system and not from the flatpak instance. This is why 2 steams are able to open.
interesting, i don't have steam installed via package manager (pacman), only flatpak. I even pointed r2 to look for the game and steam on .var/... directory, since it's the default for flatpak, it launches, but always a second instance. any clue in this behavior?
r2modman does not currently support auto launching of flatpak steam. If you click launch modded it runs steam on the system and not from the flatpak instance. This is why 2 steams are able to open.
interesting, i don't have steam installed via package manager (pacman), only flatpak. I even pointed r2 to look for the game and steam on .var/... directory, since it's the default for flatpak, it launches, but always a second instance. any clue in this behavior?
As long as steam has the required packages to run (without actually having the native steam package installed) it will run on your system natively due to how it is handled. Launching mods through r2modman will launch the flatpak steam.sh file on your system natively and through the steam.sh all the normal steam runtimes are downloaded (or in some cases it uses the same .var directory just running natively instead of flatpaked).
Steam doesn't work like every other package on a linux system because it downloads a bunch of external runtimes that aren't from a package manager. All that happens when you download the steam package is a file similar (or the same) as the steam.sh you find in the steam folder gets downloaded and the first time you launch it it downloads steam's runtimes.