Lutris, the all encompassing game manager for installing games from various stores and services (both Native and with Wine / Proton) has a new version out. Plus, the Flatpak is finally ready, making it real easy to run on Steam Deck.
So now you can head to Flathub to get it across pretty much any Linux distribution, or directly via the Discover store on Steam Deck in desktop mode.
What's new in version 0.5.11:
- Fix for some installers commands exiting with return code 256
- Change shortcut for show/hide installed games to Ctrl + i
- Show/hide hidden games is assigned to Ctrl + h
- Install game launcher before login for services that use one.
- Add Amazon Games integration
- Added SheepShaver, BasiliskII and Mini vMac runners
- Don't perform runtime updates when a game is launched via a shortcut
- Support variables in script URLs
- Fix crash when Lutris is unable to read the screen resolution
- Enable Gamescope on Nvidia >= 515
- Fixes for Steam shortcuts
- Add Gnome Console and Deepin Terminal to supported terminal emulators
- Fix crash when Mangohud is used alongside Gamescope
- Translation updates
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
I didn't even know that there are Amazon Games, until very recently. That was quite a shock news to me. So its another launcher cause we really needed more of those?
Good to see support for all those launchers i guess though.
Good to see support for all those launchers i guess though.
0 Likes
I've had the beta flatpak installed and I'd like to switch to the official one. Is there some correct way to do this to make sure I don't lose settings? Like someone said earlier, the official and beta seem to be the same version at the moment.
0 Likes
Won't be at my desktop for a few weeks, but will do once I get home.
What works on nfs: installing any gog game which does not use the gog installer and running any installed game viw lutris, same goes for installing any steam game or playing it, so rights are okay.
What does not work: installing any game that uses the gog installer while the lutris game directory is set to the nfs
If I move the lutris game directory to local that same game installs just fine, copy everything over to the nfs, change lutris directory and game runs fine.
Just to clarify - "installing any gog game which does not use the gog installer", does this mean installing directly with a manual extraction, or simply not using lutris "gog install" script?
IE: Do you mean it works when not using the GOG installer that comes with the game, or not letting lutris download & install for you?
This sounds like it could be some kind of path settings issue or? Definitely gonna need that debug output to see what it's doing.
I've had it before where lutris has done the download for me, and somehow not managed to get it working (saying missing file) - but selecting my own downloaded gog install file worked fine. Is this what you're getting?
When selecting games to install all downloads work (either cache dir local or cache dir on nfs), then some use lutris script and scummv or other use lutris scripts and for example dosbox. Those work fine. It's when there is no other option but wine/gog installer (one with the green buttons), the installer starts and then exits with code 256, that is it, it won't install if the location is nfs.
I will send the output but 4 more weeks from home, sorry :)
1 Likes, Who?
I've had the beta flatpak installed and I'd like to switch to the official one. Is there some correct way to do this to make sure I don't lose settings? Like someone said earlier, the official and beta seem to be the same version at the moment.By all accounts, they are exactly the same. From what I can see they've basically just re-released Beta 1 as stable. Which is odd considering several bugs for fixed after beta 1 in the repo that didn't make it into stable. But nevermind.
Anyway onto switching flatpak versions, you can do this with a very very simple process.
Firstly, just double check that you're actually currently on beta:
$ flatpak info net.lutris.LutrisYou should see "Branch: beta" within the output.
Install stable:
$ flatpak install net.lutris.LutrisYou'll get a message about remotes found with similar refs, select the number which does not say "flathub-beta" (so the other one, not beta)
If you select the beta by accident, you'll get a message about it already being installed.
Verify both are installed with:
$ flatpak listYou should see two entries for Lutris, beta and stable. If so, you've now got both installed.
Now, test it by opening beta first, so you know what to expect (all data intact):
$ flatpak run --branch=beta net.lutris.LutrisEverything okay? Cool!
Now test stable:
$ flatpak run --branch=stable net.lutris.LutrisEverything again, should be intact and should be the same!
Assuming that went well, make the current stable branch the default branch:
$ flatpak make-current net.lutris.Lutris stableAt this point, opening the flatpak lutris should now always open the stable branch instead of the beta branch!
Optional Changes
Personally, I would leave it at this point, so that you can always switch back to beta should you want to try it in the future.
However, if you don't want the beta installed at all then you can now safely remove it:
$ flatpak remove net.lutris.LutrisYou'll be presented multiple options - remove the one that says "app/net.lutris.Lutris/x84_64/beta".
If you don't want the extra repo "flathub-beta" anymore (again, personally I'd leave it there) you can remove that too if you wanted:
$ flatpak remote-delete flathub-betaDone, you now only have stable installed!
When selecting games to install all downloads work (either cache dir local or cache dir on nfs), then some use lutris script and scummv or other use lutris scripts and for example dosbox. Those work fine. It's when there is no other option but wine/gog installer (one with the green buttons), the installer starts and then exits with code 256, that is it, it won't install if the location is nfs.
I will send the output but 4 more weeks from home, sorry :)
Yeah, sounds like a really strange issue. Going to need the output from that
Does the same thing happen with other drives? Eg, if you install onto sdb instead of sda/nvme any problems?
0 Likes
I noticed the Amazon Games integration a few days ago and was very pleased. I have a lot of freebies in my Prime account and previously had to jump through hoops to install them. Now I just need to decide if anything in my account is actually worth playing...
They give a ton of amazing indies, games that probably will never receive attention on Steam.
I dunno if you like rhythmical games, but look if you have this on your account:
https://store.steampowered.com/app/398030/Old_School_Musical/
Wait... mistermv in this game, what?! I didn't know about it!
0 Likes
I'd been claiming these games for months, but rarely used them... who needs yet another launcher, right?
But still, seeing them all like this was a hell of a shock!
!Scaine's Amazon library via Lutris
But still, seeing them all like this was a hell of a shock!
!Scaine's Amazon library via Lutris
1 Likes, Who?
The Amazon integration doesn't work properly yet. The only thing which works, is connecting your account and load the list of games. None of the games can be installed, it just fails with an error on the terminal.I just tried Rogue Heroes and it gives:
For the time being, I can suggest using the CLI tool Nile, it works great.
2022-08-29 17:56:46,410: Unable to get games from API: HTTP Error 405: Method Not Allowed
2022-08-29 17:56:48,035: Failed http request https://sds.amazon.com/amazon/
2022-08-29 17:56:48,036: There was an error getting patches: 1ebe8dd8-ca72-cc12-ab87-8683f149801e
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/lutris/gui/application.py", line 628, in on_game_install
game_id = service.install(db_game)
File "/usr/lib/python3.10/site-packages/lutris/services/base.py", line 252, in install
installer = self.generate_installer(db_game)
File "/usr/lib/python3.10/site-packages/lutris/services/amazon.py", line 605, in generate_installer
file_dict, directories = self.get_game_files(details["id"])
File "/usr/lib/python3.10/site-packages/lutris/services/amazon.py", line 544, in get_game_files
game_patches = self.get_game_patches(game_id, manifest_info["versionId"], hashpairs)
File "/usr/lib/python3.10/site-packages/lutris/services/amazon.py", line 504, in get_game_patches
raise UnavailableGame(
lutris.exceptions.UnavailableGame: ('Unable to get the patches of game, please check your Amazon credentials and internet connectivity', '1ebe8dd8-ca72-cc12-ab87-8683f149801e')Meanwhile, A Knight's Tale seems to work:
!Lutris installer showing "A Knight's Tale"
It's downloading now - looks like it creates an "amazon" directory in your default Lutris folder.
EDIT Hmmm, ah well. After downloading, I hit "Launch":
!Dialog says "Tried to launch a game that isn't installed".
EDIT2 After stopping/starting Lutris, it recognises it's installed! But still doesn't run. Logs show it trying, but it doesn't take.
2022-08-29 18:15:58,395: Unable to load libGLX_nvidia.so.0
2022-08-29 18:15:58,395: Unable to locate libGLX_nvidia
Started initial process 68085 from gamemoderun /home/scaine/.local/share/lutris/runners/wine/lutris-7.2-2-x86_64/bin/wine /home/scaine/Games/Lutris/amazon/a-knights-quest/drive_c/game/AKnightsQuest.exe
Start monitoring process.
ERROR: ld.so: object 'libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object 'libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
fsync: up and running.
Initial process has exited (return code: 13568)
Monitored process exited.
Exit with return code 13568
2022-08-29 18:16:06,450: Game still running (state: running)
2022-08-29 18:16:06,450: Stopping A Knight's Quest (wine)Last edited by scaine on 29 August 2022 at 5:17 pm UTC
0 Likes
You gotta be so careful with flatpak's with their origins
An official flatpak beta has existed for a while. It is legit but beta and not on flathub :)
Edit: Here is the link.
I checked that link and it seems to be the same as the publisher details on flathub - am i missing something?
0 Likes
Sorry, that's on me!You gotta be so careful with flatpak's with their origins
An official flatpak beta has existed for a while. It is legit but beta and not on flathub :)
Edit: Here is the link.
I checked that link and it seems to be the same as the publisher details on flathub - am i missing something?
I made a mistake and forgot that the flatpak had previously been released only in the beta branch after installing it. I thought it had released stable, completely forgot it was beta.
So in any case, both are official and from the same source.
0 Likes
I've had the beta flatpak installed and I'd like to switch to the official one. Is there some correct way to do this to make sure I don't lose settings? Like someone said earlier, the official and beta seem to be the same version at the moment.By all accounts, they are exactly the same. From what I can see they've basically just re-released Beta 1 as stable. Which is odd considering several bugs for fixed after beta 1 in the repo that didn't make it into stable. But nevermind.
Anyway onto switching flatpak versions, you can do this with a very very simple process.
Firstly, just double check that you're actually currently on beta:
$ flatpak info net.lutris.Lutris
You should see "Branch: beta" within the output.
Install stable:
$ flatpak install net.lutris.Lutris
You'll get a message about remotes found with similar refs, select the number which does not say "flathub-beta" (so the other one, not beta)
If you select the beta by accident, you'll get a message about it already being installed.
Verify both are installed with:
$ flatpak list
You should see two entries for Lutris, beta and stable. If so, you've now got both installed.
Now, test it by opening beta first, so you know what to expect (all data intact):
$ flatpak run --branch=beta net.lutris.Lutris
Everything okay? Cool!
Now test stable:
$ flatpak run --branch=stable net.lutris.Lutris
Everything again, should be intact and should be the same!
Assuming that went well, make the current stable branch the default branch:
$ flatpak make-current net.lutris.Lutris stable
At this point, opening the flatpak lutris should now always open the stable branch instead of the beta branch!
Optional Changes
Personally, I would leave it at this point, so that you can always switch back to beta should you want to try it in the future.
However, if you don't want the beta installed at all then you can now safely remove it:
$ flatpak remove net.lutris.Lutris
You'll be presented multiple options - remove the one that says "app/net.lutris.Lutris/x84_64/beta".
If you don't want the extra repo "flathub-beta" anymore (again, personally I'd leave it there) you can remove that too if you wanted:
$ flatpak remote-delete flathub-beta
Done, you now only have stable installed!
Thank you so much! The flatpak run commands didn't work on Steam Deck for some reason but nevertheless I got the stable installed and made default. Everything seems to work as expected.
0 Likes
Patreon
PayPal
See more from me