Update Gamescope? (Super Key "stuck")
Running Bazzite Stable (41.20250106.3) on my Desktop, and I am having weird issues with gamescope. The 'super' key is acting like its stuck engaged so certain keys (so happen to overlap with shortcut keys of gamescope) dont work.
S, F, B and N to name a few.
This appears to been fixed in Gamescope 3.16.2 (via PR 1666), but I am running 3.15.9. Theres no updates pending via topgrade. A workaround is toggling numlock, but this feels like a silly workaround to fix it.
How can I manually update Gamescope on Bazzite?25 Replies
I'm afraid you can't manually update, and we're in a position of not updating to this version anytime soon
It has issues that cause numerous games to crash
Every game that I depend on gamescope commands for is now broken, I need PR1666 and I don't have a keyboard with numlock.
I agree, gamescope should be updated asap, every game on my system using gamescope is broken
IIRC @matt_schwartz mentioned elsewhere if you dont care about HDR then you can use
--backend sdl to hopefully workaround the issue
update gamescope --> numerous games crash now instead
sounds like a good plan ya? 🤦apparently that doesn’t work with your Gamescope version either unfortunately
F, thanks for mentioning
This crash problem is Fedora/Bazzite related?
gamescope related
afaik
Every distro is affected?
no it’s Fedora, antheas has already said it works if you build it on arch and then transfer the binary
Nobara is also broken in the same way
and Fedora likely will be as well when they finally rebase to 3.16
so until one of the three figures it out, upgrading Gamescope is a no go
I tried antheas’ 3.16 rebase on arch and it worked fine
Damn, is by any chance only happening on wayland? Or x11 works fine?
x11 probably doesn’t work with your Gamescope version either if the SDL backend is not working like someone else said earlier
best bet is probably to rebase to an earlier bazzite image if you weren’t affected by the issue before a certain point
Yea this issue started happening some days ago
Welp, gonna wait then, thanks for the info
this is why we got rollbacks and rebasing for 🙂
i had to stay on bazzite 39 for the longest time because gamescope broke on polaris cards and while we worked to get a workaround going everyone who was affected had to be on 39
I see, i will keep following this issue, thanks for the advice!
just to be clear the SDL backend not working might simply be my system, I recall it not working a while ago and I think it is one of the rare times having an A770 caused something sorta major in breakage
What version would I rollback to?
check the changelogs https://github.com/ublue-os/bazzite/releases
sadly no 1:1 version numbers since our gamescope is built from specific gamescope commits
GitHub
Releases · ublue-os/bazzite
Bazzite is a cloud native image built upon Fedora Atomic Desktops that brings the best of Linux gaming to all of your devices - including your favorite handheld. - ublue-os/bazzite
or you can do the sensible thing and just try rebase back 1 month or something
and nudge forward or back more
I ahven't had to rebase on the system yet before, what do I do for that?
brh
use thatThats it?
yes
Okay, How do i go back like exactly a month lol
sorry just researching this
read the helptext of
brh
then brh list
then i am sure you can figure out the rest