Aahah, so it's not running properly
Athat would explain the controller issue
Awhat happens when you click refresh?
Anothing?
A
Athis is what it should look like when it's working
FI cant 
FWhen is press
FI have only 2 blinks and 3
FNot 1
FOhh
FOkey
FWTF
F
Kif you're finally in xinput mode you probably want to restart before testing
FOkey, i will check
FNothing, i install again
FHhd
Khhd is preinstalled
Kif you are manually installing hhd, that could be the source of your issue
FOkey, i reinstall the os
Hyo
HI can't get the keyboard to work on the Bazzite install
Hcan I just go rootless
Hand enable root later
Hwait shit that doesn't help with
Hmaking a user account
Hokay how do I convince a keyboard to work when it doesn't want to
Kyou plugged one in?
Kno touch keyboard in the installer (yet)
Hyup
Kif this is with a deck it may be that your keyboard needs more power than it has on offer, try a powered USB hub or a dock
Hboard is Akko World Tour Tokyo through USB-C
HI did, still didn't work
Konly other option then is to try a stock fedora kinoite/silverblue installer and see if it works any better for you
Kyou can rebase to bazzite from there
A@Aru out of curiousity, if youve messed with game emulation on legion go and bazzite, have you ever had an emulate refuse to map D pad inputs for you? I am in dualsense edge mode and specifically the dpad doesnt work for mGBA etc..
Ahrm, i have never had it happen before, but I can test in a bit. is this mGBA standalone? or mGBA retroarch core?
AI believe mGBA standalone/(whatever emudeck installed)
Aemudeck defaults to retroarch, i think
Aunless you explicitly enabled standalone
Aanyways, retroarch is kinda odd because it actually ships it's own separate controller configs
Ait could be related to the issue you're seeing
Alet me try testing gba in a bit
M@Kyle Gospo got a cross-distro bug to flag for you. Seems like touchscreen input is not being interpreted correctly on non-deck handhelds on both nobara and bazzite right now. It seems like the first touch input after launching a game works correctly, but after that point tapping the screen basically no longer acts like a touchscreen at all. Pulling out the steam menus from gamescope-session remain working, so it’s only in-game input.
M—force-external-panel or whatever the exact syntax for that is didn’t seem to make a difference
MIf I pull up Hades on both my OLED Deck and my ROG Ally, I can navigate the UI without issues on the Deck but touch input is only good for the first tap on Ally.
Ahrm, so on the LGO i can use multitouch with waydroid in gamescope-session