3

I'm trying to install a UEFI Secure Boot dbx update on my Dell Latitude 5410 running Ubuntu, but it consistently fails to apply during reboot.

I’ve followed the recommended steps:

  • Used sudo fwupdmgr update to apply the UEFI dbx firmware update
  • Disabled Secure Boot
  • Moved "Linux Firmware Update" to the top of the boot order
  • Reinstalled the update via sudo fwupdmgr reinstall 2

After rebooting, I get the following black screens then ubuntu start normally:

fwupd-efi version 1.4
WARNING: No updates to process, exiting in 10 seconds.

Then:

start_image() returned Invalid Parameter, falling back to default loader

I confirmed that fwupd is installed from Ubuntu's official repositories via apt, and the update gets queued successfully — but fails silently on reboot. Manual .cab flashing via USB is the only workaround left.

I’ve also opened a GitHub issue here: https://github.com/fwupd/fwupd/issues/9025

And reported bug in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2117332

Question:

Is there any known workaround from the Ubuntu side (shim/efibootmgr/fwupd package version) to make the capsule update work properly during boot? Do I need to upgrade/downgrade any packages like shim or fwupd to avoid this error?


>>> Updates

I’ve applied the workaround mentioned in this answer.

sudo apt remove fwupd
sudo snap install fwupd --classic
sudo reboot
sudo snap connect snap-store:fwupd fwupd:fwupd
sudo reboot

That worked!

Additionally, I updated the firmware to the latest version using the fwupd package installed via Snap.

But now, every time I boot into my system, this notification appears.

enter image description here

enter image description here

Does anyone know why this is happening? Is there any way to fix it? It's really frustrating.

  • I am also experiencing the same issue on my Lenovo Thinkpad E14 running Ubuntu 22.04. – Nilesh Jul 11 '25 at 04:06
  • I have the same problem with Ubuntu 22.04.5 with a different current firmware version (468): Secure Boot dbx Configuration Update 468 -> 20241101 – Jaydin Jul 22 '25 at 23:41

1 Answers1

4

As explained in this Ubuntu bug, the issue seems to be that fwupd version is too old. Here is the workaround (explained here):

sudo apt remove fwupd
sudo snap install fwupd --classic
sudo reboot
sudo snap connect snap-store:fwupd fwupd:fwupd
sudo reboot

I haven't tried this workaround, as I am hoping for an Ubuntu native update. Please comment below if the above workaround works for you.

Jaydin
  • 1,631
  • 1
  • 23
  • 47