Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.
Internal Use - Confidential
In 1.3.2-5 the service is disabled by default (and also this issue should be fixed).
> -----Original Message-----
> From: Jean-Marc <jean-marc@6jf.be>
> Sent: Wednesday, October 23, 2019 11:37 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.2-2
> Severity: normal
>
> Dear Maintainer,
>
> On my PC, fwupd-refresh.service failed to start.
>
> $ 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: enabled)
> Active: failed (Result: exit-code) since Wed 2019-10-23 16:06:35 CEST; 2h
> 13min ago
> Docs: man:fwupdmgr(1)
> Process: 4608 ExecStart=/usr/bin/fwupdmgr refresh (code=exited,
> status=0/SUCCESS)
> Process: 4624 ExecStart=/usr/bin/fwupdmgr get-updates --log 85-fwupd
> (code=exited, status=1/FAILURE) Main PID: 4624 (code=exited,
> status=1/FAILURE)
>
> oct 23 16:06:35 svrname systemd[1]: Starting Refresh fwupd metadata and
> update motd...
> oct 23 16:06:35 svrname fwupdmgr[4608]: Fetching metadata
> https://cdn.fwupd.org/downloads/firmware.xml.gz
> oct 23 16:06:35 svrname fwupdmgr[4608]: Fetching signature
> https://cdn.fwupd.org/downloads/firmware.xml.gz.asc
> oct 23 16:06:35 svrname systemd[1]: fwupd-refresh.service: Main process
> exited, code=exited, status=1/FAILURE oct 23 16:06:35 svrname systemd[1]:
> fwupd-refresh.service: Failed with result 'exit-code'.
> oct 23 16:06:35 svrname systemd[1]: Failed to start Refresh fwupd metadata
> and update motd.
>
> That's the service definition:
> $ systemctl cat fwupd-refresh.service
> # /lib/systemd/system/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
> RuntimeDirectory=motd.d
> CacheDirectory=fwupdmgr
> RuntimeDirectoryPreserve=yes
> StandardError=null
> ExecStart=/usr/bin/fwupdmgr refresh
> ExecStart=/usr/bin/fwupdmgr get-updates --log 85-fwupd DynamicUser=yes
> RestrictAddressFamilies=AF_NETLINK AF_UNIX AF_INET AF_INET6
> SystemCallFilter=~@mount ProtectKernelModules=yes
> ProtectControlGroups=yes RestrictRealtime=yes
>
> And about the runtime directory:
> $ ls -ld /run/motd.d
> lrwxrwxrwx 1 root root 14 oct 23 16:06 /run/motd.d -> private/motd.d $ ls -ld
> /run/private/
> drwx------ 3 root root 60 oct 23 16:06 /run/private/ $ sudo ls -ld
> /run/private/motd.d drwxr-xr-x 2 62803 62803 40 oct 23 16:06
> /run/private/motd.d $ sudo ls -l /run/private/motd.d total 0
>
>
> Kind Regards,
>
> Jean-Marc
>
>
> -- System Information:
> Debian Release: bullseye/sid
> APT prefers testing
> APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
> Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8),
> LANGUAGE=fr_BE:fr (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages fwupd depends on:
> ii libarchive13 3.4.0-1
> ii libc6 2.29-2
> ii libefiboot1 37-2
> ii libefivar1 37-2
> ii libelf1 0.176-1.1
> ii libfwupd2 1.3.2-2
> ii libgcab-1.0-0 1.3-1
> ii libglib2.0-0 2.62.1-1
> ii libgnutls30 3.6.9-5
> ii libgpg-error0 1.36-7
> ii libgpgme11 1.13.1-1
> 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.1-1
> ii libsoup2.4-1 2.68.2-1
> ii libsqlite3-0 3.30.1-1
> ii libtss2-esys0 2.1.0-4+b1
> ii libxmlb1 0.1.13-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.2+2
> ii python3 3.7.5-1
>
> fwupd suggests no packages.
>
> -- no debconf information
Reply to: