Red Hat Bugzilla – Bug 981908
SELinux is preventing /usr/lib64/xulrunner/plugin-container from 'unlink' accesses on the sock_file socket-1640-1804289383.
Last modified: 2015-02-17 10:54:52 EST
Description of problem: SELinux is preventing /usr/lib64/xulrunner/plugin-container from 'unlink' accesses on the sock_file socket-1640-1804289383. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that plugin-container should be allowed unlink access on the socket-1640-1804289383 sock_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 plugin-containe /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c 0.c1023 Target Context unconfined_u:object_r:xdm_tmp_t:s0 Target Objects socket-1640-1804289383 [ sock_file ] Source plugin-containe Source Path /usr/lib64/xulrunner/plugin-container Port <Unknown> Host (removed) Source RPM Packages xulrunner-21.0-4.fc17.x86_64 Target RPM Packages Policy RPM selinux-policy-3.10.0-169.fc17.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.8.13-100.fc17.x86_64 #1 SMP Mon May 13 13:36:17 UTC 2013 x86_64 x86_64 Alert Count 4 First Seen 2013-05-10 23:38:57 PDT Last Seen 2013-06-09 23:41:14 PDT Local ID 3cc2d4cf-cfff-45f5-979d-93322e8f1beb Raw Audit Messages type=AVC msg=audit(1370846474.760:68): avc: denied { unlink } for pid=1640 comm="plugin-containe" name="socket-1640-1804289383" dev="dm-1" ino=265240 scontext=unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:xdm_tmp_t:s0 tclass=sock_file type=SYSCALL msg=audit(1370846474.760:68): arch=x86_64 syscall=unlink success=no exit=EACCES a0=7f2bdc3ff300 a1=7ffff7284b10 a2=7ffff7284b10 a3=636f732f32697073 items=0 ppid=1523 pid=1640 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 ses=2 tty=(none) comm=plugin-containe exe=/usr/lib64/xulrunner/plugin-container subj=unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c0.c1023 key=(null) Hash: plugin-containe,mozilla_plugin_t,xdm_tmp_t,sock_file,unlink Additional info: reporter: libreport-2.1.5 hashmarkername: setroubleshoot kernel: 3.9.9-301.fc19.x86_64 type: libreport Potential duplicate: bug 904319
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.