Is there a way to put a password on before you can use it like on windows 10
Is there a way to put a password on before you can use it like on windows 10
CI'm just wandering as I don't want people going on it when I'm out
©Only if your UEFI-BIOS supports booting from the SDCard...
Zas far as I know, the deck's fw supports it
©can try, but i doubt it... SDCards are normally considered removable drives
©Which you can select to boot from using the UEFI-Boot menu, but they won't stick
©But it's worth to try
Ianyone here knows how to disable grub
©Why? it's your bootloader
©AFAIK, Bazzite, as-is, doesn't support any other bootloader
©Good moaning to all those on same half of the globe as me 
Zgm! :)
Zoh i don't really mind it not sticking
Zi just want to try bazzite out
©Try and see, if it won't run from SDCard, try an USB-Stick
Iso i installed refind set it up nice and everything and now after i choose to boot to bazzite the grub bootloader appears and i gotta wait 60 secs to boot
©It needs
Grub due to ostree way of working...©But im sure you can change the timeout...
Iyeah thats what im looking into right now
©it's some setting in
/etc/default/grub if they use standard configsIok
©then regenerate the initrd, using the commands for ostree/bazzite
©it's some
ujustgot it
©gl
Ithanks
©I'm sure you will like it though, i do at least on desktop
Hyour
and if you have a
.bashrccp /etc/skel/.bashrc ~/.bashrcand if you have a
.bashrc.d folder in your $HOME rename that temporarily so you can figure out where it breaks
GThanks, that fixed the broken prompt, though I still get no MOTD anymore
DI have an error log at #Gamescope frequently crashes on boot any idea for what I can do?
Htry toggle it again, if not then kyle who made the motd might need to help you
Gyep still nothing. Will have to wait on Kyle then
T-deck
BAre you able to get to a tty or desktop mode? For me (who has the same issue) I can still navigate game mode even though I can't see it. So I press steam button on my deck, then dpad up, then A button, then d-pad down 4 times, then A button again. That boots me to desktop mode
BIf you have a keyboard Ctrl+alt+f4 should take you to a tty
Dyeah it is hit and miss sometimes. why such a complicated key combo?
Dfor the controlls not keyboard
BIt navigates the menu to select "switch to desktop mode"
BFrom a tty entering
steamos-session-select plasma should take you to desktop modeDI can't access tty. I have the blinking
_ issueBYeah I couldn't get to one either just now, thankfully blind navigation with the controls still works. I ran rpm-ostree upgrade but issue still remains
DI made a post for it here #Gamescope frequently crashes on boot
BYeah there's also this. https://github.com/ublue-os/bazzite/issues/771
Unfortunately until a dev can reproduce this issue themselves we may be a bit stuck.
Unfortunately until a dev can reproduce this issue themselves we may be a bit stuck.
GitHub
Describe the bug The system will boot into one of two states: Black screen with a single white "_" (underscore) character in the top left. Other TTYs cannot be accessed in this state -- a...
DI have logs in there
B@PipPaine @Alex&Indie did you find a workaround to your broken gamescope issue? Rollbacks, upgrades, rebasing to earlier versions that worked before I did
rpm-ostree upgrade all still have black screen gamescope on boot so I'm thinking it must be either something in the kernel, bios or home folder that has changed to cause it to persist throughout
Amy deck is on pause, i dont have time to deal with it, gonna make a fresh bazzite install in these days
BOkay thanks, I'm trying to avoid that myself. It's my main computer.
It does seem the "return to game mode" .desktop file does launch game mode successfully at least
It does seem the "return to game mode" .desktop file does launch game mode successfully at least
GFWIW, I had the exact same problem Geechan described after the most recent update, except unlike them, in my case running
cp /etc/skel/.bashrc ~/.bashrc fully fixed the issue, with MOTD showing up correctly. At least in my case, the issue was that ~/.bashrc just didn't exist at all - which is weird because prior to the update everything was working fine, which implies the file originally existed, so I'm not sure what could have caused it to disappear. Anyway, hope this info is of some use for debugging!
Dwhy would there need to be a fresh reinstall for an immutable os? I can see why you want ~/ to be refreshed but the core system is immutable
T@dnkmmr @Alex&Indie @BearFOX did you use the
ujust-deck
Dwhat is the default?
