>> Wi-Fi handling was significantly reworked. Please try the latest
>> version whether it still has the issue.
I was tested NM 1.28 and found it . but the problem was
automatically quickly recovered normal after the nm-dispatcher service
restarted .
Thomas Haller 于2021年2月8日周一 下午3:03写道:
>
> Hi,
>
Thanks for your notification and I have got that .
>> Look at all the logs by enabling level=TRACE level.
I used log-level=DEBUG
And This debug message with add into src/devices/nm-device.c from me .
```code
static void
_set_state_full (NMDevice *self,
NMDeviceState state,
NMDeviceStateReason re
Hi,
On Sun, 2021-02-07 at 11:53 +0800, Heysion Yuan via networkmanager-list
wrote:
>
> I found the NM didn't trigger scan_done probabilistically after S3 or
> S4 resume .
> I traced the NM do_sleep_wake is normal and trigger scan by dbus to
> wpa ,the wpa push scan result to dbus.
> but NM didn'
Hello all
I found the NM didn't trigger scan_done probabilistically after S3 or S4
resume .
I traced the NM do_sleep_wake is normal and trigger scan by dbus to wpa
,the wpa push scan result to dbus.
but NM didn't trigger scan_done signal and fetch scan result on dbus.
and I debug the device stat