#Steam flatpak not launching

1 messages · Page 1 of 1 (latest)

low sentinel
#

try removing hardened_malloc

#

hm

kind flame
#

you didnt run the permission lockdown ujust right?

#

afaia no, could you screenshot your steam permissions?

low sentinel
#

wait

#

resetting the permissions resets them to the overrides in the file i believe

#

you should check the steam permissions against the manifest to double check

kind flame
low sentinel
#

after i run the flatpak override ujust, and then i click reset

#

it resets it to the state set by the override ujust

kind flame
#

do you hit reset in the app or global?

low sentinel
#

app

#

i thought that was the expected behavior

kind flame
#

that is, yeah

low sentinel
#

ah nvm

kind flame
#

they reset it in both

#

this is exactly what I have

#

except for the portals

#

and it didnt launch without flatpak lockdown?

#

didnt you try doing a global app reset?

#

odd... the reset through flatseal should work

#

weird...

kind flame
#

Its probably power managment

signal summit
#

These settings are currently working for me:

#

These are more restrictive than you might want, but games work. Tested today by successfully launching Dark Souls III under GE-Proton9-27

kind flame
#

did you try enabling devel?

signal summit
#

That will require devel as well

#

Do you know if Helldivers 2 works with this configuration, perchance?

#

All good. Just wondered. I refunded the thing right after switching to Linux because anticheat didn't work but I think that was user error because I didn't know how ptrace scope and such worked yet.

#

It should be exactly the same as overwatch

signal summit
#

Some games just are. It really varies. Try GE-Proton if you haven't already.

#

Glorious Eggroll. Somebody who improved Valve's Proton a bit for use on systems other than the Steam Deck.

#

Hang on...

#

Oh good! Looks like there's a new version out. I think Wine 10 fully supports Wayland (although Steam still doesn't. 🫠 )

#

I did not.

#

I used the normal one, ran the checksum, and stuffed it in the steam folder.

#

The flatpak maintainer is an unnecessary trusted party.

#

Probably fine, but not what I prefer.

hexed raven
#

For anyone who comes across this thread in the future:

  1. My issue was that I had run ujust flatpak-permissions-lockdown before I installed the Steam Flatpak via ujust install-steam. Resetting the permissions through Flatseal didn't work, so I had to use ujust flatpak-reset-global-overrides to get Steam working again.
  2. Once reset, I just noted down the output of flatpak info --show-permissions com.valvesoftware.Steam, then I ran the Flatpak lockdown script again. I then went through adding all of Steam's permissions back, using Flatseal.

For Overwatch specifically:

  1. I had to ujust toggle-anticheat-support to on to get the game to launch.
  2. For stutterring issues, I switched to Proton Experimental and set these launch options: __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 __GL_SHADER_DISK_CACHE=1 DXVK_HUD=compiler LD_PRELOAD="" %command%
  3. I disabled shader pre-caching from Steam settings.
  4. I switched to using DirectX 12 through the graphics settings in-game.

End result: Steam works, Overwatch launches, and only minor stutters for the first 10-15 minutes or so, before becoming mostly smooth.

tired brook
#

Following along, I tried to set Flatseal as per ValiantMaverick's, but Portals/Background isn't even a thing I can toggle? I assume that is a hint at what's broken. I do wish it would give me meaningful error messages.

signal summit
#

Portals is the section at the bottom. Background is the first item in that section.

#

Some portals may be greyed out (I think because the flatpak doesn't request them), but Background should not be.

#

If your system isn't in English, it may be called something else. 🤷‍♂️

signal summit