[Pkg-utopia-maintainers] Bug#969319: Bug#969319: wifi cannot connect after combined suspend & gateway reboot
Lyndon Brown
jnqnfe at gmail.com
Sat Sep 5 12:22:16 BST 2020
On Mon, 2020-08-31 at 14:02 +0200, Michael Biebl wrote:
> Am 31.08.20 um 12:22 schrieb Lyndon Brown:
> > Package: network-manager
> > Version: 1.26.2-1
> > Severity: important
> >
> > I'm on Debian Sid, with network manager configured to use iwd. I
> > have
> > an Intel AX200 wifi card.
> >
>
> Can you reproduce that with wpasupplicant?
short answer no.
details of hours of experimentation today follows...
firstly, i forgot previously to mention that it's a hidden network.
also, it can be noted that the other day i tried leaving the gateway on
over night for a change, while leaving the laptop sleeping (lid shut),
and when i returned to it the next day, it successfully reconnected. so
time left sleeping does not seem to be a particularly significant
factor, whilst the gateway being off for a while during that sleep
definitely does.
however, i've been doing that for the past few days now, and today
experienced the same connection failure, despite the gateway having
remained on the entire time. (unless there was a power cut while i
slept i guess; i didn't check). so that's interesting.
since that has forced me to close down all of the work i'm in the
middle of (which is why i'm leaving it sleeping) for a reboot, i've
taken the opportunity to investigate further as asked...
firstly i felt the need to test reproducibility before any switch to
wpa_supplicant.
so i started off doing the following:
1. rebooted and logged in.
2. it connected automatically and i took the opportunity to install
package updates.
3. i shut the lid and waited for approximately one minute.
4. turned off the gateway and waited for approximately one minute.
5. turned the gateway back on and waited for approximately one and a
half minutes.
6. opened the lid of the laptop and unlocked it.
unfortunately it had no issue reconnecting (which it did
automatically).
dmesg output:
```
[ 362.938616] PM: suspend exit
[ 364.687381] wlan0: authenticate with «MAC»
[ 364.691259] wlan0: send auth to «MAC» (try 1/3)
[ 365.590534] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 365.590626] wlan0: Connection to AP «MAC» lost
[ 366.175547] wlan0: send auth to «MAC» (try 2/3)
[ 366.183586] wlan0: authenticated
[ 366.183659] wlan0: associating with AP with corrupt probe response
[ 366.186737] wlan0: associate with «MAC» (try 1/3)
[ 366.198772] wlan0: RX AssocResp from «MAC» (capab=0x411 status=0
aid=1)
[ 366.214860] wlan0: associated
[ 366.512295] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
```
so although it did not connect exactly cleanly, it still connected.
perhaps there's a time factor and i need to leave it for longer?
so i tried again, this time with the following differences:
1. directly locked the desktop first (win+l)
2. did not reboot since the last experiment
3. expanded the time periods from parts 3-5 of the previous experiment
to 3min, 5min and 3min respectively.
having returned to the laptop, this time it's not automatically
reconnected. good.
dmesg:
```
[ 1776.902728] PM: suspend exit
[ 1778.750632] wlan0: authenticate with «MAC»
[ 1778.753331] wlan0: send auth to «MAC» (try 1/3)
[ 1779.321626] wlan0: send auth to «MAC» (try 2/3)
[ 1780.220436] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1780.220475] wlan0: Connection to AP «MAC» lost
[ 1780.281716] wlan0: send auth to «MAC» (try 3/3)
[ 1781.180748] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1781.180849] wlan0: Connection to AP «MAC» lost
[ 1781.304939] wlan0: authentication with «MAC» timed out
```
explicitly selecting the network fails, ah but damn, turning it off
then back on it's now successfully connected, which is not what has
been happening previously.
```
[ 1776.902728] PM: suspend exit
[ 1778.750632] wlan0: authenticate with «MAC»
[ 1778.753331] wlan0: send auth to «MAC» (try 1/3)
[ 1779.321626] wlan0: send auth to «MAC» (try 2/3)
[ 1780.220436] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1780.220475] wlan0: Connection to AP «MAC» lost
[ 1780.281716] wlan0: send auth to «MAC» (try 3/3)
[ 1781.180748] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1781.180849] wlan0: Connection to AP «MAC» lost
[ 1781.304939] wlan0: authentication with «MAC» timed out
[ 1978.199366] wlan0: authenticate with «MAC»
[ 1978.204215] wlan0: send auth to «MAC» (try 1/3)
[ 1979.103492] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1979.103593] wlan0: Connection to AP «MAC» lost
[ 1979.322185] wlan0: send auth to «MAC» (try 2/3)
[ 1980.221124] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1980.221207] wlan0: Connection to AP «MAC» lost
[ 1980.282051] wlan0: send auth to «MAC» (try 3/3)
[ 1981.181057] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1981.181101] wlan0: Connection to AP «MAC» lost
[ 1981.273205] wlan0: authentication with «MAC» timed out
[ 2019.275680] wlan0: authenticate with «MAC»
[ 2019.281234] wlan0: send auth to «MAC» (try 1/3)
[ 2019.314404] wlan0: authenticated
[ 2019.314427] wlan0: associating with AP with corrupt probe response
[ 2019.316979] wlan0: associate with «MAC» (try 1/3)
[ 2019.334886] wlan0: RX AssocResp from «MAC» (capab=0x411 status=0
aid=1)
[ 2019.351335] wlan0: associated
[ 2019.895411] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
```
so next up i tried a third experiment:
1. rebooted and logged in.
2. directly locked the desktop shortly after.
3. repeated the sleep experiment with the 3min, 5min, 3min pattern.
again, it tried to auto connect whilst logging back in but failed.
though this is the only dmesg output:
```
[ 734.056338] PM: suspend exit
[ 735.910400] wlan0: authenticate with «MAC»
[ 735.914592] wlan0: send auth to «MAC» (try 1/3)
[ 735.945697] wlan0: authenticated
[ 735.945724] wlan0: associating with AP with corrupt probe response
[ 735.946032] wlan0: associate with «MAC» (try 1/3)
[ 735.948653] wlan0: RX AssocResp from «MAC» (capab=0x411 status=0
aid=1)
[ 735.964969] wlan0: associated
[ 740.965512] wlan0: deauthenticating from «MAC» by local choice
(Reason: 15=4WAY_HANDSHAKE_TIMEOUT)
```
manually selecting the network from the list gnome provides, i got an
authentication-needed prompt, with my password pre-filled, which has
happened once before recently. on that past occurance it connected fine
afterwards, but this time the connection failed due to the sleeping
issue being investigated.
checking dmesg again:
```
[ 734.056338] PM: suspend exit
[ 735.910400] wlan0: authenticate with «MAC»
[ 735.914592] wlan0: send auth to «MAC» (try 1/3)
[ 735.945697] wlan0: authenticated
[ 735.945724] wlan0: associating with AP with corrupt probe response
[ 735.946032] wlan0: associate with «MAC» (try 1/3)
[ 735.948653] wlan0: RX AssocResp from «MAC» (capab=0x411 status=0
aid=1)
[ 735.964969] wlan0: associated
[ 740.965512] wlan0: deauthenticating from «MAC» by local choice
(Reason: 15=4WAY_HANDSHAKE_TIMEOUT)
[ 1025.229046] wlan0: authenticate with «MAC»
[ 1025.234014] wlan0: send auth to «MAC» (try 1/3)
[ 1025.274375] wlan0: authenticated
[ 1025.275271] wlan0: associating with AP with corrupt probe response
[ 1025.278266] wlan0: associate with «MAC» (try 1/3)
[ 1025.288095] wlan0: RX AssocResp from «MAC» (capab=0x411 status=0
aid=1)
[ 1025.300724] wlan0: associated
[ 1029.143152] wlan0: deauthenticated from «MAC» (Reason:
15=4WAY_HANDSHAKE_TIMEOUT)
```
so strangely none of the previous output about connection issues.
i played around a little with iwctl, journalctl and iwmon to see what
helpful info these could possibly provide, and ultimately several
minutes later tried selecting the network manually again, and this time
it connected successfully. remember, the state at this point was that
although it had failed to connect, the dmesg output was different to
earlier. also, at this time, the wifi icon has a '?' on it.
so repeating the sleep experiment again for the same periods without
rebooting, results in failed connect and the original dmesg output. so
it seems roughly reliably reproducable, with sufficient time periods,
and after a couple of such sleep cycles after reboot.
`journalctl -u iwd.service` output for today so far:
```
Sep 05 02:47:13 <host> iwd[44267]: Received error during
CMD_TRIGGER_SCAN: Network is down (100)
Sep 05 08:13:46 <host> iwd[44267]: authentication timed out
Sep 05 08:14:30 <host> iwd[44267]: authentication timed out
Sep 05 08:15:10 <host> iwd[44267]: authentication timed out
Sep 05 08:16:46 <host> iwd[44267]: authentication timed out
Sep 05 08:27:00 <host> iwd[44267]: authentication timed out
Sep 05 08:27:22 <host> iwd[44267]: authentication timed out
Sep 05 08:29:23 <host> iwd[44267]: authentication timed out
Sep 05 08:29:49 <host> iwd[44267]: authentication timed out
Sep 05 08:30:17 <host> iwd[44267]: authentication timed out
Sep 05 08:33:27 <host> systemd[1]: Stopping Wireless service...
Sep 05 08:33:27 <host> iwd[44267]: Terminate
Sep 05 08:33:27 <host> iwd[44267]: Removing scan context for wdev 4
Sep 05 08:33:27 <host> iwd[44267]: D-Bus disconnected, quitting...
Sep 05 08:33:28 <host> iwd[44267]: Removing scan context for wdev 5
Sep 05 08:33:28 <host> systemd[1]: iwd.service: Succeeded.
Sep 05 08:33:28 <host> systemd[1]: Stopped Wireless service.
-- Reboot --
Sep 05 08:34:16 <host> systemd[1]: Starting Wireless service...
Sep 05 08:34:17 <host> iwd[687]: Wireless daemon version 1.8
Sep 05 08:34:17 <host> systemd[1]: Started Wireless service.
Sep 05 08:34:17 <host> iwd[687]: station: Network configuration is
disabled.
Sep 05 08:34:17 <host> iwd[687]: Wiphy: 0, Name: phy0
Sep 05 08:34:17 <host> iwd[687]: Permanent Address:
84:c5:a6:dc:6f:ef
Sep 05 08:34:17 <host> iwd[687]: Bands: 2.4 GHz 5 GHz
Sep 05 08:34:17 <host> iwd[687]: Ciphers: CCMP TKIP BIP
Sep 05 08:34:17 <host> iwd[687]: Supported iftypes: ad-hoc
station ap p2p-client p2p-go p2p-device
Sep 05 08:52:15 <host> iwd[687]: Received error during
CMD_TRIGGER_SCAN: Network is down (100)
Sep 05 09:03:32 <host> iwd[687]: authentication timed out
Sep 05 09:06:52 <host> iwd[687]: authentication timed out
Sep 05 09:11:23 <host> iwd[687]: Received Deauthentication event,
reason: 3, from_ap: false
Sep 05 09:11:23 <host> iwd[687]: Received error during
CMD_TRIGGER_SCAN: Network is down (100)
Sep 05 09:14:36 <host> iwd[687]: Received Deauthentication event,
reason: 3, from_ap: false
Sep 05 09:31:53 <host> systemd[1]: Stopping Wireless service...
Sep 05 09:31:53 <host> iwd[687]: Terminate
Sep 05 09:31:53 <host> iwd[687]: Removing scan context for wdev 2
Sep 05 09:31:53 <host> iwd[687]: D-Bus disconnected, quitting...
Sep 05 09:31:54 <host> iwd[687]: Removing scan context for wdev 3
Sep 05 09:31:54 <host> systemd[1]: iwd.service: Succeeded.
Sep 05 09:31:54 <host> systemd[1]: Stopped Wireless service.
-- Reboot --
Sep 05 09:32:46 <host> systemd[1]: Starting Wireless service...
Sep 05 09:32:47 <host> iwd[758]: Wireless daemon version 1.8
Sep 05 09:32:47 <host> systemd[1]: Started Wireless service.
Sep 05 09:32:47 <host> iwd[758]: station: Network configuration is
disabled.
Sep 05 09:32:47 <host> iwd[758]: Wiphy: 0, Name: phy0
Sep 05 09:32:47 <host> iwd[758]: Permanent Address:
84:c5:a6:dc:6f:ef
Sep 05 09:32:47 <host> iwd[758]: Bands: 2.4 GHz 5 GHz
Sep 05 09:32:47 <host> iwd[758]: Ciphers: CCMP TKIP BIP
Sep 05 09:32:47 <host> iwd[758]: Supported iftypes: ad-hoc
station ap p2p-client p2p-go p2p-device
Sep 05 09:44:35 <host> iwd[758]: 4-Way handshake failed for ifindex: 3,
reason: 15
Sep 05 09:49:23 <host> iwd[758]: Received Deauthentication event,
reason: 15, from_ap: true
Sep 05 10:16:46 <host> iwd[758]: authentication timed out
```
under iwctl, the network is listed under the known-networks list
command.
damn, i started capturing iwmon output while manually selecting the
network, expecting it to thus capture the failure, but unfortunately it
actually successfully connected. i'd done nothing special, just typed
up more of this report and collected the info just given.
okay, trying wpasupplicant...
1. sudo rm /etc/NetworkManager/conf.d/iwd.conf
2. sudo systemctl unmask wpa_supplicant
3. sudo aptitude remove iwd
4. rebooted
5. sorted out setting up the connection: (selecting it asked for the
password, which it did not already have stored this time). a new 'foo
1' entry was created in the list. i told it to forget the old one. i
had to wait for several moments of a twirling progress icon before
things settled down as it got a connection and i was able to apply my
custom dns settings.
6. rebooted to get a fresh start.
and of course, FFS, no autoconnection, and looking in the list of
connections available, my network isn't even there. so i'm going to
have to re-add it from scratch...
oh, so going to add the hidden network, a 'connection' dropbox had my
'foo 1' entry, which i could just select... it gave the password prompt
with pre-filled password. connecting... connecting... connecting...
taking it's damn time, finally connected. my custom dns settings are
already there, good. okay, let's experiment...
okay, so repeated the sleep experiment (now obviously under
wpa_supplicant if you're following me properly), and it automatically
reconnected successfully.
dmesg:
```
[ 957.150695] PM: suspend exit
[ 963.129984] wlp58s0: authenticate with «MAC»
[ 963.138051] wlp58s0: send auth to «MAC» (try 1/3)
[ 964.037239] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 964.037281] wlp58s0: Connection to AP «MAC» lost
[ 964.369050] wlp58s0: send auth to «MAC» (try 2/3)
[ 965.268092] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 965.268136] wlp58s0: Connection to AP «MAC» lost
[ 965.361083] wlp58s0: send auth to «MAC» (try 3/3)
[ 966.259808] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 966.259844] wlp58s0: Connection to AP «MAC» lost
[ 966.352156] wlp58s0: authentication with «MAC» timed out
[ 972.870772] wlp58s0: authenticate with «MAC»
[ 972.879033] wlp58s0: send auth to «MAC» (try 1/3)
[ 973.778182] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 973.778271] wlp58s0: Connection to AP «MAC» lost
[ 974.352628] wlp58s0: send auth to «MAC» (try 2/3)
[ 975.251652] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 975.251697] wlp58s0: Connection to AP «MAC» lost
[ 975.376930] wlp58s0: send auth to «MAC» (try 3/3)
[ 976.276118] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 976.276173] wlp58s0: Connection to AP «MAC» lost
[ 976.368200] wlp58s0: authentication with «MAC» timed out
[ 979.150288] wlp58s0: authenticate with «MAC»
[ 979.157890] wlp58s0: send auth to «MAC» (try 1/3)
[ 979.961377] wlp58s0: authenticated
[ 979.961921] wlp58s0: associating with AP with corrupt probe response
[ 979.964032] wlp58s0: associate with «MAC» (try 1/3)
[ 979.976254] wlp58s0: RX AssocResp from «MAC» (capab=0x411 status=0
aid=1)
[ 979.994578] wlp58s0: associated
[ 980.530576] IPv6: ADDRCONF(NETDEV_CHANGE): wlp58s0: link becomes
ready
```
so the same error entries are appearing, but it managed to get
connected anyway.
okay, repeating with a second sleep cycle... and okay, so it
automatically tried to connect, taking it's time, gave a failed
connection popup, but then immediately tried again and was successful.
dmesg:
```
[ 1884.328344] PM: suspend exit
[ 1890.500115] wlp58s0: authenticate with «MAC»
[ 1890.504863] wlp58s0: send auth to «MAC» (try 1/3)
[ 1891.404284] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1891.404369] wlp58s0: Connection to AP «MAC» lost
[ 1891.857678] wlp58s0: send auth to «MAC» (try 2/3)
[ 1892.756659] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1892.756754] wlp58s0: Connection to AP «MAC» lost
[ 1892.817638] wlp58s0: send auth to «MAC» (try 3/3)
[ 1893.716682] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1893.716768] wlp58s0: Connection to AP «MAC» lost
[ 1893.808719] wlp58s0: authentication with «MAC» timed out
[ 1894.732275] wlp58s0: authenticate with «MAC»
[ 1894.738922] wlp58s0: send auth to «MAC» (try 1/3)
[ 1895.638323] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1895.638412] wlp58s0: Connection to AP «MAC» lost
[ 1895.857610] wlp58s0: send auth to «MAC» (try 2/3)
[ 1896.756594] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1896.756680] wlp58s0: Connection to AP «MAC» lost
[ 1896.849574] wlp58s0: send auth to «MAC» (try 3/3)
[ 1897.748432] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1897.748448] wlp58s0: Connection to AP «MAC» lost
[ 1897.840637] wlp58s0: authentication with «MAC» timed out
[ 1898.946703] wlp58s0: authenticate with «MAC»
[ 1898.953690] wlp58s0: send auth to «MAC» (try 1/3)
[ 1899.825237] wlp58s0: send auth to «MAC» (try 2/3)
[ 1900.724347] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1900.724390] wlp58s0: Connection to AP «MAC» lost
[ 1900.817463] wlp58s0: send auth to «MAC» (try 3/3)
[ 1901.716507] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1901.716549] wlp58s0: Connection to AP «MAC» lost
[ 1901.840507] wlp58s0: authentication with «MAC» timed out
[ 1905.107473] wlp58s0: authenticate with «MAC»
[ 1905.113984] wlp58s0: send auth to «MAC» (try 1/3)
[ 1905.841223] wlp58s0: send auth to «MAC» (try 2/3)
[ 1906.740336] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1906.740378] wlp58s0: Connection to AP «MAC» lost
[ 1906.833226] wlp58s0: send auth to «MAC» (try 3/3)
[ 1907.732316] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 1907.732360] wlp58s0: Connection to AP «MAC» lost
[ 1907.824346] wlp58s0: authentication with «MAC» timed out
[ 1915.924433] wlp58s0: authenticate with «MAC»
[ 1915.931576] wlp58s0: send auth to «MAC» (try 1/3)
[ 1915.956539] wlp58s0: authenticated
[ 1915.956817] wlp58s0: associating with AP with corrupt probe response
[ 1915.960151] wlp58s0: associate with «MAC» (try 1/3)
[ 1915.964527] wlp58s0: RX AssocResp from «MAC» (capab=0x411 status=0
aid=1)
[ 1915.982792] wlp58s0: associated
[ 1916.839084] IPv6: ADDRCONF(NETDEV_CHANGE): wlp58s0: link becomes
ready
```
switching back to iwd:
1. recreated the config file
2. remasked wpa_supplicant
3. rebooted
4. remembered that i needed to reinstall iwd, did so
5. rebooted
in wifi connections, told it to forget 'foo 1', 'foo' then reappeared.
so i tried editing it to apply my custom dns, which it did not have set
for some reason, but having filled them in, the 'apply' button is still
disabled... closing that, now 'foo' has disappeared from the list...
damn it NM...
add hidden network, was able to select 'foo', though it does not know
the password, and oh, the fields are disabled so i can't actually
supply it... HUH?
had to forget it from the 'known networks' list and then completely re-
add it.
And it just fails to connect (I know the details are correct, i'd
copied and pasted them...) nothing in dmesg about that...
some possibly relevant `journalctl -b 0` output:
```
Sep 05 11:19:10 <host> NetworkManager[782]: <info> [1599301150.4326]
audit: op="connection-activate" uuid="uuid1" name="Foo 1" pid=1997
uid=1000 result>
Sep 05 11:19:19 <host> gnome-control-c[1997]: ((libnm/nm-access-
point.c:145)): assertion '<dropped>' failed
Sep 05 11:19:21 <host> NetworkManager[782]: <info> [1599301161.2891]
audit: op="connection-delete" uuid="uuid1" name="Foo 1" pid=1997
uid=1000 result=">
Sep 05 11:19:23 <host> NetworkManager[782]: <info> [1599301163.6207]
device (wlan0): Activation: starting connection 'Foo' (<snip>)
Sep 05 11:19:23 <host> NetworkManager[782]: <info> [1599301163.6209]
audit: op="connection-add-activate" uuid="<snip>" name="Foo" pid=1997
uid=1000 resu>
Sep 05 11:19:23 <host> NetworkManager[782]: <info> [1599301163.6218]
device (wlan0): state change: disconnected -> prepare (reason 'none',
sys-iface-state: 'managed')
Sep 05 11:19:23 <host> NetworkManager[782]: <info> [1599301163.6226]
manager: NetworkManager state is now CONNECTING
Sep 05 11:19:23 <host> NetworkManager[782]: <info> [1599301163.6234]
device (wlan0): state change: prepare -> config (reason 'none', sys-
iface-state: 'managed')
Sep 05 11:19:23 <host> NetworkManager[782]: <info> [1599301163.6432]
device (wlan0): state change: config -> need-auth (reason 'no-secrets',
sys-iface-state: 'managed')
Sep 05 11:19:25 <host> NetworkManager[782]: <warn> [1599301165.6060]
device (wlan0): User canceled the secrets request.
Sep 05 11:19:25 <host> NetworkManager[782]: <error> [1599301165.6080]
device (wlan0): Activation: (wifi) Network.Connect failed:
GDBus.Error:net.connman.iwd.Aborted: Operation aborted
Sep 05 11:19:25 <host> NetworkManager[782]: <info> [1599301165.6094]
device (wlan0): state change: need-auth -> failed (reason 'no-secrets',
sys-iface-state: 'managed')
Sep 05 11:19:25 <host> NetworkManager[782]: <info> [1599301165.6114]
manager: NetworkManager state is now DISCONNECTED
Sep 05 11:19:25 <host> NetworkManager[782]: <warn> [1599301165.6182]
device (wlan0): Activation: failed for connection 'Foo'
Sep 05 11:19:25 <host> NetworkManager[782]: <info> [1599301165.6216]
device (wlan0): state change: failed -> disconnected (reason 'none',
sys-iface-state: 'managed')
Sep 05 11:19:25 <host> gnome-shell[1669]: An active wireless
connection, in infrastructure mode, involves no access point?
Sep 05 11:19:25 <host> gnome-shell[1669]: An active wireless
connection, in infrastructure mode, involves no access point?
Sep 05 11:19:28 <host> systemd[1528]: gnome-launched-gnome-wifi-
panel.desktop-1997.scope: Succeeded.
Sep 05 11:19:29 <host> gnome-shell[1669]: ../clutter/clutter/clutter-
actor.c:10556: The clutter_actor_set_allocation() function can only be
called from within the implementation of the ClutterActo>
Sep 05 11:19:32 <host> NetworkManager[782]: <info> [1599301172.0826]
manager: rfkill: Wi-Fi hardware radio set disabled
Sep 05 11:19:32 <host> NetworkManager[782]: <info> [1599301172.0860]
device (wlan0): state change: disconnected -> unavailable (reason
'none', sys-iface-state: 'managed')
Sep 05 11:19:32 <host> systemd[1]: Starting Load/Save RF Kill Switch
Status...
Sep 05 11:19:32 <host> NetworkManager[782]: <info> [1599301172.0955]
audit: op="radio-control" arg="wireless-enabled" pid=1669 uid=1000
result="success"
Sep 05 11:19:32 <host> NetworkManager[782]: <info> [1599301172.0974]
manager: rfkill: Wi-Fi now disabled by radio killswitch
Sep 05 11:19:32 <host> systemd[1]: Started Load/Save RF Kill Switch
Status.
Sep 05 11:19:32 <host> gnome-shell[1669]: ../clutter/clutter/clutter-
actor.c:10556: The clutter_actor_set_allocation() function can only be
called from within the implementation of the ClutterActo>
Sep 05 11:19:34 <host> NetworkManager[782]: <info> [1599301174.5839]
manager: rfkill: Wi-Fi hardware radio set enabled
Sep 05 11:19:34 <host> NetworkManager[782]: <info> [1599301174.5855]
audit: op="radio-control" arg="wireless-enabled" pid=1669 uid=1000
result="success"
Sep 05 11:19:34 <host> NetworkManager[782]: <info> [1599301174.5894]
manager: rfkill: Wi-Fi now enabled by radio killswitch
Sep 05 11:19:34 <host> NetworkManager[782]: <info> [1599301174.8062]
device (wlan0): new IWD device state is disconnected
Sep 05 11:19:34 <host> NetworkManager[782]: <info> [1599301174.8069]
device (wlan0): state change: unavailable -> disconnected (reason
'supplicant-available', sys-iface-state: 'managed')
Sep 05 11:19:35 <host> gnome-shell[1669]: ../clutter/clutter/clutter-
actor.c:10556: The clutter_actor_set_allocation() function can only be
called from within the implementation of the ClutterActo>
Sep 05 11:19:39 <host> systemd[1]: systemd-rfkill.service: Succeeded.
Sep 05 11:19:43 <host> gnome-control-c[2093]: ((libnm/nm-access-
point.c:145)): assertion '<dropped>' failed
Sep 05 11:25:15 <host> gnome-shell[1669]: ../clutter/clutter/clutter-
actor.c:10556: The clutter_actor_set_allocation() function can only be
called from within the implementation of the ClutterActo>
Sep 05 11:25:17 <host> NetworkManager[782]: <info> [1599301517.1840]
manager: rfkill: Wi-Fi hardware radio set disabled
Sep 05 11:25:17 <host> NetworkManager[782]: <info> [1599301517.1841]
device (wlan0): state change: disconnected -> unavailable (reason
'none', sys-iface-state: 'managed')
Sep 05 11:25:17 <host> NetworkManager[782]: <info> [1599301517.1846]
audit: op="radio-control" arg="wireless-enabled" pid=1669 uid=1000
result="success"
Sep 05 11:25:17 <host> systemd[1]: Starting Load/Save RF Kill Switch
Status...
Sep 05 11:25:17 <host> NetworkManager[782]: <info> [1599301517.1892]
manager: rfkill: Wi-Fi now disabled by radio killswitch
Sep 05 11:25:17 <host> systemd[1]: Started Load/Save RF Kill Switch
Status.
Sep 05 11:25:17 <host> gnome-shell[1669]: ../clutter/clutter/clutter-
actor.c:10556: The clutter_actor_set_allocation() function can only be
called from within the implementation of the ClutterActo>
Sep 05 11:25:19 <host> NetworkManager[782]: <info> [1599301519.6642]
manager: rfkill: Wi-Fi hardware radio set enabled
Sep 05 11:25:19 <host> NetworkManager[782]: <info> [1599301519.6645]
audit: op="radio-control" arg="wireless-enabled" pid=1669 uid=1000
result="success"
Sep 05 11:25:19 <host> NetworkManager[782]: <info> [1599301519.6656]
manager: rfkill: Wi-Fi now enabled by radio killswitch
Sep 05 11:25:19 <host> NetworkManager[782]: <info> [1599301519.8693]
device (wlan0): new IWD device state is disconnected
Sep 05 11:25:19 <host> NetworkManager[782]: <info> [1599301519.8695]
device (wlan0): state change: unavailable -> disconnected (reason
'supplicant-available', sys-iface-state: 'managed')
Sep 05 11:25:37 <host> systemd[1528]: gnome-launched-gnome-wifi-
panel.desktop-2093.scope: Succeeded.
Sep 05 11:25:38 <host> gnome-shell[1669]: ../clutter/clutter/clutter-
actor.c:10556: The clutter_actor_set_allocation() function can only be
called from within the implementation of the ClutterActo>
Sep 05 11:25:55 <host> gnome-control-c[2645]: ((libnm/nm-access-
point.c:145)): assertion '<dropped>' failed
Sep 05 11:26:06 <host> gnome-control-c[2645]: ((libnm/nm-access-
point.c:145)): assertion '<dropped>' failed
Sep 05 11:26:07 <host> NetworkManager[782]: <info> [1599301567.8564]
audit: op="connection-delete" uuid="<snip>" name="Foo" pid=2645
uid=1000 result="su>
Sep 05 11:26:57 <host> NetworkManager[782]: <info> [1599301617.8447]
device (wlan0): Activation: starting connection 'Foo' (838cc3c5-4ce5-
452c-be1e-fbb364a24525)
Sep 05 11:26:57 <host> NetworkManager[782]: <info> [1599301617.8449]
audit: op="connection-add-activate" uuid="838cc3c5-4ce5-452c-be1e-
fbb364a24525" name="Foo" pid=2645 uid=1000 resu>
Sep 05 11:26:57 <host> NetworkManager[782]: <info> [1599301617.8457]
device (wlan0): state change: disconnected -> prepare (reason 'none',
sys-iface-state: 'managed')
Sep 05 11:26:57 <host> NetworkManager[782]: <info> [1599301617.8466]
manager: NetworkManager state is now CONNECTING
Sep 05 11:26:57 <host> NetworkManager[782]: <info> [1599301617.8482]
device (wlan0): state change: prepare -> config (reason 'none', sys-
iface-state: 'managed')
Sep 05 11:26:57 <host> NetworkManager[782]: <warn> [1599301617.8490]
device (wlan0): Activation: (wifi) network is provisioned but dbus
supplicant path for AP unknown
Sep 05 11:26:57 <host> NetworkManager[782]: <info> [1599301617.8498]
device (wlan0): state change: config -> failed (reason 'supplicant-
failed', sys-iface-state: 'managed')
Sep 05 11:26:57 <host> NetworkManager[782]: <info> [1599301617.8505]
manager: NetworkManager state is now DISCONNECTED
Sep 05 11:26:57 <host> NetworkManager[782]: <warn> [1599301617.8518]
device (wlan0): Activation: failed for connection 'Foo'
Sep 05 11:26:57 <host> NetworkManager[782]: <info> [1599301617.8527]
device (wlan0): state change: failed -> disconnected (reason 'none',
sys-iface-state: 'managed')
Sep 05 11:26:57 <host> gnome-control-c[2645]: Failed to add new
connection: (2) request succeeded with
/org/freedesktop/NetworkManager/ActiveConnection/2 but object is in an
unsuitable state
Sep 05 11:27:17 <host> NetworkManager[782]: <info> [1599301637.7429]
device (wlan0): Activation: starting connection 'Foo' (838cc3c5-4ce5-
452c-be1e-fbb364a24525)
Sep 05 11:27:17 <host> NetworkManager[782]: <info> [1599301637.7434]
audit: op="connection-activate" uuid="838cc3c5-4ce5-452c-be1e-
fbb364a24525" name="Foo" pid=2645 uid=1000 result=">
Sep 05 11:27:17 <host> NetworkManager[782]: <info> [1599301637.7440]
device (wlan0): state change: disconnected -> prepare (reason 'none',
sys-iface-state: 'managed')
Sep 05 11:27:17 <host> NetworkManager[782]: <info> [1599301637.7457]
manager: NetworkManager state is now CONNECTING
Sep 05 11:27:17 <host> NetworkManager[782]: <info> [1599301637.7506]
device (wlan0): state change: prepare -> config (reason 'none', sys-
iface-state: 'managed')
Sep 05 11:27:17 <host> NetworkManager[782]: <warn> [1599301637.7523]
device (wlan0): Activation: (wifi) network is provisioned but dbus
supplicant path for AP unknown
Sep 05 11:27:17 <host> NetworkManager[782]: <info> [1599301637.7547]
device (wlan0): state change: config -> failed (reason 'supplicant-
failed', sys-iface-state: 'managed')
Sep 05 11:27:17 <host> NetworkManager[782]: <info> [1599301637.7595]
manager: NetworkManager state is now DISCONNECTED
Sep 05 11:27:17 <host> NetworkManager[782]: <warn> [1599301637.7618]
device (wlan0): Activation: failed for connection 'Foo'
Sep 05 11:27:17 <host> NetworkManager[782]: <info> [1599301637.7627]
device (wlan0): state change: failed -> disconnected (reason 'none',
sys-iface-state: 'managed')
Sep 05 11:27:17 <host> gnome-shell[1669]: An active wireless
connection, in infrastructure mode, involves no access point?
Sep 05 11:27:17 <host> gnome-shell[1669]: An active wireless
connection, in infrastructure mode, involves no access point?
```
going to try rebooting... okay, after a reboot, i had to select it
again via add-hidden-network, clicking connect brought up a password
prompt, pre-filled with the password, clicking connect on that worked.
i then was able to successfully apply my custom dns settings and
rebooted once more to ensure they took effect. it seems to be happily
connected again.
something else to point out that i encountered during all of this,
there was a significant issue in the GUI of the wifi settings when
editing a connection. for some reason the dialog was much shorter in
height, with overlapping options, and vertical scrolling on the
IPv4/IPv6 tabs (did not check the others). i was going to perhaps
report this seperately as a bug that seems to have cropped up in an
updated package presumably, but now having got the connection back to
normal, the interface has restored to normal as well it seems...
i'm going to stop here at this point, having spent about 3.5 hours
today on nothing but this. i hope the details of this exploration help
and thus it was worth my time to do.
so the problem seems to be iwd specific. there's also buggy NM / gnome-
wifi-settings issues that i hope attention will be paid attention to,
to improve UX.
More information about the Pkg-utopia-maintainers
mailing list