Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.
I'm running testing/sid and have fwupd-1.5.5-2 installed. I have found
that when fwupd-refresh.service restarts either with the timer or
manually that if DynamicUser=yes is enabled then the service fails to
start. When I remove DynamicUser from the unit it restarts fine.
I noticed that the unit has: CacheDirectory=fwupdmgr but the
metadata seems to live in /var/cache/fwupd.
After purging the package and removing /var/cache/fwup* /var/lib/fwupd
/var/cache/private/fwupd and reinstalling I can see the /var/cache dirs
created but the service does not start.
When removing the "StandardError=null" directive from the unit I get an
additional error, which seems to indicate it's having trouble
talking to dbus.
$ sudo systemctl restart fwupd-refresh.service
Job for fwupd-refresh.service failed because the control process exited with error code.
See "systemctl status fwupd-refresh.service" and "journalctl -xe" for details.
$ sudo journalctl -f
Jan 27 10:09:30 systemd: Starting Refresh fwupd metadata and update motd...
Jan 27 10:09:31 fwupdmgr: (fwupdmgr:176638): GLib-DEBUG: 10:09:31.089: setenv()/putenv() are not thread-safe and should not be used after threads are created
Jan 27 10:09:31 systemd: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE
Jan 27 10:09:31 systemd: fwupd-refresh.service: Failed with result 'exit-code'.
Jan 27 10:09:31 systemd: Failed to start Refresh fwupd metadata and update motd.
$ find /var/cache/fw*
$ sudo ls -la /var/cache/fwupdmgr /var/cache/private/fwupdmgr
lrwxrwxrwx 1 root root 16 Jan 27 10:57 /var/cache/fwupdmgr -> private/fwupdmgr
drwxr-xr-x 2 62803 62803 4096 Jan 27 10:57 .
drwx------ 3 root root 4096 Jan 27 10:57 ..
Jan 27 11:09:30 fwupdmgr: Failed to connect to daemon: Exhausted all available authentication mechanisms (tried: EXTERNAL) (available: EXTERNAL)