I suspect this is related to an upgrade from the intermediary version that had problematic objects/permissions created.
Can you please try to check whether there are broken symlinks in /var/lib/private or /var/cache/private? Thanks, > -----Original Message----- > From: Diederik de Haas <didi.deb...@cknow.org> > Sent: Saturday, March 14, 2020 7:26 AM > To: Debian Bug Tracking System > Subject: Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh > fwupd metadata and update motd. > > > [EXTERNAL EMAIL] > > Package: fwupd > Version: 1.3.9-2 > Followup-For: Bug #943343 > > Essentially the same issue as initially reported, but just got version > 1.3.9-2 and it's still happening. > Running the 'ExecStart' line manually succeeded successfully. > > root@bagend:~# systemctl status fwupd-refresh.service ● fwupd- > refresh.service - Refresh fwupd metadata and update motd > Loaded: loaded (/lib/systemd/system/fwupd-refresh.service; static; vendor > preset: disabled) > Active: failed (Result: exit-code) since Sat 2020-03-14 09:37:54 CET; 3h > 32min > ago > TriggeredBy: ● fwupd-refresh.timer > Docs: man:fwupdmgr(1) > Main PID: 13148 (code=exited, status=1/FAILURE) > > mrt 14 09:37:54 bagend systemd[1]: Starting Refresh fwupd metadata and > update motd... > mrt 14 09:37:54 bagend systemd[1]: fwupd-refresh.service: Main process exited, > code=exited, status=1/FAILURE mrt 14 09:37:54 bagend systemd[1]: fwupd- > refresh.service: Failed with result 'exit-code'. > mrt 14 09:37:54 bagend systemd[1]: Failed to start Refresh fwupd metadata and > update motd. > root@bagend:~# 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. > root@bagend:~# journalctl -xe > -- A start job for unit fwupd-refresh.timer has finished successfully. > -- > -- The job identifier is 5651. > mrt 14 13:08:51 bagend systemd[1]: Reloading. > mrt 14 13:08:51 bagend systemd[1]: /lib/systemd/system/dbus.socket:5: > ListenStream= references a path below legacy directory /var/run/, updating > /var/run/d> mrt 14 13:08:52 bagend systemd[1]: Reloading. > mrt 14 13:08:52 bagend systemd[1]: /lib/systemd/system/dbus.socket:5: > ListenStream= references a path below legacy directory /var/run/, updating > /var/run/d> mrt 14 13:08:55 bagend dbus-daemon[828]: [system] Reloaded > configuration mrt 14 13:10:24 bagend systemd[1]: Starting Refresh fwupd > metadata and update motd... > -- Subject: A start job for unit fwupd-refresh.service has begun execution > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- A start job for unit fwupd-refresh.service has begun execution. > -- > -- The job identifier is 5965. > mrt 14 13:10:24 bagend systemd[1]: fwupd-refresh.service: Main process exited, > code=exited, status=1/FAILURE > -- Subject: Unit process exited > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- An ExecStart= process belonging to unit fwupd-refresh.service has exited. > -- > -- The process' exit code is 'exited' and its exit status is 1. > mrt 14 13:10:24 bagend systemd[1]: fwupd-refresh.service: Failed with result > 'exit-code'. > -- Subject: Unit failed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- The unit fwupd-refresh.service has entered the 'failed' state with result > 'exit- > code'. > mrt 14 13:10:24 bagend systemd[1]: Failed to start Refresh fwupd metadata and > update motd. > -- Subject: A start job for unit fwupd-refresh.service has failed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- A start job for unit fwupd-refresh.service has finished with a failure. > -- > -- The job identifier is 5965 and the job result is failed. > root@bagend:~# cat $(locate fwupd-refresh.service) [Unit] Description=Refresh > fwupd metadata and update motd > Documentation=man:fwupdmgr(1) > After=network.target network-online.target systemd-networkd.service > NetworkManager.service connman.service > > [Service] > Type=oneshot > CacheDirectory=fwupdmgr > StandardError=null > DynamicUser=yes > RestrictAddressFamilies=AF_NETLINK AF_UNIX AF_INET AF_INET6 > SystemCallFilter=~@mount ProtectKernelModules=yes > ProtectControlGroups=yes RestrictRealtime=yes > SuccessExitStatus=2 > ExecStart=/usr/bin/fwupdmgr refresh --no-metadata-check root@bagend:~# > /usr/bin/fwupdmgr refresh --no-metadata-check Fetching metadata > https://cdn.fwupd.org/downloads/firmware.xml.gz > Downloading… [***************************************] > Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc > > Successfully downloaded new metadata: 1 local device supported > > > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), > (101, > 'experimental'), (1, 'experimental-debug') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.4.0-4-amd64 (SMP w/16 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages fwupd depends on: > ii libc6 2.30-2 > ii libefiboot1 37-2 > ii libefivar1 37-2 > ii libelf1 0.176-1.1 > ii libflashrom1 1.2-5 > ii libfwupd2 1.3.9-2 > ii libfwupdplugin1 1.3.9-2 > ii libglib2.0-0 2.64.0-2 > ii libgnutls30 3.6.12-2 > ii libgpg-error0 1.37-1 > ii libgpgme11 1.13.1-7 > ii libgudev-1.0-0 233-1 > ii libgusb2 0.3.0-1 > ii libjson-glib-1.0-0 1.4.4-2 > ii libpolkit-gobject-1-0 0.105-26 > ii libsmbios-c2 2.4.3-1 > ii libsoup2.4-1 2.70.0-1 > ii libsqlite3-0 3.31.1-4 > ii libtss2-esys0 2.3.3-1 > ii libxmlb1 0.1.15-1 > ii shared-mime-info 1.10-1 > > Versions of packages fwupd recommends: > ii bolt 0.8-4 > ii fwupd-amd64-signed [fwupd-signed] 1.3.9+2 > ii python3 3.8.2-1 > > fwupd suggests no packages. > > -- no debconf information
