i think the only way you can get around this is by connecting to open wifi and not setting a user/ro
i think the only way you can get around this is by connecting to open wifi and not setting a user/root password (if that even works)
Tusername also needs to be inputted
Tso i dont think you can
VI don't have a keyboard I can connect to the deck
Tsomeone used krfb + krdc somehow on the installer with a wireless keyboard or something. i dont know how they did this at all though
Tdont know the details on how they managed to connect to the installer and i never attempted something like that myself
Tit was someone in the steam deck discord, here's the link to that conversation since you're in there.
https://discord.com/channels/865611969661632521/866460709733924884/1174153610796482630
https://discord.com/channels/865611969661632521/866460709733924884/1174153610796482630
Tif you can figure this out and get more details on it, then maybe later ill edit the documentation if it's not too bad of a workaround for those with wireless keyboards only
Phow should vortex or modorganizer be run?
Tyou can still try, but vortex is finicky, and I don't actually use it to know what is a current best practice
Twhat I suggest is setting your proton version to run them to be either proton 7 or 8 or GE, then running them with the commandline
steamtinkerlaunch mo2 startsteamtinkerlaunch vortex startvortex requires dotnet48 which sucks to install. it takes forever
NAnyone run into an issue with steam upgrading from 38 - 39 of Bazzite? The built in steam shortcut does not open any of my already installed games. And it doesn't detect my PS4 controller either.
NI was able to work around this by re-exporting my steam that is installed inside bazzite-arch distrobox.
Tsteam is layered in now
Kshouldn't cause any issues with launching games though
K@dogphilosopher can you change your launch options to
PROTON_LOG=1 %command%and try launching it?
KIt'll make a log in your home directory that you can share
Nyeah, I'll give that a try.
NDoesn't seem to be outputting the log file..
Tit should be at
~/steam-<appID>.logSet launch options here right?
N
Tyes
Nno dice
NThis is what happens.
NI've tried uninstalling and reinstalling my games and that hasn't done it either.
NI'm wondering maybe it's a permissions issue? I have my games saved on a separate disk.
Twhat file system is that disk?
Kyes
Tpermissions aren't too much of an issue when you are not using a flatpak
Next4
Npermissions look right for my user account anyway.
Kafter adding that do you have a log file in home?
Nnope.
Kok, it's not even starting proton then
Knext thing to try, close steam entirely
Kopen a terminal
K/usr/bin/bazzite-steamKand then try launching a game
Kand give the terminal output
Nmessage.txt20.54KB
KKtried to run proton
KKand this is the only thing that stands out
Kcan you validate your game files on that title real quick?
Nsure!
Njust so you are aware, this same behavior is happening for all my proton based games. I haven't tried installing a native game.
