GNOME Bugzilla – Bug 676345
network menu: connection not selected
Last modified: 2021-07-05 14:44:09 UTC
Created attachment 214426 [details] screenshot I just noticed that my shell network menu does currently not show my connected wifi as connected.
I just had a similar problem, it was because the wireless card for some reason disassociated from the AP while staying connected, and therefore the network menu couldn't find a matching network. A partial workaround follows.
Created attachment 216062 [details] [review] NetworkMenu: don't fail if infrastructure wifi has no access point I don't know how, but it happens that connected wifi is not associated with any access point (as reported by both NetworkManager and iwconfig). In that case, treat it like an ad-hoc connection.
Someone to review this one? (It should be a safe patch)
Review of attachment 216062 [details] [review]: "I don't know how, but it happens that connected wifi is not associated with any access point" I'd like to see this get debugged before we plug random hacks into the shell like this one.
I'd like too, but I'm no kernel developer - and that's the level of this problem, as dmesg had "Associated to 00:00:00:00:00:00" and iwconfig had "Access-Point:Not Associated" (with iwlifi on a Intel Corporation Ultimate N WiFi Link 5300. I don't know the model of AP in question)
GNOME's policy is to not work around kernel and other stack bugs. CCing dcbw.
Logs from /var/log/messages and/or kernel logs would help here. If the connection gets dropped for some reason, NM waits a short period of time for it to be re-established by the supplicant/driver (about 10 seconds) and during that time 'iwconfig' may report no association and NM cannot determine the associated AP (because there really isn't one). This condition is either followed by a reassociation or by dropping the connection entirely. Here, I think a UI should continue to show connected state until NM indicates that the connection is dropped, but simply not show which SSID is associated in the menu. You can still use the current Active Connection's details though, like the connection ID or show the SSID from the active connection's wifi setting if you want, even though the wifi device's ActiveAccessPoint property is "/".
Unfortunately, I'm not able to provide logs here (I was away when it happened, and I don't have access to that AP right now). In any case, it should be noted that the connection kept working with no interruptions, it was not failing or reconnecting automatically. Btw, the proposed workaround (showing the connection ID) is what this patch implements.
*** Bug 679679 has been marked as a duplicate of this bug. ***
A few months later, and this patch is still in my queue. What are going to do? Merge it? Drop it? Wait and see if NetworkManager/drivers are fixed by now?
(In reply to comment #10) > A few months later, and this patch is still in my queue. What are going to do? > Merge it? Drop it? Wait and see if NetworkManager/drivers are fixed by now? My policy is that every hack we add to the shell to work around upstream bugs without a thorough investigation lessens the chance of those upstream bugs get fixed. If there has been a thorough investigation and this is the correct way forward, I will accept such a patch only if it has a giant comment clearly marking this as a workaround for an upstream bug, with references to both GNOME bugs and the upstream bugs.
Created attachment 236292 [details] [review] NetworkMenu: don't fail if infrastructure wifi has no access point I don't know how, but it happens that connected wifi is not associated with any access point (as reported by both NetworkManager and iwconfig). In that case, treat it like an ad-hoc connection. Rebased, per Bastien's request in bug 687853.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help.