# Bluefin stable image 40.20240801.0 fails to boot

**URL:** <https://universal-blue.discourse.group/t/bluefin-stable-image-40-20240801-0-fails-to-boot/3337>\
**Category:** Bluefin\
**Created:** [August 2, 2024, 2:30pm UTC](https://universal-blue.discourse.group/t/bluefin-stable-image-40-20240801-0-fails-to-boot/3337 "2024-08-02T14:30:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![stego](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/stego/32/866_2.png) [@stego](https://universal-blue.discourse.group/u/stego)\
**Post date:** [August 2, 2024, 2:30pm UTC](https://universal-blue.discourse.group/t/bluefin-stable-image-40-20240801-0-fails-to-boot/3337/1 "2024-08-02T14:30:03Z")

</div>

There was an update yesterday (thursday), which probably means that it was a security update, given that stable is typically updated on tuesdays.

When I select the newest grup menu entry I get (transcribed):

```auto
error: ../../grub_core/kern/efi/sb.c:182 bad shim signature
error: ../../loader/i386/efi/linux.c:258 you need to load the kernel first

```

And after a few seconds the grub boot menu opens again.

Secure boot is enabled.

```auto
$ rpm-ostree status
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:stable
                   Digest: sha256:b8ec0f2ab98acad7c01d4f80e8584a213d91b7b94324102d510f2a5e07bf31a9
                  Version: 40.20240801.0 (2024-08-01T19:51:22Z)
                     Diff: 25 upgraded, 7 removed, 7 added

● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin:stable
                   Digest: sha256:1afce620e1190ad2cd194579b38d1eeb45f843c40a9380da78940b4b0c7585a9
                  Version: 40.20240730.0 (2024-07-30T05:49:18Z)

```

---

<div class="post-metadata">

**Author:** ![nicknamenamenick](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/nicknamenamenick/32/4512_2.png) [@nicknamenamenick](https://universal-blue.discourse.group/u/nicknamenamenick)\
**Post date:** [August 2, 2024, 2:52pm UTC](https://universal-blue.discourse.group/t/bluefin-stable-image-40-20240801-0-fails-to-boot/3337/2 "2024-08-02T14:52:16Z")

</div>

This is most likely Secure Boot related. I would disable it, then enter `ujust enroll-secure-boot-key` in the terminal on the next boot and enter the password `universalblue` and turn Secure Boot back on, and see if the error still occurs.

---

<div class="post-metadata">

**Author:** ![stego](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/stego/32/866_2.png) [@stego](https://universal-blue.discourse.group/u/stego)\
**Post date:** [August 2, 2024, 3:31pm UTC](https://universal-blue.discourse.group/t/bluefin-stable-image-40-20240801-0-fails-to-boot/3337/3 "2024-08-02T15:31:00Z")

</div>

That solved it. I’m still new to secure boot and I didn’t know that I also need to run `ujust enroll-secure-boot-key` after switching secure boot on.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/univeral_blue/original/2X/e/e39f7d1952979cf23b0f8d634e025fb38da50026.png) [@system](https://universal-blue.discourse.group/u/system)\
**Post date:** [August 3, 2024, 3:31am UTC](https://universal-blue.discourse.group/t/bluefin-stable-image-40-20240801-0-fails-to-boot/3337/4 "2024-08-03T03:31:53Z")

</div>

This topic was automatically closed 12 hours after the last reply. New replies are no longer allowed.