Bug 791063

Summary: SELinux is preventing /bin/systemd-tmpfiles from 'setattr' accesses on the None ksocket-dallas.
Product: [Fedora] Fedora Reporter: dallas.molyneux
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: dominick.grift, dwalsh, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f3f4353572bdb2ee4973210623e08c64d04d7cba40efbe06d9df729f9bba4b14
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-15 17:08:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Files that were logged in connetion to this none

Description dallas.molyneux 2012-02-16 02:33:09 UTC
libreport version: 2.0.8
executable:     /usr/bin/python
hashmarkername: setroubleshoot
kernel:         3.2.2-1.fc16.x86_64
reason:         SELinux is preventing /bin/systemd-tmpfiles from 'setattr' accesses on the None ksocket-dallas.
time:           Wed 15 Feb 2012 07:25:17 PM MST

description:
:SELinux is preventing /bin/systemd-tmpfiles from 'setattr' accesses on the None ksocket-dallas.
:
:*****  Plugin catchall (100. confidence) suggests  ***************************
:
:If you believe that systemd-tmpfiles should be allowed setattr access on the ksocket-dallas <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 systemd-tmpfile /var/log/audit/audit.log | audit2allow -M mypol
:# semodule -i mypol.pp
:
:Additional Information:
:Source Context                system_u:system_r:systemd_tmpfiles_t:s0
:Target Context                unconfined_u:object_r:user_home_dir_t:s0
:Target Objects                ksocket-dallas [ None ]
:Source                        systemd-tmpfile
:Source Path                   /bin/systemd-tmpfiles
:Port                          <Unknown>
:Host                          (removed)
:Source RPM Packages           systemd-units-37-11.fc16.x86_64
:Target RPM Packages           
:Policy RPM                    selinux-policy-3.10.0-75.fc16.noarch
:Selinux Enabled               True
:Policy Type                   targeted
:Enforcing Mode                Enforcing
:Host Name                     (removed)
:Platform                      Linux (removed) 3.2.2-1.fc16.x86_64 #1 SMP
:                              Thu Jan 26 03:21:58 UTC 2012 x86_64 x86_64
:Alert Count                   1
:First Seen                    Wed 15 Feb 2012 07:23:49 PM MST
:Last Seen                     Wed 15 Feb 2012 07:23:49 PM MST
:Local ID                      5a9b7b1b-eeab-4a99-b2bf-a10f1ba2c57a
:
:Raw Audit Messages
:type=AVC msg=audit(1329359029.49:107): avc:  denied  { setattr } for  pid=2345 comm="systemd-tmpfile" name="ksocket-dallas" dev=dm-1 ino=396646 scontext=system_u:system_r:systemd_tmpfiles_t:s0 tcontext=unconfined_u:object_r:user_home_dir_t:s0 tclass=dirnode=(removed) type=SYSCALL msg=audit(1329359029.049:107): arch=c000003e syscall=280 success=no exit=-13 a0=5 a1=0 a2=7ffffc25fc20 a3=0 items=0 ppid=1 pid=2345 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-tmpfile" exe="/bin/systemd-tmpfiles" subj=system_u:system_r:systemd_tmpfiles_t:s0 key=(null)
:
:
:Hash: systemd-tmpfile,systemd_tmpfiles_t,user_home_dir_t,None,setattr
:
:audit2allow
:
:
:audit2allow -R
:
:

Comment 1 Miroslav Grepl 2012-02-16 11:28:31 UTC
What does

find /tmp -name ksocket-dallas

or

find /var/tmp  -name ksocket-dallas

Do you use KDE?

Comment 2 dallas.molyneux 2012-02-16 12:38:14 UTC
Created attachment 562481 [details]
Files that were logged in connetion to this

The attached file is all the files related to this bug I reported.

Comment 3 dallas.molyneux 2012-02-16 12:42:07 UTC
I use Gnome. not kde. 

I was launching Streamtuner2 when it gave me this but it has done it at random times.

It started after system updated to gnome3 and has also seemed to break other things as well.

Sorry for my lack of. I'm still some what new to Linux.

Comment 4 Daniel Walsh 2012-02-16 16:22:41 UTC
You should just clean out your /tmp and then the problem will probably go away.  This is one of the reasons I use tmpfs for /tmp, that way old cruft gets cleaned out on reboot.