Bug 893875

Would you specify some details:
1. You say the icon is just white bars instead of blue bars indicating some signal, right?
2. That would indicate incorrect handling with icons or more probably an issue with signal strength within NM or driver.
Can you get output of these commands:
$ nmcli -f general dev list iface wlan0
$ nmcli dev wifi list
3. If you run a second nm-applet (from a terminal), what does its icon look like?

1. Yes, the normal case is the display of an icon with an appropriate number of blue bars.  The abnormal case is the display of an icon with all bars showing white.

2. In both the normal and abnormal cases, the wifi connection is successful and the signal strength reported by the kernel in /proc/net/wireless is strong.

[root@robert ~]# nmcli -f general dev list iface wlan0
GENERAL.DEVICE:                         wlan0
GENERAL.TYPE:                           802-11-wireless
GENERAL.VENDOR:                         Intel Corporation
GENERAL.PRODUCT:                        Centrino Advanced-N 6235
GENERAL.DRIVER:                         iwlwifi
GENERAL.DRIVER-VERSION:                 3.6.10-4.fc18.x86_64
GENERAL.FIRMWARE-VERSION:               18.168.6.1
GENERAL.HWADDR:                         C4:85:08:2B:3E:FF
GENERAL.STATE:                          100 (connected)
GENERAL.REASON:                         0 (No reason given)
GENERAL.UDI:                            /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/net/wlan0
GENERAL.IP-IFACE:                       wlan0
GENERAL.NM-MANAGED:                     yes
GENERAL.AUTOCONNECT:                    yes
GENERAL.FIRMWARE-MISSING:               no
GENERAL.CONNECTION:                     /org/freedesktop/NetworkManager/ActiveConnection/2
[root@robert ~]# nmcli dev wifi list
SSID                              BSSID               MODE             FREQ       RATE       SIGNAL   SECURITY   ACTIVE  
'tri5_a'                          10:BF:48:52:F3:6C   Infrastructure   5745 MHz   54 MB/s    100      WPA2       no      
'tri5'                            10:BF:48:52:F3:68   Infrastructure   2437 MHz   54 MB/s    93       WPA2       yes     

3. If we run a second nm-applet instance, we see two cases:

Case 1:  The result is no second icon appearing:

[root@robert ~]# nm-applet

** (nm-applet:2466): WARNING **: Failed to initialize D-Bus: Failed to connect to socket /tmp/dbus-iAwC2W1Jrw: Connection refused



Case 2:  The result is a second icon appears with all blue bars.

[root@robert ~]# nm-applet
** Message: applet now removed from the notification area
** Message: applet now embedded in the notification area

** (nm-applet:2436): WARNING **: Failed to register as an agent: (32) Session not found

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.