Arch Linux User Repository

WRONG screen even after setting up /.config/environment.d/gamescope-session.conf correctly. Required removing *,

Also logging in via SDDM does not work. Needs TTY gamescope-session method.

Games just load, but blackscreen is all I see. I think their being run on some hidden virtual window. Don't know why.

How do we use Mangohud with this? I have it installed but enabling the overlay isn't showing anything.

EDIT: lib32-mangohuds OPTIONAL glfw-x11 is required because gamescope uses mangoapp :( So much for the switch to all Wayland.

What are your thoughts on renaming the session? From "ChimeraOS (gamescope)" to "Steam (Big Picture)" or something else a little more descriptive?

The mouse cursor auto hides after a couple of seconds. I noticed when that occur, the FPS increases. When I move my mouse and the cursor shows up, the FPS drops and stay lower. Is there a way to fix this? Like using hardware cursor or something.

Thanks for your replies - they are really appreciated!

As to steam-native. Its been my experience that if something fails with steam-native, it will fail using steam. I've yet to come across something that works in steam but not steam-native. Which is surprising and a bit of a testament to the quality of Arch and Linux QA (maybe I am just lucky :-).

Agree with your assessment of my bluetooth issue. Mentioned it here since I figured others will probably encounter similar problems (I've previously gone through the arch bluetooth wiki, I'll look again :-/ )

Ok. One by one of your concerns. I would prefer the discussion to be made on the git repo for better tracking, but here we go:

Would you know if anyone is using it to start steam-native instead of steam?

I don't know. Maybe it will work, maybe it won't, use STEAMCMD environment variable to override the steam command and thuss its options and let me know. I would expect it to break more often as the client is made on the premise it will run on its own runtime.

Is there any place I can automate this when gamescope is starting?

This is completely unrelated to Gamescope itself. Is just a compositor and this session only uses it to run steam like the SteamDeck would (in a more general way). You can automate those things using systemd, but consider reading the Bluetooth article on the ArchWiki on those issues and troubleshooting. The most simple solution I can think of is a one-shot systemd user unit launched at login that runs your script.

Looks like my bluetooth device ends up soft blocked. So to power it on it needs

rfkill unbock Bluetooth; bluetoothctl power on

Is there any place I can automate this when gamescope is starting?

Once I changed things to use networkmanager to start my connection it recognizes the wired connection. Thanks for the pointer.

Bluetooth is not working correctly though I do not think is your problem. Looks like a recent update broke bluetooth here in that bluetoothctl power on now longer works. Interestingly kde has no problem powering on the adapter...

I'd seen the example using .config/... Figured once I have the setup working I try that. Would you know if anyone is using it to start steam-native instead of steam?