Hide Forgot
SELinux is preventing /usr/sbin/modem-manager from 'read' accesses on the file n1. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that modem-manager should be allowed read access on the n1 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 modem-manager /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:modemmanager_t:s0-s0:c0.c1023 Target Context system_u:object_r:tmpfs_t:s0 Target Objects n1 [ file ] Source modem-manager Source Path /usr/sbin/modem-manager Port <Unbekannt> Host (removed) Source RPM Packages ModemManager-0.4-7.git20110201.fc15 Target RPM Packages Policy RPM selinux-policy-3.9.16-6.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.38.2-9.fc15.x86_64 #1 SMP Wed Mar 30 16:55:57 UTC 2011 x86_64 x86_64 Alert Count 16 First Seen Do 31 Mär 2011 19:04:43 CEST Last Seen Fr 01 Apr 2011 01:29:59 CEST Local ID 87706d1a-7719-4c5d-8717-c83ceb7496fe Raw Audit Messages type=AVC msg=audit(1301614199.69:30): avc: denied { read } for pid=1124 comm="modem-manager" name="n1" dev=tmpfs ino=10815 scontext=system_u:system_r:modemmanager_t:s0-s0:c0.c1023 tcontext=system_u:object_r:tmpfs_t:s0 tclass=file type=SYSCALL msg=audit(1301614199.69:30): arch=x86_64 syscall=open success=no exit=EACCES a0=7fff226a2e80 a1=80000 a2=1b6 a3=0 items=0 ppid=1 pid=1124 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=modem-manager exe=/usr/sbin/modem-manager subj=system_u:system_r:modemmanager_t:s0-s0:c0.c1023 key=(null) Hash: modem-manager,modemmanager_t,tmpfs_t,file,read audit2allow #============= modemmanager_t ============== allow modemmanager_t tmpfs_t:file read; audit2allow -R #============= modemmanager_t ============== allow modemmanager_t tmpfs_t:file read;
*** This bug has been marked as a duplicate of bug 692459 ***