I am running an updated version of fedora version 31 and consistently get an error on update containing the message as shown in the title.
I have figured out it has something to do with a service and I have been hunting for the file org.freedesktop.fwupd, but I have been unable to find it. I checked /etc/systemd/ first but still could not find it. I also executed from \etc the command find . -name org.freedesktop.fwupd to no avail.
My regular update I do using dnf upgrade --refresh on the commandline and have had no issues doing that.
My queries are “Why does freedesktop have an update?” and “do I need this freedesktop?” or alternatively “How can I find out what is wrong?”.
Turns out tpm2-abrmd was the problem. It is resolved upstream, but not in the fedora 31 dist yet. I removed it as I had no dependencies on this package. I do wonder if I should reinstall i.e. if this package has a use I cannot infer from dependencies: any know?
I marked your answer as the solution and added +1. Thanks.
Why is downgrading and blocking update a better approach than uninstalling? As far as I can see none of the other packages depend on tpm2-abrmd. Or is there some hidden way the package may be used only if it is present?
P.S. My plan was to uninstall and check for version number of the package regularly
Anothers Motherboards is coming with the TPM module or chip included which can be active or inactive. You need check it in your BIOS model if you are curious.
And the package has the mission of check for access broker. The problem is because the package fwupd is updating firmware and there are some part where tpm2 is not working like waited with the fwupd package to update some firmware… the problem is also fwupd is linked with the gnome-software so if you downgrade the package you will need downgrade gnome-software package too. At least so was before… but it bug is coming solve in the next update of tpm2 package what will be drop in the next updates surely.
I hope it did help you understand a bit more about the error of it package.
@alciregi according to the report we will need wait a bit with it, the version that solve the issue would be the 2.3.1. While in repos still we do have the 2.2.0 what i did test do some days and the issue was present.
I did install it right now and enable +start service and version 2.2.0-4 looks working good and skipping the tpm check if you don’t have it. I will reboot now the PC to check it after reboot )so the version that i did test maybe was 2.2.0-3 my error so but one thing is sure I did check one days ago and the issue was there )
[jorge@f31 ~]$ systemctl status tpm2-abrmd
● tpm2-abrmd.service - TPM2 Access Broker and Resource Management Daemon
Loaded: loaded (/usr/lib/systemd/system/tpm2-abrmd.service; enabled; vendor preset: disabled)
Active: inactive (dead)
Condition: start condition failed at Sun 2020-01-19 09:40:10 CET; 3min 5s ago
jan 19 09:39:08 f31 systemd: Condition check resulted in TPM2 Access Broker and Resource Management Daemon being skipped.
jan 19 09:40:10 f31 systemd: Condition check resulted in TPM2 Access Broker and Resource Management Daemon being skipped.
Edit: After reboot spamming again it is still failing so it was probably the version that i did test before too.
I’ve also got the same nasty error notification message since I upgraded my computers (a desktop and a laptop) to Fedora 31.
At every boot, I got the notification:
An important update has failed.
Detailed errors from the package manager follow:
Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached.
I finally decided to deal with that annoyance and also check if there was a security issue here ; and I landed here.
After reading all the thread, I checked my fully updated Fedora 31 installations.
What’s installed is :
Name : tpm2-abrmd
Version : 2.2.0
Release : 4.fc31
Architecture : i686
Size : 117 k
Source : tpm2-abrmd-2.2.0-4.fc31.src.rpm
Since on one of the computers the TPM chip was not activated, I uninstalled the tpm2-abrmd package.
As expected, no more error notification message at every boot! Done.
I’ll re-install the package tpm2-abrmd when it gets fixed, hopefully soon in a future Fedora update.
Oddly, IMO, this problem happened on my system for the first time, today. I update my packages multiple times per week, so why didn’t it cause me a problem in December instead of waiting until late February?