okay, 336 then. it shouldn’t be a bios version issue at least.
okay, 336 then. it shouldn’t be a bios version issue at least.
Ti was going to ask if it's the
-ally-deckbut it probably is
Tdamn i dont own an ally to test this myself :/ this is a bizarre issue
Sso what bios should i use? i think its not the bios problem
Tand this is a new install?
Adamn that boot animation is fancy af
Sya fresh install
Khow did you set up your user?
Snormal like installing fedora
Tuser password?
Kso no root account, and one user w/ administrator access and a password?
Sya i use password
Sbtw whats the different between graphic mode and none?
Si choose d clasic graphic
Kjust how the installer behaves, that's fine
Sso is there any fix?
Tanyone got waydroid working in gamemode?
TI've got it launching normally through desktop mode but no dice with game mode
Kcat /etc/sddm.conf.d/steamos.conf | fpastecan get to a terminal with control+alt+f4
Sdamn i already try to reinstalling it lol
Si'll try when i got that bug again
Swhen i try to nano the gdm custom.conf before, it said theres no directory
Kdeck builds don't use gdm at this time, all sddm
Saahh i see, even it use gnome?
Kyes
Scool
Twhen you first installed, it booted GNOME the first time to go through the Bazzite Portal right?
Tand after you did the portal, logged in to steam, and rebooted, it went to game mode, but then you couldnt switch back to desktop mode
Syap thats happen
Safter fresh reinstalling, its still happen
T@semakusut follow this
Tso there's some kind of log for the project
Salready
Sit sayd uploaded
Kgive us the URL
SSi think the gamescope session name is wrong
Sit should gamescope-session-steam
KAre you making any changes what so ever? chsh or anything like that?
Snope
Kgamescope-session is correct
Kyou wouldn't make it to gamemode if it wasn't
Si use nobara before, and got trouble like this to
Sgnome nobara
Sstil use gdm
Sthe naming of gamescope-session is different from the nobara 38, its changed to gamescope-session-steam.desktop
Ksounds like something upstream then, the loop you're seeing is GNOME's session failing to start
Kwhich then falls back to gamescope-session
