"Bad shim signature" when rebasing to Bazzite
Sooo... As far as I'm concerned, the whole idea of Universal Blue is, that you can essentially use UBlue, then if you want rebase to Bluefin, and if you feel like it, freely rebase to Bazzite. Or any other image.
So I tried that - installed Bluefin from official UBlue ISO, than rebased to Bazzite stable (the default one). After rebooting, when I select Bazzite in grub, I get:
While Bluefin boots normally. Is this intended behaviour? Or I'm just stupid and it's not like I can rebase Bluefin or any other image to any different image?
As for my hardware - ThinkPad E14 Gen2, i7-1165G7
15 Replies
You're using secure boot and haven't enrolled our key
you can disable secure boot and then enroll the key with our ujust command, then re-enable it
Secure boot is disabled, but okay, I'll try enrolling the key - you mean in Bluefin, right?
that error can only mean it's enabled
double check
Sorry, me stupido potato... I disabled TPM, not secure boot, cuz I was getting "Unknown TPM error"... :facepalm: Will try that
Works now, thank you Kyle!
np!
By the way, since I have you here - why is it crucial to perform
rpm-ostree reset before rebasing?we mention it to weed out common help requests
you don't have to do it 🤫
but if you've layered stuff we already layer
or that conflicts with ours
it'll blow up in your face
Okay, so let me get this straight - maintainers provide the base, preconfigured image - UBlue, Bluefin, Bazzite, as well as custom layers with applications - let's say Alacritty for simplicity. Every UBlue image has its own custom layers.
Then I can layer my own software on top of that, eg. using
rpm-ostree install kitty. When I want to rebase, I change the underlying image as well as custom layers. And if so happens, that in this custom layer there already is kitty, this could blow in my face and break. So I should either review custom layers to ensure there are no conflicts, or perform rpm-ostree reset, which will remove all MY layers, essentially removing kitty. So if I ever want to go back to Bluefin deployment I pinned, it will no longer be there - I will have to again layer it on top of Bluefin. Correct?it could if bazzite shipped kitty
or a package that conflicts with kitty
we do neither, so that's safe
That's just an example, but I assume my thinking is correct. So it's not like I can pin a fully customized bluefin, rebase to bazzite and then go back to bluefin any time or switch between them at will? Or does that only affect layered packages, the flatpaks and all my files will be intact?
flatpaks remain intact
and layered packages are part of your pins technically
Yeah, but after rpm-ostree reset they will be gone
so don't reset
just means your layered packages need to be compatible with both images
Okay okay. Now only to read what "pinning" actually does and how it works. Thanks a ton!
np