Quoting: Eike

Quoting: BlackBloodRumFor example, I accidentally dumped 70+ hours into Saints Row 2 (with mods like GoTR and proton) on the Steam Deck alone. However that game is actually tagged by Valve as incompatible with the Deck (It has the in valves testing this didn't work yadda yadda warning).

Erm, no, like most of my 17 (not really) incompatibles, it's got the "Valve is still working on it" badge [External Link].

So I got some terminology wrong big deal. Either way it says "Unsupported" - which most people would take to mean "it doesn't work".

Proof:
https://i.imgur.com/YbIyv0c.png [External Link]

For most people, this does not mean "Yeah it works just fine".

If your average non-technical gamer saw this, they would think/believe the game doesn't work. My point was that the game works without Proton-GE and works with regular proton 7.0 without any proton tweaks[1].

[1] I installed the mod because the game has bugs that are present even on Windows, that mod simply fixes those.

View this comment - View article - View full comments

Yeah about the "playable" rating system. I've personally found it doesn't necessarily accurately reflect the title's playability.

For example, I accidentally dumped 70+ hours into Saints Row 2 (with mods like GoTR and proton) on the Steam Deck alone. However that game is actually tagged by Valve as incompatible with the Deck (It has the in valves testing this didn't work yadda yadda warning).

So personally, I'd suggest not using solely that rating system and instead just trying games and finding out for yourself.

View this comment - View article - View full comments

Quoting: Valck

Quoting: Eike

Quoting: denyasisI think it's cool, but support until 2025... That seems a little short. Is it?

I mean most won't get these until 2023, and maybe I'm weird, but I don't buy hardware with the intent to replace it in just a few years.

It should mean that they will bring new processors for the platform in 2025 - not that you cannot use your old processor anymore after 2025. I cannot think of a case where I replaced a processor, but not mainboard, RAM, ...

Twice in recent memory, with current AM4... 1800/3700/5800.
Multiple times more in ancient history, which many of you may not remember, or weren't even born. I remember several generations of 3- and 486es, and a couple of Athlons, all running fine in the same main boards as their predecessors, and often more than one upgrade. I have always been assembling my machines myself, and I have always hated when I had to upgrade the main boards... and still do.

As such, I agree, "until" 2025 is rather short. If you read it critically, that covers two years. Barely enough for one end-of-life upgrade.

I'm old enough to remember building my own AMD Athlon 64 3000+ machine, does that count? :tongue:

64-bit support with Linux at the time, and an almost non-exist windows 64-bit. :grin: The Good ol' days!

View this comment - View article - View full comments

Quoting: scyto

Quoting: Kohrias

Quoting: BlackBloodRumYou 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 [External Link].

I checked that link and it seems to be the same as the publisher details on flathub - am i missing something?

Sorry, that's on me!

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.

View this comment - View article - View full comments

Quoting: WayneJetSki

Quoting: CyborgZetaBut do they have Pluton?

What is Pluton?

Something you don't want on your computer, depending on where you sit regarding user freedom.

In simple terms, it's a DRM chip inside the CPU that Microsoft & AMD designed that is similar to those found in the modern Xbox and has the potential to reign complete control over your computer and is cloud connected. For example it can submit documents to the cloud for "attestation" and "verify" that the OS isn't tampered or running pirated software. It can also receive updates from Microsoft via Windows Update and you have absolutely no control over it or say in what it may or may not do. It's great for companies like Epic and their EAC though who wish to have more control over you and your games, it's a wet dream for them.

Sadly, not all details are known about it as Microsoft are keeping their cards close to their chest regarding the full details of how it works.

The more worrying thing isn't so much the potential of "what can it do" but rather why are certain manufacturers, such as Dell & Lenovo rejecting it? They are claiming they will ship it disabled and inactive. So you have to ask yourself why would they, being companies that are fully in the pocket of Microsoft, chose to go against Microsoft like that? What do they know?

Sadly, I am biased against it as I do not support it so I am probably not the best person to explain it. I want gaming to be successful on Linux, but not at the cost of compromising my freedom to use my computer as I wish or to give up my privacy. I simply can't support such a technology.

View this comment - View article - View full comments

Will these ones contain the Pluton backdoor?

View this comment - View article - View full comments

Quoting: theCrowI'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!

Quoting: BumadarWhen 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 :huh:

Does the same thing happen with other drives? Eg, if you install onto sdb instead of sda/nvme any problems?

View this comment - View article - View full comments

Quoting: BumadarWon'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?

View this comment - View article - View full comments

They do this, a few days after I struggled with the old UI to finally get my Desktop controls just right and to my liking.. my luck right there. :grin:

View this comment - View article - View full comments

Quoting: Termy

Quoting: BlackBloodRumJust be sure to check which permissions you're granting, because you could end up granting full system access

yeah, thats something i always missed on flathub - no easy way to see beforehand what is requested. Flatseal is a nice tool to get an overview. And regarding Lutris: by default it is granted full home dir access - don't know why they would do something like that tbh...

If you install via command line, flatpak will show you the permissions every time. But be aware application updates can request additional permissions to what you have previously reviewed, again if using the flatpak command it will present those additional permissions to you before proceeding. I'm not sure how UI's handle this such as discover in KDE since I've always just used the command (I know I'm weird :tongue:).

As for lutris's home directory access request, I think that's intended to make things easier for an end user. I mean, if it was confined to only its own local files (full lockdown) then it would be difficult for an average user to load in extra games like emulated Atari games and such since most people will probably have those downloaded and saved into another directory somewhere else (such as ~/Games\ for\ Atari) and to keep the sandbox in that case the files would have to be copied or moved into lutris's sandbox directory.

Good luck explaining all that to a new Steam Deck user who just wants to play their game and has no prior knowledge of Linux. So in that case it's far easier to just allow home directory access and let the user go pick the file he wants as normal.

In addition probably also trying to maintain consistency with the non-flatpak version.

Quoting: BumadarNo, I used the version in the tumbleweed repo. It's not that the nfs share is not available, just the gog installer, so might be a wine issue seeing the nfs as network drive.

Odd issue, but unlikely to be because of the filesystem being NFS (Assuming it has read/write permissions?). When Linux mounts an NFS partition, that's all handled by the kernel and mounting tools. Beyond that any other application (such as wine) just sees it as a regular directory on the computer the same as any other.

Try to see if you can get more info by running the following command:

 
lutris --debug

Try to install your game again but watch the terminal window, it might spit some other errors out which might better paint a picture of the problem.

View this comment - View article - View full comments