Bug 772325 - SELinux is preventing /usr/libexec/kde4/lnusertemp from 'create' accesses on the Verzeichnis .kde.
Summary: SELinux is preventing /usr/libexec/kde4/lnusertemp from 'create' accesses on ...
Keywords:
Status: CLOSED DUPLICATE of bug 769810
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 16
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:43e36891067671c50a7ae8aaa89...
: 984407 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-06 20:34 UTC by Alexander
Modified: 2013-07-16 08:56 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-01-16 22:11:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Alexander 2012-01-06 20:34:13 UTC
libreport version: 2.0.8
executable:     /usr/bin/python
hashmarkername: setroubleshoot
kernel:         3.1.6-1.fc16.i686
reason:         SELinux is preventing /usr/libexec/kde4/lnusertemp from 'create' accesses on the Verzeichnis .kde.
time:           Fr 06 Jan 2012 21:33:28 CET

description:
:SELinux is preventing /usr/libexec/kde4/lnusertemp from 'create' accesses on the Verzeichnis .kde.
:
:*****  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 lnusertemp should be allowed create access on the .kde 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 lnusertemp /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:admin_home_t:s0
:Target Objects                .kde [ dir ]
:Source                        lnusertemp
:Source Path                   /usr/libexec/kde4/lnusertemp
:Port                          <Unbekannt>
:Host                          (removed)
:Source RPM Packages           kdelibs-4.7.2-5.fc16
:Target RPM Packages           
:Policy RPM                    selinux-policy-3.10.0-51.fc16
:Selinux Enabled               True
:Policy Type                   targeted
:Enforcing Mode                Enforcing
:Host Name                     (removed)
:Platform                      Linux (removed) 3.1.0-7.fc16.i686 #1 SMP Tue Nov 1
:                              21:00:16 UTC 2011 i686 i686
:Alert Count                   1
:First Seen                    Sa 05 Nov 2011 22:36:29 CET
:Last Seen                     Sa 05 Nov 2011 22:36:29 CET
:Local ID                      6d9fdaf6-f104-489b-8541-7e8552f8a9a9
:
:Raw Audit Messages
:type=AVC msg=audit(1320528989.360:48): avc:  denied  { create } for  pid=1138 comm="lnusertemp" name=".kde" scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:admin_home_t:s0 tclass=dir
:
:
:type=SYSCALL msg=audit(1320528989.360:48): arch=i386 syscall=mkdir success=no exit=EACCES a0=bfcaaa79 a1=1c0 a2=bfcaaa79 a3=bfcaaa18 items=0 ppid=1124 pid=1138 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=lnusertemp exe=/usr/libexec/kde4/lnusertemp subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null)
:
:Hash: lnusertemp,xdm_t,admin_home_t,dir,create
:
:audit2allow
:
:#============= xdm_t ==============
:#!!!! This avc can be allowed using the boolean 'allow_polyinstantiation'
:
:allow xdm_t admin_home_t:dir create;
:
:audit2allow -R
:
:#============= xdm_t ==============
:#!!!! This avc can be allowed using the boolean 'allow_polyinstantiation'
:
:allow xdm_t admin_home_t:dir create;
:

Comment 1 Miroslav Grepl 2012-01-09 09:51:41 UTC
Are you trying to log in as root?

Comment 2 Alexander 2012-01-09 20:59:31 UTC
No, I don't.
The mistake was during normally using as user.
I use the root-mode only in the bash.

Comment 3 Carl G. 2012-01-16 22:11:17 UTC

*** This bug has been marked as a duplicate of bug 769810 ***

Comment 4 Miroslav Grepl 2013-07-16 08:56:56 UTC
*** Bug 984407 has been marked as a duplicate of this bug. ***


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