RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 633501 - Enable Networking and Enable Wireless options are grayed out in NetworkManager Applet after update
Summary: Enable Networking and Enable Wireless options are grayed out in NetworkManage...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: NetworkManager
Version: 6.0
Hardware: All
OS: Linux
urgent
medium
Target Milestone: rc
: ---
Assignee: Dan Williams
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 638598
TreeView+ depends on / blocked
 
Reported: 2010-09-13 20:40 UTC by James Laska
Modified: 2013-09-02 06:50 UTC (History)
8 users (show)

Fixed In Version: NetworkManager-0.8.1-6.el6
Doc Type: Bug Fix
Doc Text:
Occasionally, the NetManager panel applet would not be able to determine user permissions to enable networking and therefore disabled the "Enable Networking" and "Enable Wireless" check boxes. This is now fixed to ensure that if the user has permissions to enable networking, the check boxes display as expected.
Clone Of: 627365
Environment:
Last Closed: 2011-05-19 14:24:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0769 0 normal SHIPPED_LIVE NetworkManager bug fix and enhancement update 2011-05-18 18:08:36 UTC

Description James Laska 2010-09-13 20:40:32 UTC 
+++ This bug was initially created as a clone of Bug #627365 +++

Description of problem:
Aug 25 23:29:03 ao yum[2163]: Updated: 1:NetworkManager-0.8.1-3.git20100813.fc12.i686
After this update Enable Networking and Enable Wireless options are grayed out in NetworkManager Applet.

Version-Release number of selected component (if applicable):
1:NetworkManager-0.8.1-3.git20100813.fc12.i686

--- Additional comment from work.eric on 2010-08-26 14:43:22 EDT ---

I'm seeing the same problem after the 0.8.1-4 update on F13.

--- Additional comment from brackbillbruce on 2010-08-26 22:38:55 EDT ---

I see this too.

A kind of workaround is to edit the connection.  It will bring up a dialog for root privileges and then the Enable Networking and Enable Wireless will be available.

Has editing a connection always required root? I don't remember it being this way. Maybe this grayed out problem is a privileges issue.

--- Additional comment from bugzilla.co.uk on 2010-08-27 11:53:56 EDT ---

This bug also prevents use of Mobile Broadband, as Enable Mobile Broadband always starts un-ticked when the device is connected. 
This should make it a more urgent bug. It is rare to need to un-tick Enable Networking or Enable Wireless, but without ticking 'Enable Mobile Broadband' it is impossible to connect. 

Edit connection does not require root privilege, however running something that does (such as system-config-firewall) will make Enable Networking and Enable Wireless available.

--- Additional comment from jklimes on 2010-08-30 08:38:36 EDT ---

The 'Enable Wireless', 'Enable Networking' and other properties are protected with policy kit to prevent unauthorized usage (e.g. disabling network by non-local user). These permissions are defined in /usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy file.

However, nm-applet didn't set initial permissions and thus the menu items get grayed out.

Fixed upstream:
1aeb178397dd16316bfc242a2e41c54e28933f9a (master)
c7b531250e7417cf51d088c21f91e4a6ef410ac3 (NMA_0_8)

Note:
As a workaround, you can do:
sudo touch /usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy
which will update permissions and sensitize the menu items.

--- Additional comment from jklimes on 2010-08-30 09:32:06 EDT ---

*** Bug 627025 has been marked as a duplicate of this bug. ***

--- Additional comment from updates on 2010-08-31 21:25:40 EDT ---

NetworkManager-0.8.1-6.git20100831.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/NetworkManager-0.8.1-6.git20100831.fc13

--- Additional comment from updates on 2010-08-31 21:40:25 EDT ---

NetworkManager-0.8.1-6.git20100831.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/NetworkManager-0.8.1-6.git20100831.fc14

--- Additional comment from updates on 2010-08-31 21:42:42 EDT ---

NetworkManager-0.8.1-6.git20100831.fc12 has been submitted as an update for Fedora 12.
https://admin.fedoraproject.org/updates/NetworkManager-0.8.1-6.git20100831.fc12

--- Additional comment from updates on 2010-09-02 16:47:54 EDT ---

NetworkManager-0.8.1-6.git20100831.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update NetworkManager'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/NetworkManager-0.8.1-6.git20100831.fc13

--- Additional comment from raphgro on 2010-09-06 13:32:43 EDT ---

Here is some kind of work around the problem. My idea is to restart the NetworkManager service every time when the system wakes up from hibernation.

Create a file called /etc/pm/sleep.d/50custom with the following content and mark it executable.

A big thanks a lot goes to Khaytsus from IRC who nicely provided this script.

-- start of script
#!/bin/bash

service="/sbin/service"
rm="/bin/rm"
touch="/bin/touch"

case "$1" in
	hibernate)
		$touch /tmp/.hibernate
		;;
	thaw|resume) 
		if [ -e /tmp/.hibernate ]; then
			$rm /tmp/.hibernate
			# do whatever here, $service NetworkManager restart ?
			$service NetworkManager restart
		fi
		;;
	*)
		;;
esac

exit $?
-- end of script

--- Additional comment from codezilla on 2010-09-07 14:38:28 EDT ---

Installed NetworkManager-0.8.1-6.git20100831.fc13.i686 and dependencies

It is no longer grayed out.

--- Additional comment from updates on 2010-09-07 22:27:44 EDT ---

NetworkManager-0.8.1-6.git20100831.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

--- Additional comment from raphgro on 2010-09-10 10:20:53 EDT ---

Sorry, but it does not seem to work properly. Either Network-Manager is very slow in detecting another network connection being available after an hibernation or the bug is only fixed at half. I had to restart the service to get NM working again (disabled network after waked up from hibernation).

--- Additional comment from aph on 2010-09-10 11:22:14 EDT ---

Raphael, that's a different bug:

https://bugzilla.redhat.com/show_bug.cgi?id=628309

--- Additional comment from raphgro on 2010-09-10 11:44:12 EDT ---

(In reply to comment #14)
Sorry, but I doubt that it has anything to do with udev. As stated before, the issue is gone if NM is restarted (and nothing else done additionally).

--- Additional comment from updates on 2010-09-10 23:34:43 EDT ---

NetworkManager-0.8.1-6.git20100831.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

--- Additional comment from aph on 2010-09-11 14:39:59 EDT ---

(In reply to comment #15)

> Sorry, but I doubt that it has anything to do with udev.

It certainly seems to be.

> As stated before, the
> issue is gone if NM is restarted (and nothing else done additionally).

That's the same symptom as 628309.  By all means tell me I'm wrong, but not if you haven't tried it.

--- Additional comment from mitko on 2010-09-12 09:23:24 EDT ---

I have same problem on Asus Eeepc 1000h 
NetworkManager-0.8.1-6.git20100831.fc13.i686 is installed.

Аfter executing command :
exec dbus-send --system                        \
        --dest=org.freedesktop.NetworkManager \
        /org/freedesktop/NetworkManager       \
        org.freedesktop.NetworkManager.wake

, the network begins to operate normally

--- Additional comment from dcbw on 2010-09-13 09:59:07 EDT ---

(In reply to comment #18)
> I have same problem on Asus Eeepc 1000h 
> NetworkManager-0.8.1-6.git20100831.fc13.i686 is installed.
> 
> Аfter executing command :
> exec dbus-send --system                        \
>         --dest=org.freedesktop.NetworkManager \
>         /org/freedesktop/NetworkManager       \
>         org.freedesktop.NetworkManager.wake
> 
> , the network begins to operate normally

This issue is different than the issue this bug was filed for and is related to suspend/resume.
Comment 1 James Laska 2010-09-13 20:40:57 UTC 
> dcbw: for reference, the fix is
> dcbw: http://git.gnome.org/browse/network-manager-applet/commit/?id=1aeb178397dd16316bfc242a2e41c54e28933f9a
Comment 10 Dan Williams 2010-09-22 21:45:52 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Occasionally upon login to a desktop, the network panel applet's right-click menu will have disabled "Enable Networking" and "Enable Wireless" checkboxes.  This is due to a bug in determining whether those menu items should be enabled based on the logged-in user's permissions.  If the user does have permission to perform those actions, it is possible to re-enable the menu items by running the following command as root:

touch /usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy

Alternatively, WiFi can be enabled/disabled through the command-line using the following commands:

nmcli nm wifi on
nmcli nm wifi off

This issue will be addressed in a future update.
Comment 13 Ryan Lerch 2010-09-24 02:46:48 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,10 +1,11 @@
-Occasionally upon login to a desktop, the network panel applet's right-click menu will have disabled "Enable Networking" and "Enable Wireless" checkboxes.  This is due to a bug in determining whether those menu items should be enabled based on the logged-in user's permissions.  If the user does have permission to perform those actions, it is possible to re-enable the menu items by running the following command as root:
+Under some circumstances, the NetworkManger panel applet cannot determine if a user has permission to enable networking. Consequently, after logging into the desktop, the "Enable Networking" and "Enable Wireless" checkboxes may be disabled. To work around this, run the following command as root:
 
 touch /usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy
+							
+Alternatively, WiFi can be enabled using the command:
 
-Alternatively, WiFi can be enabled/disabled through the command-line using the following commands:
-
 nmcli nm wifi on
-nmcli nm wifi off
+								
+or disabled using the command:
 
-This issue will be addressed in a future update.+nmcli nm wifi off
Comment 14 Dan Williams 2010-09-28 19:10:42 UTC 
Scratch build upstream fix is here:

http://brewweb.devel.redhat.com/brew/taskinfo?taskID=2779776

Please test and let me know how it works.  With that feedback, we can actually
push the fix into RHEL6.
Comment 15 Dan Williams 2010-09-28 19:57:42 UTC 
Non-scratch brew build with this fix (and committed to CVS):

http://brewweb.devel.redhat.com/brew/taskinfo?taskID=2785531
Comment 20 Misha H. Ali 2011-04-20 07:10:44 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,11 +1 @@
-Under some circumstances, the NetworkManger panel applet cannot determine if a user has permission to enable networking. Consequently, after logging into the desktop, the "Enable Networking" and "Enable Wireless" checkboxes may be disabled. To work around this, run the following command as root:
+Occasionally, the NetManager panel applet would not be able to determine user permissions to enable networking and therefore disabled the "Enable Networking" and "Enable Wireless" check boxes. This is now fixed to ensure that if the user has permissions to enable networking, the check boxes display as expected.-
-touch /usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy
-							
-Alternatively, WiFi can be enabled using the command:
-
-nmcli nm wifi on
-								
-or disabled using the command:
-
-nmcli nm wifi off
Comment 21 errata-xmlrpc 2011-05-19 14:24:59 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0769.html
Note You need to log in before you can comment on or make changes to this bug.