Bug 703003

Summary: SELinux is preventing NetworkManager from 'read, write' accesses on the chr_file rfkill.
Product: [Fedora] Fedora Reporter: Wendell Baker <wendellcraigbaker>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dcbw, jklimes
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-30 12:28:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
/var/log/messages (see the sealerts at the end)
none
/sbin/lspci >& o.lspci.out none

Description Wendell Baker 2011-05-08 23:43:45 UTC
Created attachment 497693 [details]
/var/log/messages (see the sealerts at the end)

Description of problem:

NetworkManager is not recognizing the wireless networks.




Version-Release number of selected component (if applicable):

$ rpm -q NetworkManager
NetworkManager-0.8.998-4.git20110427.fc15.i686


How reproducible:

100%

Steps to Reproduce:
1. Install Fedora 15 (prerelease circa 2011-05-01)
2. boot it
3. login
4. see that the wifi external switch is "off" ... move it to "on"
  
Actual results:

The wireless networks are not recognized in the Network Manager notification area of GNOME Shell


Expected results:

Fedora 14 works flawlessly on this hardware (Fujitsu Stylistic ST-6010)

Additional info:

Included is lspci, messages and other actualities


See the sealert ...

$ sudo sealert -l ff393900-6d2c-4fcb-9c6e-ebd821586b38
[sudo] password for wbaker: 
SELinux is preventing NetworkManager from 'read, write' accesses on the chr_file rfkill.

*****  Plugin catchall (100. confidence) suggests  ***************************

If you believe that NetworkManager should be allowed read write access on the rfkill chr_file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep NetworkManager /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Comment 1 Wendell Baker 2011-05-08 23:44:22 UTC
Created attachment 497694 [details]
/sbin/lspci >& o.lspci.out

Comment 2 Jirka Klimes 2011-05-30 12:28:59 UTC

*** This bug has been marked as a duplicate of bug 700734 ***