However, it usually requires a suspend cycle over night to trigger this bug anyway - so I will report back tomorrow.
(I was rather surprised that it was triggered in my last attempt)
Where is the PrepareForSleep=false signal emitted and what is it supposed to do?
Is it something NetworkManager requires to wake up again?
With the normal suspend methd, PrepareForSleep =false showed up now (and the network came up again), (together with PrepareForSleep =true):
signal sender=:1.3 -> dest=(null destination) serial=1094 path=/org/ freedesktop/ login1; org.freedesktop .login1. Manager; member= PrepareForSleep
interface=
boolean false
However, it usually requires a suspend cycle over night to trigger this bug anyway - so I will report back tomorrow.
(I was rather surprised that it was triggered in my last attempt)
Where is the PrepareForSleep =false signal emitted and what is it supposed to do?
Is it something NetworkManager requires to wake up again?