Package Details: gamescope-session-git r231.127f432-1

Git Clone URL: https://aur.archlinux.org/gamescope-session-git.git (read-only, click to copy)
Package Base: gamescope-session-git
Description: Common gamescope session files
Upstream URL: https://github.com/ChimeraOS/gamescope-session
Keywords: chimera chimeraos gamescope steam
Licenses: MIT
Submitter: Samsagax
Maintainer: Samsagax (ruineka, pastaq, alkazar)
Last Packager: alkazar
Votes: 4
Popularity: 0.000472
First Submitted: 2021-05-03 14:53 (UTC)
Last Updated: 2024-05-01 12:01 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

wustdsh commented on 2023-10-20 11:47 (UTC) (edited on 2023-10-20 11:55 (UTC) by wustdsh)

Whether booting from a terminal or sddm, nothing happens. Two "Steam Big Picture (Wayland)" are displayed in sddm. I'm a bit confused, also I'm using plasma (wayland)

× gamescope-session-plus@steam.service - Gamescope Session Plus
     Loaded: loaded (/usr/lib/systemd/user/gamescope-session-plus@.service; static)
     Active: failed (Result: exit-code) since Thu 2023-10-19 12:53:20 CST; 19min ago
   Duration: 3.027s
    Process: 8864 ExecStart=/usr/share/gamescope-session-plus/gamescope-session-plus steam (code=exited, status=1/FAILURE)
   Main PID: 8864 (code=exited, status=1/FAILURE)
        CPU: 39ms

10月 19 12:53:17 ArchlinuxFly systemd[5927]: Started Gamescope Session Plus.
10月 19 12:53:20 ArchlinuxFly systemd[5927]: gamescope-session-plus@steam.service: Main process exited, code=exited, status=1/FAILURE
10月 19 12:53:20 ArchlinuxFly systemd[5927]: gamescope-session-plus@steam.service: Failed with result 'exit-code'.

LukeShortCloud commented on 2023-10-17 03:28 (UTC) (edited on 2023-10-17 03:29 (UTC) by LukeShortCloud)

Hey @rlriueab , thanks for reporting your issue! These two PKGBUILDs (gamescope-session-git and gamescope-session-steam-git) and the related git repositories went through a major restructuring this past 24 hours. I can confirm that installing gamescope-session-git and gamescope-session-steam-git are working now. Be sure to clear any build cache you may have and fetch the latest sources.

The fonts can still be found in the gamescope-session-steam-git package. It is to workaround Steam Big Picture Mode issues on first launch: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=gamescope-session-steam-git#n31

rlriueab commented on 2023-10-16 14:51 (UTC)

Why does it contain DejaVuSans.ttf?

$ paru -Ql gamescope-session-git
...
gamescope-session-git /usr/share/
gamescope-session-git /usr/share/fonts/
gamescope-session-git /usr/share/fonts/truetype/
gamescope-session-git /usr/share/fonts/truetype/ttf-dejavu/
gamescope-session-git /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf
...

And it conflicts with gamescope-session-steam-git

theriddick commented on 2023-09-21 02:27 (UTC) (edited on 2023-09-21 02:58 (UTC) by theriddick)

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.

parkerlreed commented on 2023-09-18 22:03 (UTC) (edited on 2023-09-18 22:16 (UTC) by parkerlreed)

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.

murrant commented on 2023-09-13 13:02 (UTC)

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

flxrbr commented on 2023-08-01 02:37 (UTC)

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.

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.