When launching a game via steam://run/..., Steam doesn't set the GAMESCOPECTRL_BASELAYER_APPID or GAMESCOPECTRL_BASELAYER_WINDOW on the root window.
When launching Steam and then launching a game manually via the UI, both of these are set:
> DISPLAY=:2 xprop -root GAMESCOPECTRL_BASELAYER_APPID GAMESCOPECTRL_BASELAYER_WINDOW
GAMESCOPECTRL_BASELAYER_APPID(CARDINAL) = 413091, 1368030, 769
GAMESCOPECTRL_BASELAYER_WINDOW(CARDINAL) = 0
So I guess there's a bug in Steam (we can't fix that 😢), but I wonder if gamescope should fall back when no window is tagged, or if there's some possible workaround here.
Nothing extracted yet.
Is there an existing issue for this?
Are you using any gamescope patches or a forked version of gamescope?
Current Behavior
If I run
gamescope -e steam steam://run/367520, no window renders (i.e.: not even gamescope), but after a while, I do hear music andps auxfshows gamescope, steam and the game running.Steps To Reproduce
Run
gamescope -e steam steam://run/367520. The game launches but no window is shown.Running
gamescope -e steamor evengamescope -e steam steam://open/bigpictureand then executing the game manually works fine.Hardware information
Software information
Which gamescope backends have the issue you are reporting?
Logging, screenshots, or anything else
https://gist.github.com/WhyNotHugo/238b8dd9d8f0bbc8f5c3653c8ea7a8b4#file-nowin-log