Bug 1044559 - SELinux is preventing /usr/bin/Xorg from 'remove_name' accesses on the directory X8.
Summary: SELinux is preventing /usr/bin/Xorg from 'remove_name' accesses on the direct...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:35d47c73ca134e704d05129dc06...
: 1044554 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-18 14:50 UTC by Aditya Pratikto
Modified: 2015-06-30 00:47 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 00:47:05 UTC
Type: ---


Attachments (Terms of Use)

Description Aditya Pratikto 2013-12-18 14:50:43 UTC
Description of problem:
i've got compilation failed

[root@trolldemnoobz ghorhe]# grep Xorg /var/log/audit/audit.log | audit2allow -M mypol
compilation failed:
sh: /usr/bin/checkmodule: No such file or directory
[root@trolldemnoobz ghorhe]# 
SELinux is preventing /usr/bin/Xorg from 'remove_name' accesses on the directory X8.

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

If you believe that Xorg should be allowed remove_name access on the X8 directory 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 Xorg /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                system_u:system_r:bumblebee_t:s0
Target Context                system_u:object_r:xdm_tmp_t:s0
Target Objects                X8 [ dir ]
Source                        Xorg
Source Path                   /usr/bin/Xorg
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           xorg-x11-server-Xorg-1.14.4-5.fc20.x86_64
Target RPM Packages           
Policy RPM                    selinux-policy-3.12.1-106.fc20.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 3.11.10-301.fc20.x86_64 #1 SMP Thu
                              Dec 5 14:01:17 UTC 2013 x86_64 x86_64
Alert Count                   1
First Seen                    2013-12-18 21:48:53 WIB
Last Seen                     2013-12-18 21:48:53 WIB
Local ID                      61dcfe79-3940-42fb-a98a-b540e4f0fb03

Raw Audit Messages
type=AVC msg=audit(1387378133.117:785): avc:  denied  { remove_name } for  pid=22117 comm="Xorg" name="X8" dev="tmpfs" ino=257279 scontext=system_u:system_r:bumblebee_t:s0 tcontext=system_u:object_r:xdm_tmp_t:s0 tclass=dir


type=AVC msg=audit(1387378133.117:785): avc:  denied  { unlink } for  pid=22117 comm="Xorg" name="X8" dev="tmpfs" ino=257279 scontext=system_u:system_r:bumblebee_t:s0 tcontext=system_u:object_r:xdm_tmp_t:s0 tclass=sock_file


type=SYSCALL msg=audit(1387378133.117:785): arch=x86_64 syscall=unlink success=yes exit=0 a0=1786192 a1=5a87bd a2=0 a3=ffffffff items=0 ppid=20926 pid=22117 auid=4294967295 uid=0 gid=1001 euid=0 suid=0 fsuid=0 egid=1001 sgid=1001 fsgid=1001 ses=4294967295 tty=(none) comm=Xorg exe=/usr/bin/Xorg subj=system_u:system_r:bumblebee_t:s0 key=(null)

Hash: Xorg,bumblebee_t,xdm_tmp_t,dir,remove_name

Additional info:
reporter:       libreport-2.1.10
hashmarkername: setroubleshoot
kernel:         3.11.10-301.fc20.x86_64
type:           libreport

Comment 1 Aditya Pratikto 2013-12-18 15:17:05 UTC
it solve when i install checkpolicy

Comment 2 Daniel Walsh 2013-12-19 20:35:11 UTC
Well the bug is in selinux-policy not the work around.

Comment 3 Daniel Walsh 2013-12-19 20:36:29 UTC
*** Bug 1044554 has been marked as a duplicate of this bug. ***

Comment 4 kerrmichaeld 2014-01-09 04:57:03 UTC
Description of problem:
Simply ran 'optirun glxgears-info' after installing bumblebee with nvidia drivers https:fedoraproject.org/wiki/Bumblebee#fedora_20

Additional info:
reporter:       libreport-2.1.10
hashmarkername: setroubleshoot
kernel:         3.12.6-300.fc20.x86_64
type:           libreport

Comment 5 Lukas Vrabec 2014-07-15 12:24:35 UTC
#============= bumblebee_t ==============

#!!!! This avc is allowed in the current policy
allow bumblebee_t xdm_tmp_t:dir remove_name;

#!!!! This avc is allowed in the current policy
allow bumblebee_t xdm_tmp_t:sock_file unlink;

Comment 7 Fedora End Of Life 2015-05-29 10:01:50 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

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

Comment 8 Fedora End Of Life 2015-06-30 00:47:05 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.


Note You need to log in before you can comment on or make changes to this bug.