[09:34] <Laney> anyone have any clue on https://paste.ubuntu.com/p/PvQmwK55hw/ ?
[09:35] <Laney> just upgraded to eoan and I can't connect to my wifi network at home any more (scanning works though)
[09:36] <Laney> :'(
[09:37] <apw> Laney, that sounds ... odd
[09:37] <apw> what encryption is it using ?
[09:38] <Laney> umm good question
[09:40] <Laney> apw: https://paste.ubuntu.com/p/C6MnFFdZgk/ <- "nmcli con show" of the connection
[09:40] <Laney> I didn't set any fancy stuff up, just normal WPA whatver the unifi thing does
[09:41] <Laney> ah it says "WPA2 Only" "AES/CCMP Only"
[09:41]  * Laney tries rebooting back to 5.0 quickly
[09:44] <Laney> RAH it's not built there
[09:44] <Laney> should have said this is broadcom 😈
[09:46] <Laney> yeah same with 5.0
[09:46] <apw> brcm ... are you saying that your brcm drvier is a dkms which didn't build ?
[09:46] <Laney> it built for 5.2 but not 5.0, the fcf-protection thing
[09:46] <Laney> hacked that out, built it and still broken on 5.0 on the same way
[09:47] <apw> Laney, waht were you running before ?
[09:47] <Laney> disco
[09:49] <apw> but 5.0 there
[09:49] <Laney> yeah
[09:49] <Laney> HMM
[09:49] <Laney> https://bbs.archlinux.org/viewtopic.php?id=248470 this is blaming NM
[09:49] <apw> so the update to the dkms pacakge in eoan
[09:49] <Laney> well it's not definitive
[09:49] <apw> (is most likely)
[09:50] <Laney> ah OK I guess I can try downgrading that first if I stay on 5.0
[09:54] <apw> yeah lets see if that works
[09:54] <apw> need to figure out which thing needs help for sure, and that sounds like a logical test
[09:56] <Laney> same
[09:56] <Laney> ok let me try network-manager then
[09:56] <apw> in theory now you have a 5.0 kernel which you have run before with a brcm you had before, which doesn't work now, erp
[09:57]  * Laney slowly downgrades back down to disco :)
[09:58] <apw> Laney, that aes-only is not something i see here, how did you ask for that
[09:58] <apw> is that from your ap, or an iwlist thing
[09:59] <Laney> it's from the AP
[09:59] <apw> what are the other options
[09:59] <apw> i am wondering if this is just a very bad choice the kernels no longer support
[09:59] <jeremy31> apw AES is CCMP
[09:59] <Laney> "Auto" is the only other option
[09:59] <Laney> O_O
[09:59] <apw> though the 5.0/brcm thing makes that less pheasable
[10:01] <Laney> I'm online
[10:01] <Laney> so it seems like it was network-manager after all, WTF
[10:02] <apw> say what now, network-manager ?
[10:02] <apw> just how does it manage that ???
[10:02] <apw> Laney, ^
[10:03] <Laney> apw: not a clue, I'm just asking upstream if it's anything they've heard of
[10:06] <jeremy31> bcmwl has never been the easiest to deal with
[10:23] <Laney> apw: seems like they are owning the problem, you're off the hook :>
[10:33] <jeremy31> Laney: do they have a patch to fix it?
[10:33] <Laney> not yet
[11:08] <apw> Laney, so they know what 'it' even is ?
[11:12] <Laney> nope
[11:12] <Laney> apw: well, ...
[11:12] <Laney> 20/08 12:10:31 <thaller> wpa_supplicant[1348]:   * akm=0xfac04
[11:12] <Laney> 20/08 12:10:36 <thaller> wpa_supplicant[1348]: nl80211: MLME connect failed: ret=-22 (Invalid argument)
[11:12] <Laney> 20/08 12:11:00 <thaller> that's RSN_AUTH_KEY_MGMT_FT_PSK ...
[11:12] <Laney> 20/08 12:11:15 <thaller> seems the driver doesn't like that...
[11:12] <Laney> he's investigating the log at least
[11:13] <Laney> follow along in #nm if you like
[11:14]  * apw does that
[11:20] <apw> Laney, i am right in thinking you downgraded nm and it started workgin ?
[11:20] <Laney> apw: correct
[11:20] <apw> Laney, so likely nm doing somethig new
[11:21] <Laney> whatever it started doing to wpa-supplicant presumably
[15:39] <Laney> jeremy31: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/2f8a4e90f0fd0f900996e3081d49f8799bba4c6f