GNOME Bugzilla – Bug 666151
Wireless networks list not correctly repopulated after suspend/resume or off/on wireless
Last modified: 2015-02-27 04:00:36 UTC
After a suspend/resume cycle, or turning the wireless hardware off and back on again, the list of networks in the Network panel applet is incomplete or inaccurate. For example, after deactivating and then reactivating wlan0, the list has only one wireless network. On the other hand, nm-tool reports all six that there should be. This is with gnome-shell-3.2.1-2.fc16.x86_64, and wasn't a problem on Gnome 3.0.
Should add that this does not happen consistently, but often. (Working OK this time round.) Restarting Gnome Shell correctly repopulates the list in those cases. I've found the following in .xsession-errors, which may be correlated with an incomplete networks list: ** (nm-applet:15212): WARNING **: _nm_object_get_property: Error getting 'Defaul t' for /org/freedesktop/NetworkManager/ActiveConnection/5: (19) Method "Get" wit h signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist ** (nm-applet:15212): WARNING **: _nm_object_get_property: Error getting 'Defaul t' for /org/freedesktop/NetworkManager/ActiveConnection/5: (19) Method "Get" wit h signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist JS ERROR: !!! Exception was: TypeError: apObj is null JS ERROR: !!! lineNumber = '1306' JS ERROR: !!! fileName = '"/usr/share/gnome-shell/js/ui/status/network.j s"' JS ERROR: !!! stack = '"([object _private_NMClient_DeviceWifi],[object _ private_NMClient_AccessPoint])@/usr/share/gnome-shell/js/ui/status/network.js:13 06 "' JS ERROR: !!! message = '"apObj is null"' JS ERROR: !!! Exception was: TypeError: apObj is null JS ERROR: !!! lineNumber = '1306' JS ERROR: !!! fileName = '"/usr/share/gnome-shell/js/ui/status/network.j s"' JS ERROR: !!! stack = '"([object _private_NMClient_DeviceWifi],[object _ private_NMClient_AccessPoint])@/usr/share/gnome-shell/js/ui/status/network.js:13 06 "' JS ERROR: !!! message = '"apObj is null"' JS ERROR: !!! Exception was: TypeError: apObj is null JS ERROR: !!! lineNumber = '1306' JS ERROR: !!! fileName = '"/usr/share/gnome-shell/js/ui/status/network.j s"' JS ERROR: !!! stack = '"([object _private_NMClient_DeviceWifi],[object _ private_NMClient_AccessPoint])@/usr/share/gnome-shell/js/ui/status/network.js:13 06 "' JS ERROR: !!! message = '"apObj is null"' JS ERROR: !!! Exception was: TypeError: apObj is null JS ERROR: !!! lineNumber = '1306' JS ERROR: !!! fileName = '"/usr/share/gnome-shell/js/ui/status/network.j s"' JS ERROR: !!! stack = '"([object _private_NMClient_DeviceWifi],[object _ private_NMClient_AccessPoint])@/usr/share/gnome-shell/js/ui/status/network.js:13 06 "' JS ERROR: !!! message = '"apObj is null"'
The JS errors were fixed in bug 659277. I don't know about the Default property not being there, seems a problem in libnm-glib...
OK, I'll try that patch. (Will it be in a future update to 3.2?) I've also applied the patches from bug 664124, though I've no idea if that's really the same bug.
(In reply to comment #3) > OK, I'll try that patch. (Will it be in a future update to 3.2?) I've also > applied the patches from bug 664124, though I've no idea if that's really the > same bug. OK, well I've just deactivated and reactivated wlan0 (I think this fails more reliably if it's left deactivated for a few minutes), and now there are no networks in the list. (Seven show up with nm-tool.) Looks like none of those patches fix this, so I'll revert to the package-original for the time being. No JavaScript (or any other) errors reported, however.
The fallback nm-applet appears to behave itself (synced with nm-tool).
The network menu has seen major rewrites since the bug was filed, so it is highly unlikely that there is any information here that is still relevant to current issues.