System Update: No Signature Exists
I've seen the older issues with this, but it's happening on a new install. At least one other person has also seen this. Both instances are from the Nvidia branch.
56 Replies
The exact same error is popping up for me too. The machine was updating just fine until today.
Your screenshot showed you were running the nvidia build. Are you running an nvidia card? Just making sure we have all the information.
The laptop has switchable graphics, AMD APU and an nVidia dedicated GPU
Mine's a desktop with an RTX 4060 Ti
Will check on my nVidia desktop later today also to see if I get the same issue. Updating apps and packages through Discover works normally so it looks its only a ujust issue with updating
My 11th Gen Intel laptop just updated normally. It must be the nvidia image. I'd assume they're working on something and we just tried to update too soon.
I had this one day recently on my custom image. No idea what happened but I booted up my ostree:1 entry in grub and updated from there and the issue has not shown up again.
Might also work rebasing to an unsigned image and back to a signed also, but booting up the older entry and updating from that removes a few steps and saves a lot of time.
I'll probably try that. I'm wondering what the actual issue is, though.
Also getting this issue, also on an Nvidia build
if you do not have an entry that is actually older, try the rebase to the unsigned version and back to signed.
Is it the same line as rebasing to what I have but with "unsigned" or do I have to do something else? I've used linux for years but recently chose Bazzite as my daily driver.
rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-nvidia-open:stable
then reboot to it and
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
replace bazzite-nvidia-open with whatever image you are on. you can check that with rpm-ostree status
you can also just try curl -sL https://fix.universal-blue.org/ | sudo bash which will download the key and update, but if the signature is missing from the image then i think the above method will work better
well
i have no idea
try boot to the old entry and update through that
have tryed but it was same
because clearly it could update from the 12th to the 14th
i have done it on 12th image it didnt work and then gone to 14th image
and i dosent work on 12th nor 14th
This has the same error.
bazzite-rollback-helper didnt help for rebaseing to 21th image now trying oldet than 12th image
Which nvidia module is the standard bazzite nvidia install using?
It's the same for older images. "A signature is required."
depends on your card which image is shown to you to download
if you have an RTX or a GTX16XX card then
nvidia-open
if you have anything older then nvidiai'm on a 3090 Ti, so open
even when trying to rebase to an older unsigned image?
dang it
weirdly enough my bazzite install on my Laptop (ROG Zephyrus G14, Ryzen 5 4600HS and GTX 1650 Ti) updates just fine
ok so try
rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-nvidia-open:stable-40.20240912.0
then reboot to it and on tuesday try
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stableHere is my fastfetch result, it seems i installed my desktop back in July after the changes of the image at that time
yeah you can try rebase to nvidia-open, it didnt exist when you installed the system
but i would suggest waiting until tuesday
time to be patient
UPDATE rebaseing from 8th didint work
i can still linux, i still have an arch install on a dedicated ssd in the system
so i'm not exposed to windows
same sig validation errors on a fresh default bazzite install with
ujust update never been run successfully since first bootalso having the same issues as other ppl here, I did first part. but why do I need to wait for tuesday to do the second command ? (Im fine with waiting I just wanna know why)
new builds are scheduled to run on mondays, waiting to tuesday means it will be available for all timezones
and currently the build is failing
Ahh okay
Thx
I try it too because i have same problem
Okay i just see you messages.
We need to run basic upgrade tuesday or we need to made manual upgrade ?
read my message, rebase back to
stable on tuesday, i will try kick a build off earlier but since the last one failed i suspect the one i will kick off will also failI just checked another laptop, a framework 13, and it's also running into the same issue without Nvidia being present
thinking its something weird with the current image 🤔
i kicked off a new build 1 hour ago
and it successfully built
so see if rebasing to the unsigned version of that works
So on my nVidia bazzite desktop it's updating just normally (so far)
2 reports on the forum, I was wondering if signatures didn't get pushed on the last set of builds or something
Well they seem to be there on the new ones I pushed today then
Yeah, interesting
so its simple to fix with ?
for me, that seems to help
That didn't work at all for me last night. Everything seems alright today.
mmmh something is weird....for sure with those update distribution channels and the keys
Definitely. The .sh that links to had a signature error yesterday for me.
hope we find out why they are so finky...again... 😄
Probably because it was trying to pull a signature that didn't exist
We pushed a new build the error should be cleared up
I probably would have never noticed if I hadn't had full system crashes due to a capture card.
The next staged build would have also unwedged it
look at it this way, the system works and stopped you from downloading an update that was not properly signed by us (even though it just did not push the signature used to verify it)