Description of problem: When I suspend and resume selinux is blocking NetworkManager from making an association. I installed fc5 with selinux disabled and there was no problem. I have since tried the permissive setting (which I am currently using) and have come across this problem. Rebooting and NM works fine again. Suspend/Resume and NM cannot associate with the wifi, although it seems to get a list of available nets. Pluging a net cable allows wired network access. I tried disabling selinux service protection for NM and restarting the NM service, but this still did not allow it to start. I then tried switching to the enforced mode and NM started working again. I have been able to suspend and resume in enforced mode with NM working ok My wifi uses wep128 Version-Release number of selected component (if applicable): selinux-policy-targeted-2.2.25-2.fc5 libselinux-1.30-1.fc5 libselinux-python-1.30-1.fc5 selinux-policy-2.2.25-2.fc5 NetworkManager-0.6.0-3 How reproducible: Steps to Reproduce: 1. Set SElinux to permissive 2. Suspend machine 3. Resume machine 4. Attempt to connect to a wireless net Actual results: Wireless net access blocked Expected results: Associate with requested wifi net Additional info:
I think you have a red herring here. But please submit the AVC messages from /var/log/messages
Created attachment 127073 [details] /var/log/messages chunk Relevant chunk of /var/log/messages from suspend/resume to eth1 failure
Any idea what process is running as mono_t?
Chris do you have any ideas?
mono_t is probably from beagled. POssible from banshee, but I don't think that was running then.
Fixed in selinux-policy-2.2.38-1.FC5.
Closing bugs