[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1011511: marked as done (fwupd-refresh fails after resuming from suspend because network is not yet available)

Your message dated Fri, 22 Mar 2024 16:19:08 -0500
with message-id <b08c8417-3c20-41dc-8452-53d274ffbc1a@gmail.com>
and subject line 
has caused the Debian Bug report #1011511,
regarding fwupd-refresh fails after resuming from suspend because network is not yet available
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 owner@bugs.debian.org
immediately.)


-- 
1011511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011511
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: fwupd
Version: 1.7.7-1
Severity: normal
X-Debbugs-Cc: cquike@arcor.de

I see in my laptop frequent errors due to fwupd-refresh. It seems that after
resuming the latop from a suspend te fwupd-refresh service tries is run a few
seconds before the WIFI network has been activated.

I have confirmed that's in fact the case by greping in the logs:

$ journalctl -r | egrep "Failed to start Refresh fwupd|CONNECTED_GLOBAL|PM:
suspend exit"
may 24 10:14:38 hostname NetworkManager[692]: <info>  [1653380078.2772]
manager: NetworkManager state is now CONNECTED_GLOBAL
may 24 10:14:35 hostname systemd[1]: Failed to start Refresh fwupd metadata and
update motd.
may 24 10:14:34 hostname kernel: PM: suspend exit
may 23 20:10:17 hostname NetworkManager[130474]: <info>  [1653329417.5285]
manager: NetworkManager state is now CONNECTED_GLOBAL
may 23 20:10:13 hostname systemd[1]: Failed to start Refresh fwupd metadata and
update motd.
may 23 20:10:13 hostname kernel: PM: suspend exit
may 23 10:44:57 hostname NetworkManager[130474]: <info>  [1653295497.8153]
manager: NetworkManager state is now CONNECTED_GLOBAL
may 23 10:44:56 hostname systemd[1]: Failed to start Refresh fwupd metadata and
update motd.
may 23 10:44:53 hostname kernel: PM: suspend exit
may 21 22:00:36 hostname NetworkManager[130474]: <info>  [1653163236.3835]
manager: NetworkManager state is now CONNECTED_GLOBAL
may 21 22:00:33 hostname systemd[1]: Failed to start Refresh fwupd metadata and
update motd.
may 21 22:00:32 hostname kernel: PM: suspend exit
may 19 13:21:29 hostname NetworkManager[691]: <info>  [1652959289.3352]
manager: NetworkManager state is now CONNECTED_GLOBAL
may 19 13:21:27 hostname systemd[1]: Failed to start Refresh fwupd metadata and
update motd.
may 19 13:21:24 hostname kernel: PM: suspend exit
may 07 10:06:52 hostname NetworkManager[697]: <info>  [1651910812.4653]
manager: NetworkManager state is now CONNECTED_GLOBAL
may 07 10:06:51 hostname systemd[1]: Failed to start Refresh fwupd metadata and
update motd.
may 07 10:06:47 hostname kernel: PM: suspend exit
may 06 08:27:01 hostname NetworkManager[697]: <info>  [1651818421.6660]
manager: NetworkManager state is now CONNECTED_GLOBAL
may 06 08:26:57 hostname systemd[1]: Failed to start Refresh fwupd metadata and
update motd.
may 06 08:26:56 hostname kernel: PM: suspend exit
may 04 19:22:03 hostname NetworkManager[697]: <info>  [1651684923.3640]
manager: NetworkManager state is now CONNECTED_GLOBAL
may 04 19:22:02 hostname systemd[1]: Failed to start Refresh fwupd metadata and
update motd.
may 04 19:21:58 hostname kernel: PM: suspend exit
abr 30 17:11:46 hostname NetworkManager[697]: <info>  [1651331506.9056]
manager: NetworkManager state is now CONNECTED_GLOBAL
abr 30 17:11:45 hostname systemd[1]: Failed to start Refresh fwupd metadata and
update motd.
abr 30 17:11:42 hostname kernel: PM: suspend exit

(I have removed a few CONNECTED_GLOBAL unrelated to a resume from suspend)

As you see, in the last month, the secuence of the events are always the same:
system resumes from suspend (kernel: PM: suspend exit), fwupd fails and a few
seconds later the network is fully available (CONNECTED_GLOBAL).

If I restart the system manually (systemctl restart fwupd-refresh.service) then
it runs without problem.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
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-7
ii  libcurl3-gnutls        7.83.0-1
ii  libefiboot1            37-6
ii  libflashrom1           1.2-5
ii  libfwupd2              1.7.7-1
ii  libfwupdplugin5        1.7.7-1
ii  libglib2.0-0           2.72.1-1
ii  libgnutls30            3.7.4-2
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-2
ii  libpolkit-gobject-1-0  0.105-33
ii  libprotobuf-c1         1.3.3-1+b2
ii  libqmi-glib5           1.30.4-2
ii  libqmi-proxy           1.30.4-2
ii  libsmbios-c2           2.4.3-1
ii  libsqlite3-0           3.38.5-1
ii  libsystemd0            250.4-1
ii  libtss2-esys-3.0.2-0   3.2.0-1
ii  libxmlb2               0.3.8-1
ii  shared-mime-info       2.2-1

Versions of packages fwupd recommends:
ii  bolt                               0.9.2-1
ii  dbus                               1.14.0-1
ii  fwupd-amd64-signed [fwupd-signed]  1:1.2+3
ii  python3                            3.10.4-1+b1
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 ---
Reply to: