Tried to Update Security keys but failed
So I got the announcement about the error that occurred on 07/04 and I tried to input the command in the linked article, but when I did so this happened in the terminal. Hoping to get some assistance with this.
11 Replies
I Put in the command, its the same result
looks you are in 39 tag and the image probably arent updated
yep, need to rebase to
:stable
39 hasn't been updated in a long, long timerebase to
ostre-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:40-20240627 then reboot and run the command to fix the security keys.
Any 40 image before that date should work for youI followed the instructions on https://universal-blue.discourse.group/t/how-to-install-universal-blues-base-images/868 and I used the info you provided and well.... see the attached image
Universal Blue
How to Install Universal Blue's Base Images
What are the base images? The base images are the building blocks for our end-user images like Bluefin, Aurora, and Bazzite. They live in the ublue-os/main repository. These are generic Fedora Atomic Desktop but with non-free codecs, RPMFusion, and automatic updates out of the box. The base images do not deviate too far from Fedora Atomic and...
that image might have been re-made with the new key. try an older one like
40-20240528OK, Managed to rebase to stable, everything seems like its working, I appreciate your help.
np did the 2nd date i gave you work as the middle jump to latest stable?
or did you have to go further back
I just used ':stable' instead because whatever specific image I tried got me the error above.
ah probably ran the script, let it fail then rebase to stable since you were rebased to
39 specifically which does not have the new key