You are not logged in.
I've been having an issue with nm-applet where it does not show the correct icon until I restart the shell.
I'm currently connected wirelessly but the icon shows that I'm still attempting to connect. It also does not show which network I'm connected to if I open the drop-down menu. If I were to be connected on wired only and then disconnect the cable, it would still show that I'm connected.
When I run nm-applet through terminal, all I get is:
** Message: applet now removed from the notification area
** Message: applet now embedded in the notification area
Any ideas?
Edit: Actually, restarting gnome-shell doesn't always make it work. After a restart it's now showing that I'm not connected to any networks.
Edit: Restarting the computer seems to temporarily fix it. I'm guessing that this might be related to suspending the laptop
Last edited by SpartanW80 (2013-07-23 16:54:34)
Offline
I think I am having the same problem. I initially didn't even realise I had a working network connection... I was researching why the connection wasn't being made... then I realised it was, its just the icon wasn't updating!
The icon continues to show it is still attempting to connect (3 dots over the dulled wireless symbol), or sometimes that there is no connection (icon with an X).
I am using GNOME 3.8, gnome-shell 3.8.2-4, networkmanager 0.9.8.0-3 and network-manager-applet 0.9.8.0-3.
I am on a MacBook pro with a Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01). Using the aur/b43-firmware drivers.
I'm connecting to a wireless network with a WPA2-PSK passphrase.
nmcli dev status
DEVICE TYPE STATE
enp3s0 802-3-ethernet unavailable
wlan0 802-11-wireless connected
nmcli dev wifi
SSID BSSID MODE FREQ RATE SIGNAL SECURITY ACTIVE
'17aHindmarshAve' 30:85:A9:E7:E4:10 Infrastructure 2437 MHz 54 MB/s 97 WPA2 no
Offline
This problem just resolved itself after my latest pacman update. I now have networkmanager 0.9.8.0-4, and the version of network-manager-applet did not change.
Spartan: do you still have an issue? You may want to use nm-connection-editor to confirm NetworkManager is waiting for an IPv6 address to complete the connection?
Offline