I'm sorry, could I please ask.for some help? I got everything right on my system besides being able to rebase with rollback helper. Whenever I type in the prompt to rebate with the 40-20240427 version it comes back with the error "remote error: cryptographic signature verification failed: invalid signature when validating asn.1 encoded signature" do I need to add a permission somewhere in terminal or should I be trying to access a different version? And if I need a different version, where would I find it/number to input?
Please disregard, after further research I realized you must pull from a release 90 days ago or sooner and found the recent release dates on the github to input. Thank you for this video, you really saved my new setup and my first dive into linux!
I see that you came right on your own, that's good news! Images are only supposed to be available for 90 days but it looks like the 20240427 edition is still available, typically you wouldn't want to go back to such an old version but you can if you want to. A few weeks back there was an issue with the Universal Blue signing key rotation, so a whole bunch of the originally signed images don't work with the new key. You should be able to use the following commands to rebase to the 20240427 edition because the "ostree-unverified-registry" will ignore the key and let you rebase (NB don't do this unless you really need to): AMD Deck image with KDE: rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:40-20240427 AMD Deck image with Gnome: rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck-gnome:40-20240427 AMD Desktop image with KDE: rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite:40-20240427 AMD Desktop image with Gnome: rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:40-20240427 Nvidia Desktop KDE: rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-nvidia:40-20240427 Nvidia Desktop Gnome: rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome-nvidia:40-20240427
Bazzite seems to be the worst among SteamOS clones that I have tried - Chimera, HoloISO etc. On a AMD Navi GPU I get gamescope black screen issues, something I have never faced in the others. On NVIDIA GPU too, the installer does not proceed beyond the grub menu; after adding kernel parmeter "noapic" it let me install (Anaconda installer is archaic compared to Calamares btw), but after first reboot, did not ever go to the desktop. It seems too many RU-vidrs are praising this which theoretically should be good like other (non-gamescope) atomics Aurora or Bluefin, but is actually a pile of ****. And the laziest troubleshooting documentation, where they simply point to Valve's Gamescope git issues page, expecting users to go through 500+ of them with comments! Even if they have only derived from Chimera's gamescope solution, Fedora does not seem to get gamescope right yet. Nobara is another PoS. Good that Valve chose Arch Linux as the base. Just waiting for Chimera to resolve their ever boring splash screen configuration updater and I will go back to it, the only drawback of Chimera for which I wanted to try Bazzite.
I hope that this video was helpful. Please let me know of any Bazzite or Linux issues that you have encountered that you'd like me to cover in a future video. 😃
@@lakshaypragnya8256 I would try the Bazzite rollback helper tool (ublue-os.github.io/bazzite/Installing_and_Managing_Software/Updates_Rollbacks_and_Rebasing/bazzite_rollback_helper/) and see if an older version of Bazzite works for you.
Great video, I really hope the ublue team can work on a bit off cli scripting that will at least fallback to cli if the gui fails as at present it just looks like you've lost your root :D
Thanks for the feedback! Typically you can just boot up your old image after a bad update. But yeah after a fresh install you have nothing to rollback to. An easy way to boot into CLI or some fallback option would make things much easier.
I dont know what is happening as i am new to linux but everytime i try and launch bazzite i always get a gray screen that loads up very slowly until im met with a frozen terminal i cant use. Can't even get to the login screen. Is there anyway to fix this?
I have an issue kind of like this one in Fedora KDE spin, where after Grub it boots into black blank screen where I have to use tty: "startplasma-wayland" to get the gui for this specific boot (needs to be done everytime...). Can you kindly please help a noobie out?
KDE uses Simple Desktop Display Manager (sddm for short) service for the login screen. You might find that this service is failing to start or not enabled for some reason, so you getting to the terminal rather than the normal login screen. While you are in tty, have a look at the status of the service with `sudo systemctl status sddm.service`. It could also be is a sddm config issue, have a look at the files in "/etc/sddm.conf.d/" and "/etc/sddm/"
