Steam Deck controller doesnt work after Lutris flatpak update, possibly runtime related.

[pizzadude]

The Steam Deck controller does not work in Lutris after the latest update to version 0.5.18. I think this is flatpak runtime related because Heroic Games Launcher had the same issue recently, and downgrading the runtime to the 2023 one fixed the issue.

here is the heroic games launcher issue for reference Heroic-Games-Launcher/HeroicGamesLauncher#4108

Downgrading the Lutris flatpak with "Warehouse" or with the terminal is the workaround until this gets resolved.

I also posted this issue here: lutris/lutris#5766 , but I was told to post it in this repo also.

[Eproms]

Control don't work in game mode for me 😑

[scottruzal]

Just started having this issue today as well. Does anyone know what the steps are to downgrade using "Warehouse" or via terminal?

[pizzadude]

Just started having this issue today as well. Does anyone know what the steps are to downgrade using "Warehouse" or via terminal?

Install Warehouse, select Lutris, and then do this:

[mittler-works]

I have the same problem on the Steam Deck. Downgrading is a temporary workaround. It cannot be the permanent solution.

The problem is that those having this issue might not be the ones who could fix the problem in a professional way. And those who could fix it might not have a steam deck.

So if anyone could provide guidance on how to get startet debugging this flatpak stuff, I'm happy to give it a try.

[rollercoaster]

I have the same issue. It was working with existing games, updated lutris via discover, steam deck inbuilt controller no longer working .. I tried a new wine folder with everything default, with both ge-proton latest and wine-ge-8-26

I had been exclusively using wine-ge-8-26 before the updated. After the updated it auto installed ge-proton. When I try this with a game that I know was already working, on launch in game mode, I can hear the audio but the screen still shows the steam loading animation and never shows the game

[A6GibKm]

This seems to be an issue related to the runtime, it was updated from GNOME 45 to 47 in a single commit recently, but the beta branch (at the flathub-beta repo) did have 46 for a while. If anyone wants to contribute to finding the solution I would suggest to first see if the commits using GNOME 46 did have this issue.

You can use

flatpak update --commit=<commit_code> <Application ID>

to checkout a specific commit. (I don't remember if the commit is the one from github or flatpak. You can use

flatpak remote-info --log <repo_name> <Application ID>

to get the list of the latest commits.

I suspect the right place to report this is the freedesktop sdk (https://gitlab.com/freedesktop-sdk) which the GNOME runtime is based on but that depends on whether it is reproducible on 46. Note that 45 and 46 are based on FDO 23.08 while 47 is based on 24.08.

[mittler-works]

Sooo I tried it. The latest selectable commit from lutris beta before the update to gnome runtime 47 is:

    Commit: 1469ae065b697f6c4d8908f270bc8a2426a942b026b314675ef96f4ec879a0ee
   Subject: I don't understand, don't ask me. (b8ff8b2a)
      Date: 2024-10-13 19:52:06 +0000

So I installed it via sudo flatpak update --commit=1469ae065b697f6c4d8908f270bc8a2426a942b026b314675ef96f4ec879a0ee net.lutris.Lutris/x86_64/beta and then sudo flatpak make-current net.lutris.Lutris beta.

I had masked lutris for the above workaround, so I had to first unmask it: sudo flatpak --remove mask net.lutris.Lutris. I noticed, that you can only mask the stable version with sudo flatpak mask net.lutris.Lutris/x86_64/stable so it is possible to update beta while preventing updates for stable.

Long story short, with beta commit 1469ae065b697f6c4d8908f270bc8a2426a942b026b314675ef96f4ec879a0ee (i.e. gnome runtime version 46) it works fine.

[A6GibKm]

Thanks, then it is probably an issue or change in behavior in the 24.08 FDO runtime. I will ask around, and maybe do a PR to downgrade to 46 in the meanwhile.

[mittler-works]

You're welcome and thank you, too! For the record, I've tried the next commit in history to find more evidence, i.e.

    Commit: 3905696721ac81ee885709def81b4b923b6664bd9c5514bc3c21e1e7d2baa8ad
   Subject: Update runtime to GNOME 47 (4c032834)
      Date: 2024-10-13 22:24:40 +0000

and it stops working. So it breaks within this diff: b8ff8b2...4c03283 which makes it very likely that it is due to the gnome runtime update.

[A6GibKm]

Opened #468, please test it once CI finishes and produces a testable build.

[A6GibKm]

Would it be possible to open the app via the CLI

flatpak run net.lutris.Lutris -d

then see if there is anything in the logs that might point to a cause?

[A6GibKm]

Has anyone managed to make the controller with certain games / wine version combinations? Or it does not work at all?