updating through gamemode runs `ujust update`
updating through gamemode runs
ujust update
Awhich will be addressed via the upcoming changes in testing
Jinteresting
Hand its a slow process
Jfor me nobara was the worst on the ally
Hthe progressbar is just a 15min countdown or something
Jits easily the most finicky
Hif it finishes before 15 mins it jumps to 100%
Jbecause unlike bazzite it doesn't have a preconfigured image with the fixes installed
XOh @Aru do you have the Z1 or the Z1X?
Anobara is basically the only choice right now for the LGO, the others don't have the LGO fixes yet
ALGO only has a Z1E, i think
Jlego
XOn your ally
J
Jidk if they have an ally
Aally? i don't have one lol
XOh
XI brain
XSorry
Alol no worries
Abut I think part of the reason why the ally could have a preconfigured image is because it's been out for a while now. and it's only within the past month or so where the Ally got basically full hardware support.
ALGO came out barely 2 months ago, and basically already has full support for it's hardware
AI hear the Ally was a royal pain to deal with on Linux
Jally just has a lot of issues, its easier to address them with an image designed specifically for it
Jwith nobara yes and chimera to an extent
Jbazzite is definitely the easiest to work with
Abazzite will be the easiest for the LGO too, once it ships hhd by default 
H1 week 
Aright now the biggest pain point for bazzite on the LGO is getting hhd working
K1 week from now
Aeverything else on Bazzite is better than Nobara in terms of out-of-box experience
Jaru do you know how I can remap the back buttons using hhd
Abut hhd basically is the only reason why I haven't recommended bazzite to others yet
KThat gives us time to further warn people using secure boot
KAnd write up documentation for the change
Aonce hhd is working, you should be able to just use steam input
JI don't think it works with the ally
Jbut that means I would have to map it per game
Jman that sucks
KIt didn't on testing until today
Aoh, you want global? 
JYeah
Jbecause its already mapped to some bs
Alook up steam deck steam input global config, maybe there's someone who tried
Aah yeah, the preconfigured mappings
Asteam for some reason defaults them when in steam ui
Aapparently the actual real controller does the same
A¯\_(ツ)_/¯
KProbably a safety thing
Jthe back buttons are mapped to touching specific parts of the touchpad
