Word to the unwise and the terribly unprogrammed; don’t change permissions on your deck
Long story short, I did something dumb like;
sudo su (Password) chown deck -r /
Don’t do it
Just
Don’t
You’ll change who owns Sudo And if 0 doesn’t own Sudo
Nobody does
Out of curiosity, what were you trying to accomplish by running that command? I’ve been a daily Linux user for about 4 years and I’m having some trouble figuring out any reason your user account could need to own the entire filesystem.
To be real chief, I was trying to circumvent “most” permissions by doing said thing. I wanted to drag and drop freely wherever I wanted.
(I was trying to add Krita shit to pykrita)
Turns out, no, you don’t and should not own the entire file system.
Oh you sweet summer child. You wanted chmod 777 still don’t recommend but it will do what you want v
you could just allow root-login, set a root password and login as root. But please dont do that. The same goes for adding your user to the root group.
I mean sure, someone who runs that command shouldn’t permanently be logged in as root, but from a security standpoint it doesn’t really matter on a steamdeck. Doesn’t have any protection if someone else gets their hands on it anyways.
Why not just add the arch repos or use other distro like Nobara
I’m actually going to try Nobara today and see how it goes
If you have any problems you can ask me or in the official discord of Nobara
If you didn’t understand the steam OS very well you’re asking for trouble switching out of it… It’s pretty tailored to the deck
Maybe they thought they could avoid using sudo on system files by owning them?