Package Details: gamescope-session-git r89.dfef341-1

Git Clone URL: (read-only, click to copy)
Package Base: gamescope-session-git
Description: Steam Big Picture Mode session based on gamescope for ChimeraOS
Upstream URL:
Keywords: chimera chimeraos gamescope steam
Licenses: WTFPL
Submitter: Samsagax
Maintainer: Samsagax
Last Packager: Samsagax
Votes: 1
Popularity: 0.000011
First Submitted: 2021-05-03 14:53 (UTC)
Last Updated: 2023-01-08 13:34 (UTC)

Dependencies (4)

Required by (0)

Sources (1)

Latest Comments

edtoml commented on 2023-02-09 15:17 (UTC)

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 :-/ )

Samsagax commented on 2023-02-09 14:28 (UTC)

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.

edtoml commented on 2023-02-09 02:00 (UTC) (edited on 2023-02-09 02:00 (UTC) by edtoml)

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?

edtoml commented on 2023-02-09 00:56 (UTC)

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...

edtoml commented on 2023-02-09 00:09 (UTC)

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?

edtoml commented on 2023-02-09 00:06 (UTC)

lib32-libnm-1.40.12-1 is installed here. Is this a 32 bit part of networkmanager? If so then it may be that I use systemd-networkd to setup eth0, not networkmanager.

Samsagax commented on 2023-02-08 23:09 (UTC)

Probably you don't have lib32-libnm. Is not required by the session but steam client lists it as a optional dependency (in their jupiter flavor).

As for the session script I would recommend against modifying it directly. If you want to override the GAMESCOPECMD environment variable to acchieve the same result. Take a look at the Readme for the session.

edtoml commented on 2023-02-08 22:51 (UTC)

I am able to get a steam session using this, but it does NOT recognize my wired ethernet connection. I have things setup so sddm start the session, while sddm is active, I can switch consoles and have used this to verify that systemd.networkd has setup my network correctly. There is no wifi connection on this PC.

PS. I also had to modify the gamescope-session-script's gamescope -O option to select the correct display (I have two, one DP 1140p, and HDMI 1080p), using the names from the drminfo command.