Bug 791358

Summary: SELinux is preventing /usr/libexec/gnome-settings-daemon from 'write' accesses on the None native.
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: dominick.grift, dwalsh, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:7793ba085e55255b64c1b64cd49aaf94afeaadb48a032b620820b478652932a9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-17 21:54:32 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 Adam Williamson 2012-02-16 20:21:49 UTC
libreport version: 2.0.8
executable:     /usr/bin/python
hashmarkername: setroubleshoot
kernel:         3.3.0-0.rc3.git4.1.1.fc17.x86_64
reason:         SELinux is preventing /usr/libexec/gnome-settings-daemon from 'write' accesses on the None native.
time:           Thu 16 Feb 2012 12:21:41 PM PST

description:
:SELinux is preventing /usr/libexec/gnome-settings-daemon from 'write' accesses on the None native.
:
:*****  Plugin catchall (100. confidence) suggests  ***************************
:
:If you believe that gnome-settings-daemon should be allowed write access on the native <Unknown> 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-settings- /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                native [ None ]
:Source                        gnome-settings-
:Source Path                   /usr/libexec/gnome-settings-daemon
:Port                          <Unknown>
:Host                          (removed)
:Source RPM Packages           gnome-shell-3.3.5-2.fc17.x86_64
:Target RPM Packages           
:Policy RPM                    selinux-policy-3.10.0-88.fc17.noarch
:Selinux Enabled               True
:Policy Type                   targeted
:Enforcing Mode                Enforcing
:Host Name                     (removed)
:Platform                      Linux (removed)
:                              3.3.0-0.rc3.git4.1.1.fc17.x86_64 #1 SMP Tue Feb 14
:                              02:44:04 UTC 2012 x86_64 x86_64
:Alert Count                   10
:First Seen                    Tue 14 Feb 2012 07:05:48 PM PST
:Last Seen                     Wed 15 Feb 2012 01:11:40 PM PST
:Local ID                      17135e57-c4fa-419c-a382-55fbb9d57455
:
:Raw Audit Messages
:type=AVC msg=audit(1329340300.641:87): avc:  denied  { write } for  pid=1209 comm="gnome-shell" name="native" dev="dm-2" ino=270943 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:tmp_t:s0 tclass=sock_filenode=(removed) type=SYSCALL msg=audit(1329340300.641:87): arch=c000003e syscall=42 success=no exit=-13 a0=1a a1=7fff3dd397c0 a2=6e a3=7fff3dd3970c items=0 ppid=1 pid=1209 auid=42 uid=42 gid=42 euid=42 suid=42 fsuid=42 egid=42 sgid=42 fsgid=42 tty=(none) ses=1 comm="gnome-shell" exe="/usr/bin/gnome-shell" subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null)
:
:
:Hash: gnome-settings-,xdm_t,tmp_t,None,write
:
:audit2allow
:
:
:audit2allow -R
:
:

Comment 1 Miroslav Grepl 2012-02-20 15:36:31 UTC
Could it be caused by systemd issue?

If you clean up your /tmp, does it happen again?

Comment 2 Miroslav Grepl 2012-02-20 15:36:55 UTC
*** Bug 791357 has been marked as a duplicate of this bug. ***

Comment 3 Daniel Walsh 2012-02-20 19:27:35 UTC
This might be a left over files on a fresh install.  /tmp should probably be cleaned after install?

Comment 4 Adam Williamson 2012-02-21 02:33:57 UTC
hum, yeah, this could be the private /tmp issue i guess. if i just wipe all those private /tmp dirs, will anything break, or will systemd just recreate them?



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 5 Daniel Walsh 2012-02-21 13:39:48 UTC
I don't think this is a private tmp issue.  I think it is trying to write to a sock_file that was created with the wrong label, perhaps when SELinux was in permissive mode?  /tmp can not be easily cleaned.

Comment 6 Miroslav Grepl 2012-10-17 09:06:29 UTC
Are you still getting this issue?

Comment 7 Adam Williamson 2012-10-17 21:54:32 UTC
I don't recall seeing this lately, no. I'll re-file if it pops up again.