Replacing Win10 at home for 3 users with Bazzite
Hello π I just got a Bazzite install up and running (after having to nuke a previous one for misconfiguring the SSD, which was still trying to boot into Windows; oops) and I thought I would have multiple Linux users (like I did Windows users prior) but even after adding them, I don't get a login screen.
Then I found SDDM and where to uncheck the automatic login for my user, but when I hit apply and enter my admin password, it just rechecks itself. I read somewhere that this may be due to the OS being immutable? But, if that's the case, do I need to do a fresh install and setup all the users at that stage? Or is there an easy option I'm missing because I've only been staring at Linux through the shop window for a few decades and have only just walked through the door?
Thank you in advance for any help!

31 Replies
strange
but it shouldn't have anything to do with the OS being immutable
as the settings themselves are normally stored in a mutable tocation
specifically /etc
there'so such thing as a registry in Linux most settings files are text files
the file for sddm is a simple INI file
Solution
-deck
images only support a single userGame mode limitation, multiple users are handled through Steam logins
Desktop images should work fine
yeah i did think so
i guess return to desktop mode wouldn't work with more users maybe
I just discovered a command that shows which image I used and it was a deck image. Then, checking the download page and my graphics card (R9) it suggested to not use a deck image but rather a desktop one. I'm going to just do a fresh install at this point and see if that gives me back the login screen.
Thanks!
You likely only need to rebase, but if it's a fresh install anyway
no need to reinstall
Oh?
Type in
bruh
in a terminal windowdue to how bazzite are designed the core OS is immutable
Ok π
this isn't a format c: trick for Linux n00bs, is it? π
No, it's Bazzite Rollback Helper
brh
also worksdue to tha all system files can be tracked by the update system
& since everything is tracked everything can & will be replaced when/if needed
that;s what happens when you update/rebase
Bazzite just handles OS updates through container images
a new system is created & set to be the default
You're changing the base system container variant, i.e. rebasing
on boot
your user files are OS interdependent
so they survive a rebase
@nagito || Knight of Emilia I think you're overcomplicating things a bit
I appreciate both of you for everything π₯°
yeah i like slightly detailed explanations
This isn't even correct though
You can layer things
ok managed is the correct term
people just commonly use immutable to mean managed
The term Fedora landed on is Atomic
Which is pretty apt
Every package manager manages the system, it's not descriptive of anything
I'm rebasing now... And if it gets b0rked, no worries, I'll just fresh install from the correct .iso
yeah but some of them manage files more strictly
such that they can't be easily manipulated indirectly
indirectly meaning by things other than the package manager itself
as that's not good for consistency/sanity
You can edit stuff in
/etc
, that's tracked by rpm-ostree
Only propagates forwardsnot really in the same way as system files
a variant of etc is in
/usr/etc
this is copied to /etc
on initial setup as i recallJust direct people to the Bazzite docs man, you don't need this jargon
Yes that's how rpm-ostree keeps tabs of what you've edited
It diffs the two
Anyhow, it's akin to buying a prefab house as opposed to say, 3D printing your walls. Both might not need you there, but one is shipped to you whole
Hope that makes sense @lightmanx5
& when you update you're essentially building a new one
with your furniture carried over
Not really, it's more like just moving your furniture to a new prefab
this helps ensure that things don't break in unpredictable ways
because all the important bits are new
which may happen when working on an existing building
another obvious benefit of this is that the old house still exists in it's exact original form if you don't like the new one
that part confuses me a bit as i come from Nix OS land where
/etc
isn't atomic or managed only individual files in it are managed
there isn't any sort of merge/diff process the managed files are just linked there at boot everything else is left as is