Org.freedesktop.fwupd: Timeout was reached

So I know this was a problem in fedora-31 but I thought that this was resolved in Fedora 32. I was running the preview beta with no problems but yesterday I did a dnf update and now I’m back to having this error. (The one discussion I was going to post to is closed so this is why I opened this in a new one)

fwupd-issue

When i run journalctl -b -u fwupd this is the output that I get
– Logs begin at Thu 2020-04-09 07:40:11 CDT, end at Fri 2020-05-01 10:09:10 CDT. –

May 01 08:22:03 systemd[1]: Starting Firmware update daemon...
May 01 08:22:03 fwupd[2957]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a)
May 01 08:23:33  systemd[1]: fwupd.service: start operation timed out. Terminating.
May 01 08:23:33  systemd[1]: fwupd.service: Failed with result 'timeout'.
May 01 08:23:33  systemd[1]: Failed to start Firmware update daemon.

Can someone help me troubleshoot this?

This is beyond Ask Fedora to debug. Let’s go straight to upstream. Please report it here.

Look at this recent report for a high-quality report that demonstrates the debug information that you should provide. But please file a new bug rather than piling on to that one, because your issue is likely different even though the symptom is the same. If it turns out to be the same issue, it’s easy for the developer to mark it as such.

@mcatanzaro Thanks for the feedback.

It is actually similar to two of the new issues and I have contributed to the issues on those. I have a logitech keyboard and I also have the same output in the verbose logging of fwupd.

What I was hoping for here was some guidance on how to troubleshoot something like this, not on the how to fix it.

I reverted back to the previous version of fwupd through koji and it resolved my issue for now. So I have excluded the package from being updated also, and I’ll check back occasional on the issues to see if they have been resolved.

Thank you.

I am having the same problem. But looking forward to the new release, as I always do, I have wondered about the effect of this on the cli upgrade. The common advisement on this issue has been, “Ignore it, it will eventually go away.” (Note the FIXME notation.) Will this break the upgrade?

– Logs begin at Thu 2020-02-06 12:43:27 EST, end at Sun 2020-05-03 10:52:22 EDT. –
May 03 10:25:51 localhost.localdomain systemd[1]: Starting Firmware update daemon…
May 03 10:26:16 localhost.localdomain fwupd[2566]: 14:26:16:0180 FIXME failed to allocate dbus proxy object: Error calling StartServiceByName for com.intel.tss2.Ta>
May 03 10:26:16 localhost.localdomain fwupd[2566]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a)
May 03 10:26:16 localhost.localdomain fwupd[2566]: 14:26:16:0201 FuEngine device [WDC WD5003AZEX-00K3CA0] does not define a v>
May 03 10:26:16 localhost.localdomain systemd[1]: Started Firmware update daemon.
~
~

Recently updated to Fedora 32. Now, every time I restart the system, gnome-software produces this error:

Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached

Searching for solutions, I found this Ask Fedora thread that linked to multiple bug reports. All trace the problem to tpm2-abrmd but I did not have that installed. I tried installing it, with no effect. Uninstalled it again.

journalctl -b --no-hostname | grep gnome-software
...
May 03 12:39:48 gnome-software[2424]: not GsPlugin error g-io-error-quark:24: Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached
May 03 12:39:48 gnome-software[2424]: not handling error failed for action refresh: Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached
May 03 12:40:16 gnome-software[2424]: updates-shell: failed to get updates: Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached
...

Feel like I’d need more information for a legitimate bug report. Help welcome. Thank you.

Is there a means of disabling the gnome software fwupd plugin until this is fixed?

@cloudwater and @depling

The fwupd team (at least the contributors) think they have a fix for this.

Please try adding this to line to the /etc/fwupd/daemon.conf
EnumerateAllDevices=false

After adding the line please reboot your computer.

If this does resolve your issue also, if you can please reply to this issue on GitHub. https://github.com/fwupd/fwupd/issues/2048

So far this has resolved everyone issue that has run into it.

2 Likes

That stopped the complaining.

1 Like

We appreciate your work with fwupd. I tried ammending the daemon.conf file as you suggested, but so far it seems to have not been effective. I have yet to upgrade to 32.