Hi,
this is what fwupdmgr does on my desktop box:
1 [66/4825]mh@fan:~ $ sudo fwupdmgr update
Devices with no available firmware updates:
• SSD 840 EVO 1TB
• ST4000DM000-1F2168
• System Firmware
• USB2.0 Hub
╔══════════════════════════════════════════════════════════════════════════════╗
║ Upgrade UEFI dbx from 77 to 217? ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ This updates the dbx to the latest release from Microsoft which adds ║
║ insecure versions of grub and shim to the list of forbidden signatures due ║
║ to multiple discovered security updates. ║
║ ║
║ Before installing the update, fwupd will check for any affected executables ║
║ in the ESP and will refuse to update if it finds any boot binaries signed ║
║ with any of the forbidden signatures. If the installation fails, you will ║
║ need to update shim and grub packages before the update can be deployed. ║
║ ║
║ Once you have installed this dbx update, any DVD or USB installer images ║
║ signed with the old signatures may not work correctly. You may have to ║
║ temporarily turn off secure boot when using recovery or installation media, ║
║ if new images have not been made available by your distribution. ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝
Perform operation? [Y|n]: y
Downloading… [***************************************]
Downloading… [***************************************]
Decompressing… [***************************************]
Authenticating… [***************************************]
Decompressing… [ ]
Blocked executable in the ESP, ensure grub and shim are up to date: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/freedesktop/UDisks2/block_devices/sde1”
I dont like this very much for multiple reasons:
- the software should not let a raw DBUS error message go through to the
user's terminal
- the software should make a better effort to say which executable is
blocked
- the system in question does not have an sde device. sde1 does not exist.
So the software should ignore this error and continue.
Before this showstopper condition was met, the software was giving the
same error message for /dev/sdb1. That partition exists and had the esp
bit set, but was not even formatted. Resetting the esp bit on the partition
didn't heal the issue, it was necessary to put a filesystem on it.
But on a nonexistent device, I cannot put a filesystem.
Greetings
Marc