if you haven't been to gamemode before, that's the welcome screen for gamemode
if you haven't been to gamemode before, that's the welcome screen for gamemode
Kyou're good
Ksteam is kind of it's own thing
Kthat whole UI is steam
Kso first boot it'll act like you've never turned the device on
Ksettings like language and all that are separate from your DE
Kso it's not really something to fix
Kjust how it works
EI was thrown off by that at the first time. I was like, didn't I just download and log into steam and pick my language and timezone and stuff. Why do I do it twice and wait for 19 minutes for who knows what to download re: steam
K@RoyalOughtness that switcheroo patch is live
Kon stable
Kalso applies to gamemode, so anyone w/ a laptop should automatically get steam running on their dgpu
Nrebased back to stable and the issue is back
I hope it's not one of my custom layers causing that
I hope it's not one of my custom layers causing that
Kwhat have you layered?
BIs there anyway to change this mountpoint? probably not
Kgnome thing, should have a shorter name but nautilus uses the longer one
Kif anyone wants to look into this I'd appreciate it 
Kworks fine in KDE
Hshould be enough to name the partition or put a label on it 
Khas a label
Nis there a command to view what I layered? I may have forgotten what I installed
Ei downloaded simple application launcher and the problem is gone, it happens on wayland btw, but only on the default launchers that come with plasma
Krpm-ostree statusseems to not be the primary disk though
Nautoconf automake libtool libusb libusb-compat-0.1 pcsc-tools strace
NI also have sunshine installed
Knothing there stands out to me
Kours is patched w/ the BTRFS patch set
Kand a minor patch to make it work with users other than deck
Kbut is otherwise this
BCool, it had random steam deck update notifications so I wasn't sure lol
Kyes it is
BWhy did I edit lmao
Kfeel free to ignore those as often as you want
Kofc
Ncan I do something to debug this
Kwell, just in case, you can try killing the joystickawake process
Kother than that there's really been no changes in the last week
Kwould have to find a way to determine what processes are watching that input device
AYeah I saw a comment that the thing blinks too much
AMaybe bring back testing now that things are becoming stable?
AWeekly release perhaps?
Ktesting is for sure being used, right now builds are every other day but I may slow that down. Last time we did we got a lot of "where are the updates?" comments so it goes both ways lol
Nit worked
Nthe issue is gone
Khmmmm
Kok, let me work around that
KI appreciate it
Kno idea why I'm not getting that behavior but the deck doesn't really need it
