Bug 917317

Summary: NetworkManager ignores rfkill (or gets really confused) for its gnome shell status icon
Product: [Fedora] Fedora Reporter: Jean-François Fortin Tam <nekohayo>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dcbw, psimerda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://bugzilla.gnome.org/show_bug.cgi?id=676285
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-07 15:56:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jean-François Fortin Tam 2013-03-03 03:12:42 UTC
On a Thinkpad X220 (i7 sandybridge with Intel wifi)

1. Turn off wifi, either by using fn+F4, or networkmanager's "turn of the wifi" slider in gnome shell's network menu, or using gnome-control-center's "airplane mode", or using "rfkill block wifi".

2. The wifi LED on the thinkpad turns off, but networkmanager's "wifi connected" icon stays unmoved.

3. Turn wifi back on... now networkmanager's icon changes to "disconnected" and then proceeds to reconnect to the wifi.


Trying to ping 8.8.8.8 seems to hint that it is only nm's gnome-shell status icon that is borked up.

Comment 1 Jean-François Fortin Tam 2013-03-03 03:23:43 UTC
I'll add that this also occurs with the hardware RF killswitch on the Thinkpad - gnome-shell still shows a "wifi connected" icon even though the hardware is completely turned off and ping says the network is unavailable.

Comment 2 Pavel Šimerda (pavlix) 2013-05-07 14:42:33 UTC
This would be better reported upstream: http://bugzilla.gnome.org/

Comment 3 Jean-François Fortin Tam 2013-05-07 15:38:58 UTC
Already reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=676285

Comment 4 Pavel Šimerda (pavlix) 2013-05-07 15:56:29 UTC
Thanks!

Comment 5 Dan Williams 2013-05-07 16:56:28 UTC
It'll get fixed in 0.9.8.2 and 0.9.10; fix is already upstream.