After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 633916 - Applet icon does not match actual state
Applet icon does not match actual state
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: nm-applet
0.8.x
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-11-03 15:00 UTC by mweaver
Modified: 2016-03-11 17:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot of problem (12.55 KB, image/png)
2010-11-03 15:00 UTC, mweaver
Details
Exceprt from /var/log/daemon.log (ip's and mac addresses redacted to protect the innocent) (4.40 KB, text/plain)
2010-11-03 15:01 UTC, mweaver
Details
output from nm-tool (1.49 KB, text/plain)
2010-11-08 14:38 UTC, mweaver
Details
nm-tool.output.20121008-2202.log (1.47 KB, text/x-log)
2012-10-08 14:22 UTC, Guy Lunardi
Details

Description mweaver 2010-11-03 15:00:50 UTC
Created attachment 173778 [details]
Screenshot of problem

Icon shows me as disconnected, but is connected to a wireless network (internet works fine).

I was connected to a different wireless network on a VPN, and when I switched to this one it showed me as disconnected even though the switch worked fine.

Problem encountered in Linux Mint 9 XFCE.
Comment 1 mweaver 2010-11-03 15:01:38 UTC
Created attachment 173779 [details]
Exceprt from /var/log/daemon.log (ip's and mac addresses redacted to protect the innocent)
Comment 2 Dan Williams 2010-11-05 20:18:23 UTC
When this happens again, can you run 'nm-tool' for me?
Comment 3 mweaver 2010-11-08 14:38:53 UTC
Created attachment 174058 [details]
output from nm-tool
Comment 4 Guy Lunardi 2012-10-08 14:22:17 UTC
Created attachment 226045 [details]
nm-tool.output.20121008-2202.log

Running NetworkManager-applet 0.9.6.2 with GNOME 3.6 and I still get this issue.

At this instant my applet icon seems stuck with the 'network-wireless-acquiring-symbolic' being displayed. Though I am surely online. 

I can access the applet and all the menus. It's just that the icon is wrong and never moved on to 'network-wireless-connected-symbolic'.

The log attached shows that I am indeed connected via Wireless according to nm-tool.

Also, the information on these sites is out of date (will create a separate bug for that):
https://live.gnome.org/DarrenAlbers/NetworkManagerFAQ
http://projects.gnome.org/NetworkManager/
Comment 5 mhuhtala 2013-03-04 15:33:10 UTC
On my system, the icon does not switch to disconnected mode when the network connection is lost. I'm using a USB mobile broadband modem, and if I physically remove it, the icon still keeps showing the signal strength bars even though the connection is gone. It will update if I use the menu to select a different connection. I'm using Fedora 18 and I have

network-manager-applet-0.9.7.997-1.fc18.x86_64
NetworkManager-0.9.8.0-1.fc18.x86_64
kernel-3.7.9-205.fc18.x86_64
Comment 6 mhuhtala 2013-03-04 15:55:38 UTC
I just noticed another bit of odd behaviour of the icon. While Wi-Fi was turned off, I removed the USB modem that was in use, and the icon kept showing the mobile broadband signal strength bars. Mobile broadband did disappear from the menu. I then turned on the Wi-Fi toggle, and got a Wi-Fi connection automatically, with the appropriate wireless signal strength icon. I then turned off the Wi-Fi toggle, the network was disconnected, but the icon switched to showing the mobile broadband signal bars! At that point, there wasn't even a mobile broadband modem on the system and the menu didn't have any mobile broadband options.

The broadband signal bars do appear reproducibly every time if I repeat the steps.
Comment 7 Lubomir Rintel 2016-03-11 16:46:39 UTC
Cleaning up the old bugs that didn't get addressed. Sorry you didn't hear from us.

I spent time time trying to reproduce this, but can not, so chances are that with the current Git master the bug is already fixed.

If it's still a problem feel free to reopen.