PSA: Fedora 42 itself force-disables Secure Boot on Secure-Boot-enabled systems | secureblue | Page 1

tranquil gulch Apr 19, 2025, 4:38 PM

#

yes, this appears to be an upstream bug: https://discussion.fedoraproject.org/t/fedora-42-disables-secure-boot-after-upgrade-and-on-new-installations-claiming-that-the-system-doesnt-support-secure-boot-anymore/149013
https://bugzilla.redhat.com/show_bug.cgi?id=2361002

#

oh whoops lol

#

I've already enrolled the secureblue secure boot key but I'm also seeing some issue: mokutil --sb-state says "SecureBoot enabled" but the "Device Security" panel in GNOME settings says "Secure Boot has Problems" and that "It is currently turned on, but will not work due to having an invalid key."

#

there's several people reporting the same issue here: https://old.reddit.com/r/Fedora/comments/1k0djnb/security_boot_problems_after_update_of_fedora_42/

From the Fedora community on Reddit: Security Boot problems after u...

Explore this post and more from the Fedora community

tranquil gulch Apr 19, 2025, 5:00 PM

#

ok I asked in the Fedora discord, sounds like it's a fwupd bug, already fixed upstream but the fix hasn't made it into a release yet, so it should be fixed once fwupd has a new release (probably 2.0.9) and that release makes its way into the Fedora repos

stable hinge Apr 20, 2025, 5:29 PM

#

PSA: Fedora 42 itself force-disables Secure Boot on Secure-Boot-enabled systems

burnt heath Apr 20, 2025, 8:42 PM

#

Are you sure secure boot is showing as fully enabled? There may be an option in bios "install keys" try than then save them

burnt heath Apr 21, 2025, 8:28 AM

#

Ignore than for now I believe

burnt heath Apr 21, 2025, 2:52 PM

#

Do you mean it no longer shows in privacy correctly?

#PSA: Fedora 42 itself force-disables Secure Boot on Secure-Boot-enabled systems