I'll check again when I get home later can you pin this comment for me or get someone to pin it so I
I'll check again when I get home later can you pin this comment for me or get someone to pin it so I can see it later?
Hi will just write in your thread
Dthe key difference between
/etc and /var is that each deployment has its own /etc so if you mess something up, you can just roll back.Dit has been 7 days since our last successful image build
Seh, better measure 10 times and cut 1
Dsteamos 4 should be based on ublue
GI saw the window on sway too
Tif I were to speculate, there's probably a 1px element that is normally hidden/out of view that is getting captured by the tiling managers
GWhy does it need to open a graphical Wayland client?
GOr does it try to open an xwindow
T
I've been out of the loop on stuff
IHi guys, does Bazzite have nvidia 545 drivers?
Dwhat is causing bazzite to fail at building images for a week?
KUpstream changes to glibc32
KVersion mismatch that ostree doesn't like
Dhopefully it will be fixed soon
KStill waiting on RPM fusion for that, it's almost ready
TTenor
Vwhy not kinoite though?
TIsn't kinoite also based on CoreOS?
Vfrom reddit, about Silverblue, but the point is the same:
Silverblue and CoreOS share quite a bit of technology (e.g. rpm-ostree) and ideology, but there are some major differences. Silverblue is designed for home / workstation use. The base image comes with Flatpak already set up, a full GNOME installation, etc. In a default install, you have podman for managing containers, which is like Docker but daemon-less and with a rootless mode.
CoreOS, on the other hand, is designed to be a host operating system for running containers on servers. The base image here is far more stark and minimal, and it also comes with Ignition which can be used to quickly configure large amounts of node servers. In addition, it contains multiple container runtimes out-of-the-box, adding Docker and CRI-O in addition to podman.
They do share the base concepts, such as ostree / rpm-ostree, the immutable rootfs, and atomic upgrades. Of course, you can still install normal rpms on both via rpm-ostree as well.
TAh right, now I get it.
Vkinoite/silverblue is more for home-use, while coreos is more for servers
Bdoes anyone have any experience with ASUS motherboards and the built-in ethernet + wifi just (literally) falling off a bus?
DIDK the packages are a wewk out of date since the image failed to build for a week
BIs there a list of flatpaks that come with the Gnome-Deck build? Rebased from KDE and kinda have a ton of KDE flatpaks installed
KGitHub
Bazzite is an OCI image that serves as an alternative operating system for the Steam Deck, and a ready-to-game SteamOS-like for desktop computers, living room home theater PCs, and numerous other h...
BAbsolutely a Hero, thank you!
Dwhat will we have to do to fix that?
KWait, it affects everyone including stock Silverblue/Kinoite, fixing it ourselves would be extremely messy
DI hope they will fix it. Could it also be on RPM Fusion's end too?
KNot in this case
Dmain is passing https://github.com/ublue-os/main/pkgs/container/silverblue-main
KMain doesn't install applications requiring 32bit libs
KSpin up a VM of main and try laying steam
Dmust be steam
Dwill try that
SI forgot my deck password for bazzite. How can I reset it?
KFedora Docs
A root password may be set up while installing Fedora Linux, although it is now suggested to leave the root account locked and use sudo. This article describes how to…
Mhow do I upgrade/rebase without uninstalling packages that can't be updated, that are third-party, basically?
M(if that's possible)
SI can't seem to get grub to show on boot.
SReason I am asking all of this. I made sure my deck was set to lastest with the os-tree command and now I am getting a login screen.
SI will make a help page.
Eujust unhide-grub should do it
EA normal update won't remove them. If you rebase or reset the tree, you'll have to reinstall them
Mso by normal update does that include the version upgrade (e.g. fedora 38 -> 39)?
Mbecause I couldn't get f39 with just a normal update and had to rebase
M
RIs there a way to get Bazzite to a sort of "factory" state with like, configs and packages without losing my personal files and flatpaks? Games, ROMs, etc?
