Hi, I got this error when running ‘dnf update’:
“Warning: A pending offline transaction initiated by the following command will be invalidated: dnf5daemon-server.”
i ran ‘dnf5 offline clean’ and it temporarily resolved the issue, but the error returns.
Perhaps you have automatic update and download enabled in Gnome Software. This can be modified by the Preferences entry in the menu In Software.
Yes, it was. Thanks!
I can confirm the same thing. I am getting that message when running dnf at the terminal. I get the “install pending updates” message when trying to restart. Even after restarting, it says there are pending updates if I try to restart again, even though Software doesn’t show any available updates.
This seems to be a newer thing, because I never saw the message when running dnf until the last few days.
I didn’t want to say this, but it sounds like an attempt at sabotage.
I’m confused? What do you mean?
Can you also check
Can’t speak for OP, but as someone who is having the same problem with restart/shutdown always showing doing an offline update, even when no update is available as well as the new warning message after running dnf.
I don’t have any pending/available FW updates.
too much bugs, atacks, etc.
Thanks, I forgot that the problem is with the dbx key.
Curious here. Doesn’t normal dnf updates include firmwares? Why have to run these command separately? Thanks.
No, standard dnf update or dnf upgrade commands do not include firmware or BIOS updates. The dnf tool is designed exclusively to manage RPM packages (software and drivers), whereas firmware updates are handled by a separate mechanism.
sudo fwupdmgr update
Some firmware is included in the RPM package linux-firmware and its subpackages (Fedora package link, upstream repo). These are binary blobs which aren’t covered by open source licenses but which the Linux kernel folks do have permission to redistribute.
On the command line, you get that package through dnf.
Other firmware is distributed by vendor via the Linux Vendor Firmware Service. That’s what you get through fwupdmgr on the command line.
The GUI software stores (GNOME Software, and Discover in KDE Plasma) cover both of those channels, plus other stuff like Flatpaks.
Hi folks, so whats the problem with this “kek” firmware, having this issue for some time now:
executed: sudo fwupdmgr update
this outputed:
Update 2011 KEK CA to 2023? This updates the UEFI Signature Database (the “KEK”) to the latest release from Microsoft, signed by DO NOT TRUST - AMI Test PK.
Do the operation? [Y|n]: y
*Writing… *
failed to write-firmware: failed to write (null): failed to write data to efivarsfs: Error while recording the file descriptor: Invalid argument
look for “solution”
There is also firmware that Fedora is not allowed to distribute, but can be found either in the original OS or 3rd party sites. A fresh install of Fedora on my old iMac has errors for missing Nvidia firmware. For even older Apple systems used to extract Nvidia firmware from macOS, but now Debian has a collection of old Nvidia firmware files that has what I need and is discoverable using the names of missing files.
The problem isn’t the firmware; as I said, I had automatic updates enabled and the error kept occurring. It wasn’t a firmware bug.
