Bug 750655

Summary: [network] NetworkManager does not show the "Off" button in the menu
Product: [Fedora] Fedora Reporter: Hubert Figuiere <hub+rhbz>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: dcbw, jklimes, maxamillion, otaylor, samkraju, samuel-rhbugs, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 19:59:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Screenshot of the menu
none
Screenshot when wired and the Wifi has been disabled from system settings. none

Description Hubert Figuiere 2011-11-01 21:24:28 UTC
Created attachment 531202 [details]
Screenshot of the menu

Description of problem:
NetworkManager does not show the "Off" button in the menu in Gnome3

Version-Release number of selected component (if applicable):
NetworkManager-0.9.1.90-5.git20110927.fc16.src.rpm

How reproducible:


Steps to Reproduce:
1.Run NetworkManager in Gnome3
2.Make sure to configure the network to use wifi
3.Display the popup
  
Actual results:
Display "unavailable" in lieu of the Off toggle button


Expected results:
Expect the Off toggle button

Additional info:
Wireless card:
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter (rev 01)

Kernel:
Linux raptor 3.1.0-5.fc16.x86_64 #1 SMP Thu Oct 27 03:46:50 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

Machine:
Thinkpad X220

Let me know if you need more

Comment 1 Hubert Figuiere 2011-11-01 21:25:00 UTC
Created attachment 531203 [details]
Screenshot when wired and the Wifi has been disabled from system settings.

Comment 2 Samuel Sieb 2012-02-08 18:53:59 UTC
It's not clear how to reproduce this.  I don't understand step 3.

Please try again with the current NetworkManager and gnome-shell packages as many things have been fixed in this area.

Comment 3 Hubert Figuiere 2012-02-11 20:43:10 UTC
(In reply to comment #2)
> It's not clear how to reproduce this.  I don't understand step 3.

"Display the popup" means click on the NM icon at the top in the shell to show the menu. The screenshot show that.

> Please try again with the current NetworkManager and gnome-shell packages as
> many things have been fixed in this area.

Whatever is current in F16 still does it. Even with the Intel wireless now (I swapped drives to a similar laptop with a different wireless)

Comment 4 Jirka Klimes 2012-02-13 09:24:08 UTC
Does the WiFi actually work? If not, please grab /var/log/messages and attach that.
If the problem is that device status (such as connecting, unavailable, etc.)
is displayed instead of ON/OFF, this is Gnome shell bug (design feature?).

Would you post output of these commands (when you have "unavailable" in Gnome shell):
$ nmcli nm
$ nmcli -p -f general dev list
$ nmcli con status

Comment 5 Hubert Figuiere 2012-02-13 16:20:41 UTC
(In reply to comment #4)
> Does the WiFi actually work? 

Of course it does. Otherwise I would have said it does not work.

> If the problem is that device status (such as connecting, unavailable, etc.)
> is displayed instead of ON/OFF, this is Gnome shell bug (design feature?).
> 
> Would you post output of these commands (when you have "unavailable" in Gnome
> shell):
> $ nmcli nm
> $ nmcli -p -f general dev list
> $ nmcli con status

% nmcli nm
RUNNING         STATE           WIFI-HARDWARE   WIFI       WWAN-HARDWARE   WWAN      
running         connected       enabled         enabled    enabled         enabled   

% nmcli -p -f general dev list
===============================================================================
                                Device details
===============================================================================
GENERAL.DEVICE:                         em1
GENERAL.TYPE:                           802-3-ethernet
GENERAL.DRIVER:                         e1000e
GENERAL.HWADDR:                         F0:DE:F1:9F:AA:E0
GENERAL.STATE:                          unavailable
-------------------------------------------------------------------------------
===============================================================================
                                Device details
===============================================================================
GENERAL.DEVICE:                         wlan1
GENERAL.TYPE:                           802-11-wireless
GENERAL.DRIVER:                         iwlwifi
GENERAL.HWADDR:                         08:11:96:A3:6A:9C
GENERAL.STATE:                          connected
-------------------------------------------------------------------------------

% nmcli con status
NAME                      UUID                                   DEVICES    DEFAULT  VPN  
Auto MyWifi               0da2c749-8889-4642-b9b6-fdfb5f100414   wlan1      yes      no

Comment 6 Jirka Klimes 2012-02-14 09:49:25 UTC
This shows that WiFi is connected. So, if you have "unavaliable" for wireless in Gnome shell menu then it's Gnome shell bug.

Comment 7 Fedora End Of Life 2013-01-16 16:23:33 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Fedora End Of Life 2013-02-13 19:59:18 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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