Subject: Re: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.

From: Ritesh Raj Sarraf <[email-masked]>
Date: Mon, 30 Dec 2019 21:42:07 +0530

Package: fwupd
Version: 1.3.4-1
Followup-For: Bug #943343

This is still broken with current mentioned version in Debian Testing. I
thought this was fixed a couple months ago.

rrs@priyasi:/var/tmp/Debian-Build/Result$ 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 Mon 2019-12-30 21:21:11 IST; 10min ago
TriggeredBy: ● fwupd-refresh.timer
       Docs: man:fwupdmgr(1)
    Process: 108303 ExecStart=/usr/bin/fwupdmgr refresh --no-metadata-check (code=exited, status=1/FAILURE)
   Main PID: 108303 (code=exited, status=1/FAILURE)

Dec 30 21:21:06 priyasi systemd[1]: Starting Refresh fwupd metadata and update motd...
Dec 30 21:21:06 priyasi fwupdmgr[108303]: Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz
Dec 30 21:21:11 priyasi systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE
Dec 30 21:21:11 priyasi systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'.
Dec 30 21:21:11 priyasi systemd[1]: Failed to start Refresh fwupd metadata and update motd.
21:32 ♒ ॐ   ☹ => 3

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER
Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (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  libarchive13           3.4.0-1+b1
ii  libc6                  2.29-3
ii  libefiboot1            37-2
ii  libefivar1             37-2
ii  libelf1                0.176-1.1
ii  libfwupd2              1.3.4-1
ii  libgcab-1.0-0          1.3-1
ii  libglib2.0-0           2.62.3-2
ii  libgnutls30            3.6.11.1-2
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.3.1-3
ii  libxmlb1               0.1.14-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.4+1
ii  python3                            3.7.5-1

fwupd suggests no packages.

-- no debconf information

---

From: Ross Vandegrift <[email-masked]>
Date: Wed, 21 Apr 2021 15:54:02 -0700

Package: fwupd
Version: 1.5.7-3
Followup-For: Bug #943343
X-Debbugs-Cc: [email-masked]

I have a pair of laptops, one where fwupd-refresh.service is broken and one
where it works.  Both are running bullseye with the same versions of fwupd,
systemd, and dbus.  No remote users, nfs, freeipa, etc.

I've run both with this config:
  $ cat /etc/systemd/system/fwupd-refresh.service.d/override.conf
  [Service]
  StandardError=
  StandardError=journal
  ExecStart=
  ExecStart=/usr/bin/strace -ff /usr/bin/fwupdmgr -v refresh

The results aren't too enlightening - the broken one cannot auth to dbus as
it's systemd dynamic user:

  socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC, 0) = 7
  fcntl(7, F_GETFL)          = 0x2 (flags O_RDWR)
  fcntl(7, F_SETFL, O_RDWR|O_NONBLOCK) = 0
  connect(7, {sa_family=AF_UNIX, sun_path="/var/run/dbus/system_bus_socket"}, 110) = 0
  sendmsg(7, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0", iov_len=1}], msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS, cmsg_data={pid=128515, uid=62803, gid=62803}}], msg_controllen=32, msg_flags=0}, MSG_NOSIGNAL) = 1
  sendto(7, "AUTH\r\n", 6, MSG_NOSIGNAL, NULL, 0) = 6
  recvfrom(7, "REJECTED EXTERNAL\r\n", 4096, 0, NULL, NULL) = 19
  sendto(7, "AUTH EXTERNAL 3632383033\r\n", 26, MSG_NOSIGNAL, NULL, 0) = 26
  recvfrom(7, "REJECTED EXTERNAL\r\n", 4096, 0, NULL, NULL) = 19

I don't know why that would fail.  If I could provide more details or test
something, please let me know.

Ross

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (40, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
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.31-11
ii  libcurl3-gnutls        7.74.0-1.2
ii  libefiboot1            37-6
ii  libelf1                0.183-1
ii  libflashrom1           1.2-5
ii  libfwupd2              1.5.7-2
ii  libfwupdplugin1        1.5.7-2
ii  libglib2.0-0           2.66.8-1
ii  libgnutls30            3.7.1-3
ii  libgudev-1.0-0         234-1
ii  libgusb2               0.3.5-1
ii  libjcat1               0.1.3-2
ii  libjson-glib-1.0-0     1.6.2-1
ii  libpolkit-gobject-1-0  0.105-30
ii  libsmbios-c2           2.4.3-1
ii  libsqlite3-0           3.34.1-3
ii  libsystemd0            247.3-3
ii  libtss2-esys-3.0.2-0   3.0.3-2
ii  libxmlb1               0.1.15-2
ii  shared-mime-info       2.0-1

Versions of packages fwupd recommends:
ii  bolt                               0.9.1-1
ii  dbus                               1.12.20-2
ii  fwupd-amd64-signed [fwupd-signed]  1.5.7+3
ii  python3                            3.9.2-2
pn  secureboot-db                      <none>
ii  udisks2                            2.9.2-1

Versions of packages fwupd suggests:
pn  gir1.2-fwupd-2.0  <none>