search

Heroic-Games-Launcher / HeroicGamesLauncher

A games launcher for GOG, Amazon and Epic Games for Linux, Windows and macOS.
https://heroicgameslauncher.com
GNU General Public License v3.0
8.31k stars 440 forks source link

Heroic flatpak & steam rpm - No functional Steam Input on Fedora 38 #2785

Open ScrambleTheRamble opened 1 year ago

ScrambleTheRamble commented 1 year ago

Describe the bug

I've spent the last few days debugging a Steam Input issue that I had on 2 Fedora 38 machines, both had Steam installed from the repositories (as an rpm) and Heroic Games Launcher from the flathub repository,

For some reason I wasn't able to get Steam Input to work for games installed through Heroic while everything worked fine for native Steam apps. I did some further testing and replaced the flatpak installed Heroic with the rpm found under releases and with that installation I could use steam input as expected.

I'm not sure if this is a flatpak issue, packaging issue or distribution issue so let me know if I should file this somewhere else.

Add logs

n/a

Steps to reproduce

  1. Install Steam from the software manager with source being the rpm in rpm-fusion-nonfree
  2. Install Heroic from the software manager (from flathub)
  3. Install any game from either gog or epic
  4. Add to steam
  5. Launch game through Steam

Expected behavior

Gamepad shouild work through Steam Input

Screenshots

No response

Heroic Version

Latest Stable

System Information

Additional information

No response

severtheskyline commented 10 months ago

I have the same issue and setup, running Fedora 39 Workstation, GNOME on Wayland with Heroic via Flathub and Steam on the RPM repo. Steam simply doesn't detect Heroic for Steam Input, when running just Heroic with Steam not running, controller support works fine. A mildly working fix is disabling the desktop Steam Input, since disabling it for Heroic/Heroic games does nothing.

casasfernando commented 7 months ago

I just hit this issue myself on my desktop PC, running Debian 12, Steam client from the distro package and the latest release of Heroic flatpak (same scenario as the guys running Fedora). I suspect this is a permission issue because after some troubleshooting I found that if I switch to Heroic's appimage (also latest version) while keeping everything else the same, steam input works correctly for non-steam games added from Heroic. What puzzles me is that on my Steam Deck running (what I believe) is an equivalent scenario (non-flatpak Steam + flatpak Heroic) I don't have this problem at all and steam input works fine.

I will try to look into udev rules for Steam's "virtual controller" that may be present in the Steam Deck but I may be missing on my desktop PC. Certainly flatpak permissions for Heroic on both machines are exactly the same.

casasfernando commented 7 months ago

I found two issues reported for Steam client that seems to be either the cause or closely related to this issue:

it also explains why the problem doesn’t affect the Steam Deck using game mode (Steam overlay integrated in gamescope).

casasfernando commented 7 months ago

BTW I suggest changing the issue title to something more accurate like “Heroic flatpak & Steam client non-flatpak - No functional Steam Input” since clearly is not only a Fedora issue.

Also while this seems to be a Steam client issue I would leave this open for tracking and for any other users finding the same problem, to get more information.

dorianve commented 7 months ago

It's been driving me crazy, glad I stumbled across this open issue. I tried to find more information. I found another related open issue on Flatpak's repo

https://github.com/flatpak/flatpak/issues/1756

It seems this problem has been around since at least 2018 then.

I'm on Nobara, but I suppose this issue occurs on any distro