Comment 13 for bug 1987067

Sorry, I've been distracted with other things for a while.

But since your last comment the system with the patched fwupd package actually idled only.

So I still see mesgs like this in the logs even today:

Sep 13 04:35:09 hwe0004 systemd[1]: Starting Firmware update daemon...
Sep 13 04:35:09 hwe0004 fwupd[74725]: 04:35:09:0585 FuContext Failed to load SMBIOS: neither SMBIOS or DT found
Sep 13 04:35:09 hwe0004 dbus-daemon[706]: [system] Successfully activated service 'org.freedesktop.fwupd'
Sep 13 04:35:09 hwe0004 systemd[1]: Started Firmware update daemon.
Sep 13 04:35:09 hwe0004 fwupdmgr[74719]: Updating lvfs
Sep 13 04:35:09 hwe0004 fwupdmgr[74719]: Downloading…: 0%
Sep 13 04:36:09 hwe0004 systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE
Sep 13 04:36:09 hwe0004 systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'.
Sep 13 04:36:09 hwe0004 systemd[1]: Failed to start Refresh fwupd metadata and update motd.

The failed download is probably okay, since the test system has limited connectivity.

I see in /etc/passwd:
fwupd-refresh:x:112:120:fwupd-refresh user,,,:/run/systemd:/usr/sbin/nologin
so it seems to use the special 'fwupd-refresh' user.

And running the refresh by hand does not succeed (due to the limited connectivity):
$ sudo fwupdmgr refresh
Updating lvfs
Downloading… [ | ]failed to download file: Connection timeout after 60001 ms
but it also does not crash.
Folder "/var/crash/" is actually empty - no new crash happened in the last 2+ weeks.