I mean to be fair I'm only forking here so I can maintain my own copr type stuff to get xwayland fractional scaling going under gnome. Basically just forking ubluestaging and fiddling with those two patches
like ideally I just want to keep things in sync with mutter stable and then apply the required patches and autobuild every time mutter stable has an update commit etc
(also this gives me a way to tinker with the patches a bit myself if I want to experiment and see what I can debug etc) but yeah I gotta figure out how to uh... set all this gumf up first lmfaoooo
but it's a bit of a pain to setup currently so I just kinda wanna make an easier copr for ublue/bazzite users who want to try and turn that stuff on just in case
does anyone have an idea of what this error is? seems to happen for some games but not others. so far sf6 demo and tekken 8 demo, but other games have been able to run just fine
@Kyle Gospo Gonna fork off the xwayland patches and stuff specifically into their own copr for GNOME targeted for usage in Bazzite etc for those who want to use that stuff, basically just going to be following ubluestaging to a T except the xwayland scaling patch is on, will let me keep up with testing some of that stuff and also give people an option to turn that on if the want to try it out in this current state where it isn't QUITE there yet (also for personally experimenting a little with the patches)
I just wanna try and keep both the xwayland fractional patch in there but I wanna keep that in sync with the mutter changes bazzite is pushing in for consistency and testing etc and also give other people the option to try it out easily if they want to because it seems very machine dependent at the moment
I just did a fresh install of bazzite-deck on a steam deck, and I couldn't get wifi to work on the first boot. Rebooting and then it starting in gaming mode let steam do the wifi things and everything was fine, but not having the first desktop boot work was kinda annoying
https://gitlab.gnome.org/GNOME/mutter/-/issues/3451 also want to note that this is something I've been running into in general as well and is seemingly being worked on in mutter. The best workaround I've found for it is running stuff in gamescope where possible