Your message dated Fri, 22 Mar 2024 16:19:08 -0500
with message-id <[email protected]>
and subject line
has caused the Debian Bug report #1006484,
regarding fwupd-refresh service is launched after resuming laptop _before_ the
network is alive
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1006484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006484
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fwupd
Version: 1.7.5-3
Severity: normal
X-Debbugs-Cc: [email protected]
I see that everytime I resume my laptop after suspending there are some errors
reported by journalctl:
feb 07 20:07:59 systemd[1]: fwupd-refresh.service: Main process exited,
code=exited, status=1/FAILURE
feb 07 20:07:59 systemd[1]: fwupd-refresh.service: Failed with result 'exit-
code'.
feb 07 20:07:59 systemd[1]: Failed to start Refresh fwupd metadata and update
motd.
One second after that the WIFI connection is established. That seems to be
consistent in all the cases I could see, so my assumption is that the fwupd-
refresh service is launched before the network connection is re-established.
On an additional side note, the last message ("Failed to start...") is marked
with priority 3 in journalctl and highlighted in red. I don't really know which
is the policy for system priority logs, but it looks to me that 3 is a bit
high, since it is at the same level as security messages and kernel hardware
issues.
Regards
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.16.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8),
LANGUAGE=es_ES:es
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fwupd depends on:
ii libc6 2.33-6
ii libcurl3-gnutls 7.81.0-1
ii libefiboot1 37-6
ii libflashrom1 1.2-5
ii libfwupd2 1.7.5-3
ii libfwupdplugin5 1.7.5-3
ii libglib2.0-0 2.70.4-1
ii libgnutls30 3.7.3-4+b1
ii libgudev-1.0-0 237-2
ii libgusb2 0.3.10-1
ii libjcat1 0.1.9-1
ii libjson-glib-1.0-0 1.6.6-1
ii libmbim-glib4 1.26.2-1
ii libmbim-proxy 1.26.2-1
ii libmm-glib0 1.18.6-1
ii libpolkit-gobject-1-0 0.105-32
ii libprotobuf-c1 1.3.3-1+b2
ii libqmi-glib5 1.30.4-1
ii libqmi-proxy 1.30.4-1
ii libsmbios-c2 2.4.3-1
ii libsqlite3-0 3.37.2-2
ii libsystemd0 250.3-2
ii libtss2-esys-3.0.2-0 3.1.0-3
ii libxmlb2 0.3.6-2
ii shared-mime-info 2.1-2
Versions of packages fwupd recommends:
ii bolt 0.9.2-1
ii dbus 1.12.20-3
ii fwupd-amd64-signed [fwupd-signed] 1:1.2+3
ii python3 3.9.8-1
pn secureboot-db <none>
ii udisks2 2.9.4-1
Versions of packages fwupd suggests:
pn gir1.2-fwupd-2.0 <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
This should be fixed in fwupd 1.8.5 and later.
https://github.com/fwupd/fwupd/commit/fe5d93f7d2712f3b708e562a5f7e9be897e04d1d
--- End Message ---
