Bug 690326

Summary: SELinux is preventing /usr/bin/gnome-session from 'setattr' accesses on the directory /tmp/at-spi2/.
Product: [Fedora] Fedora Reporter: Thomas Meyer <thomas.mey>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: dwalsh, igeorgex, mgrepl, thomas.mey
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: setroubleshoot_trace_hash:5790fa42a2819e08e3098895abbea7f69adcd4d4af14945fee2bf216e0f20ac3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-07 13:49:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Thomas Meyer 2011-03-23 22:40:37 UTC
SELinux is preventing /usr/bin/gnome-session from 'setattr' accesses on the directory /tmp/at-spi2/.

*****  Plugin catchall_boolean (89.3 confidence) suggests  *******************

If you want to enable polyinstantiated directory support.
Then you must tell SELinux about this by enabling the 'allow_polyinstantiation' boolean.
Do
setsebool -P allow_polyinstantiation 1

*****  Plugin catchall (11.6 confidence) suggests  ***************************

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

Additional Information:
Source Context                system_u:system_r:xdm_t:s0-s0:c0.c1023
Target Context                system_u:object_r:tmp_t:s0
Target Objects                /tmp/at-spi2/ [ dir ]
Source                        gnome-session
Source Path                   /usr/bin/gnome-session
Port                          <Unbekannt>
Host                          (removed)
Source RPM Packages           gnome-power-manager-2.91.92-2.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 Wed Mar 23
                              17:45:22 CET 2011 i686 i686
Alert Count                   9
First Seen                    Do 24 Mär 2011 00:36:02 CET
Last Seen                     Do 24 Mär 2011 00:36:08 CET
Local ID                      345c183a-e008-4e02-bf4a-205dc3c0eade

Raw Audit Messages
type=AVC msg=audit(1300923368.118:44): avc:  denied  { setattr } for  pid=1098 comm="gnome-power-man" name="at-spi2" dev=sda2 ino=396251 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:tmp_t:s0 tclass=dir


type=SYSCALL msg=audit(1300923368.118:44): arch=i386 syscall=chmod success=no exit=EACCES a0=b74377bd a1=3ff a2=b743e9b8 a3=b743f7c0 items=1 ppid=1 pid=1098 auid=4294967295 uid=42 gid=481 euid=42 suid=42 fsuid=42 egid=481 sgid=481 fsgid=481 tty=(none) ses=4294967295 comm=gnome-power-man exe=/usr/bin/gnome-power-manager subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null)

type=CWD msg=audit(1300923368.118:44): cwd=/

type=PATH msg=audit(1300923368.118:44): item=0 name=/tmp/at-spi2/ inode=396251 dev=08:02 mode=041777 ouid=42 ogid=481 rdev=00:00 obj=system_u:object_r:tmp_t:s0

Hash: gnome-session,xdm_t,tmp_t,dir,setattr

audit2allow

#============= xdm_t ==============
#!!!! This avc can be allowed using the boolean 'allow_polyinstantiation'

allow xdm_t tmp_t:dir setattr;

audit2allow -R

#============= xdm_t ==============
#!!!! This avc can be allowed using the boolean 'allow_polyinstantiation'

allow xdm_t tmp_t:dir setattr;

Comment 1 Daniel Walsh 2011-04-17 09:06:54 UTC
Have you seen this happen again or was this just after a fresh install?

Comment 2 Miroslav Grepl 2011-10-07 13:49:22 UTC
If the problem still persists, please reopen the bug.