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

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.

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.

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.

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

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

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

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

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

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

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

It is no longer grayed out.

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.

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).

Raphael, that's a different bug:

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

(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).

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.

(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.

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

(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.

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

In F12 it's Ok now and it works well just as before the bug.

I am a NOOB and would be very grateful for some easy help to fix this issue, my wireless is greyed out in the network manager and I am having trouble following how to fix this.  I am grateful for anyones help.

I am a NOOB and would be very grateful for some easy help to fix this issue, my wireless is greyed out in the network manager and I am having trouble following how to fix this.  I am grateful for anyones help.