On two computers running gnome-wayland, the wifi stopped working after the genup (sakaki repository) nightly (early morning) update on April 24th. Wifi had been working fine for a long time on those two computers and was broken on both of them after the update. The update installed networkmanager-1.16.0 and nm-applet-1.8.20. The two computers are a Lenovo Ideapad 320 and a Dell Inspiron 15-3521. I did some debugging on the Dell. Downgrading networkmanager and nm-applet to the previous versions did not help. Gentoo gnome-wayland was installed on those two computers in the way described in the Sakaki handbook and, as stated earlier, was running OK, including wifi, on both before the April 4th update.. I verified they both run wayland by echoing the XDG_SESSION_TYPE variable. I added an /etc/NetworkManager/NetworkManager.conf file for debugging: --- [main] [logging] domains=WIFI:DEBUG,WIFI_SCAN:OFF --- I am enclosing the output of "journalctl -b -u NetworkManager" as Dell-wifi-log. It shows attemps to connect to the "Clairbois" SSID through the gnome "All Settings" and then "Network". Attempts were also made throug nmcli (real password replaced with <pwd>): --- jplx-gn3 /var/log # nmcli dev wifi connect Clairbois password <pwd> ifname wlp2s0 Error: Connection activation failed: (7) Secrets were required, but not provided --- However, the password was actually provided. I am also enclosing the /etc/NetworkManager/system-connections/Clairbois.nmconnection file with the password replaced with <pwd> Finally, an additional piece of information: I also have a Macbook Air running gentoo x11 (not wayland due to a gdm display manager bug #673462). Wifi is still running fine on that one. I noticed two differences between this one and the other failing two: 1 - it runs gnome-x11 and not gnome-wayland 2 - in the Clairbois.nmconnection file, the MAC address matches the one reported by invoking "ifconfig". The failing computers show either a different MAC address or none at all. Not sure this is significant. Is Gentoo NetworkManager modifying wifi-interface MAC address? Reproducible: Always Steps to Reproduce: 1.Does not connect to wifi network anymore. 2. 3. Actual Results: In "All Setting" > Network, select an SSID and try to connect Expected Results: Wifi connection active with an IP address It should have connected to the wifi network
Created attachment 574334 [details] Output of "Journalctl -b -u NetworkManager" The password is provided but the software does not see it.
Created attachment 574336 [details] /etc/NetworkManager/system-connections/Clairbois.nmconnection file This file is created automatically by the system. IT does not have a MAC address. Is it correct?
Created attachment 574338 [details] emerge --info Output of "emerge --info"
what is chance your still using wpa_supplicant and it was updated in the last few days?
It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis. We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3]. I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4]. Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product. [1] https://www.gentoo.org/get-involved/irc-channels/ [2] https://forums.gentoo.org/ [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html [4] https://www.gentoo.org/support/
FYI: The wifi-working laptop (Macbook air) runs kernel 4.14.83 The two wifi-failing laptops (Lenovo, Dell) were running with kernel 4.19.27-r1 After downgrading them to 4.14.83, Wifi works fine on both of them. So, this looks like a bug involving wpa_supplicant, NetworkManager and the kernel.
As was pointed out earlier, this is not a support forum. When you do find an actual bug and want to report it, then bugs.gentoo.org is the correct place to do that. Until you find a bug, reporting a vague problem here rarely results in a particular, local solution, but reporting specific bugs usually does.
