Summary: SELinux is preventing /usr/libexec/gdm-session-worker "write" access on /root. Detailed Description: SELinux denied access requested by gdm-session-wor. It is not expected that this access is required by gdm-session-wor and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access. Allowing Access: You can generate a local policy module to allow this access - see FAQ (http://fedora.redhat.com/docs/selinux-faq-fc5/#id2961385) Please file a bug report. 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 /root [ dir ] Source gdm-session-wor Source Path /usr/libexec/gdm-session-worker Port <Unknown> Host (removed) Source RPM Packages gdm-2.28.1-24.fc12 Target RPM Packages filesystem-2.4.30-2.fc12 Policy RPM selinux-policy-3.6.32-49.fc12 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.31.6-145.fc12.i686 #1 SMP Sat Nov 21 16:28:23 EST 2009 i686 i686 Alert Count 2 First Seen Thu 03 Dec 2009 10:51:04 AM EST Last Seen Thu 03 Dec 2009 10:51:04 AM EST Local ID cdf26dd4-5864-499c-8981-c57de945160d Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1259855464.673:39): avc: denied { write } for pid=5640 comm="gdm-session-wor" name="root" dev=sda3 ino=16397 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:admin_home_t:s0 tclass=dir node=(removed) type=SYSCALL msg=audit(1259855464.673:39): arch=40000003 syscall=5 success=no exit=-13 a0=8c18380 a1=80c2 a2=180 a3=1e items=0 ppid=5597 pid=5640 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4 comm="gdm-session-wor" exe="/usr/libexec/gdm-session-worker" subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null) Hash String generated from selinux-policy-3.6.32-49.fc12,catchall,gdm-session-wor,xdm_t,admin_home_t,dir,write audit2allow suggests: #============= xdm_t ============== allow xdm_t admin_home_t:dir write;
Logging in directly as root from X Windows is not supported with SELinux, It is considered too dangerous and the amount/type of policy that would needed to be written, would allow too much access. Either put the machin in permissive mode when you login as root, or login as a normal user and use su or sudo to reach root.
*** Bug 543972 has been marked as a duplicate of this bug. ***
*** Bug 541639 has been marked as a duplicate of this bug. ***
*** Bug 544475 has been marked as a duplicate of this bug. ***
*** Bug 545412 has been marked as a duplicate of this bug. ***
*** Bug 547931 has been marked as a duplicate of this bug. ***
*** Bug 547933 has been marked as a duplicate of this bug. ***
*** Bug 548997 has been marked as a duplicate of this bug. ***
*** Bug 533636 has been marked as a duplicate of this bug. ***
*** Bug 541153 has been marked as a duplicate of this bug. ***
*** Bug 550210 has been marked as a duplicate of this bug. ***
*** Bug 550364 has been marked as a duplicate of this bug. ***
*** Bug 550659 has been marked as a duplicate of this bug. ***
*** Bug 550661 has been marked as a duplicate of this bug. ***
*** Bug 551460 has been marked as a duplicate of this bug. ***
*** Bug 551485 has been marked as a duplicate of this bug. ***
*** Bug 551504 has been marked as a duplicate of this bug. ***
*** Bug 551905 has been marked as a duplicate of this bug. ***
*** Bug 551654 has been marked as a duplicate of this bug. ***
*** Bug 551653 has been marked as a duplicate of this bug. ***
*** Bug 551652 has been marked as a duplicate of this bug. ***
*** Bug 551903 has been marked as a duplicate of this bug. ***
*** Bug 543062 has been marked as a duplicate of this bug. ***
*** Bug 557549 has been marked as a duplicate of this bug. ***
*** Bug 557550 has been marked as a duplicate of this bug. ***
*** Bug 557945 has been marked as a duplicate of this bug. ***
*** Bug 559328 has been marked as a duplicate of this bug. ***
*** Bug 559619 has been marked as a duplicate of this bug. ***
*** Bug 559617 has been marked as a duplicate of this bug. ***
*** Bug 560280 has been marked as a duplicate of this bug. ***
*** Bug 560363 has been marked as a duplicate of this bug. ***
*** Bug 560836 has been marked as a duplicate of this bug. ***
*** Bug 560837 has been marked as a duplicate of this bug. ***
*** Bug 561533 has been marked as a duplicate of this bug. ***
*** Bug 562161 has been marked as a duplicate of this bug. ***
*** Bug 563088 has been marked as a duplicate of this bug. ***
*** Bug 565282 has been marked as a duplicate of this bug. ***
*** Bug 565644 has been marked as a duplicate of this bug. ***
*** Bug 567990 has been marked as a duplicate of this bug. ***
*** Bug 570873 has been marked as a duplicate of this bug. ***
*** Bug 568323 has been marked as a duplicate of this bug. ***
*** Bug 574653 has been marked as a duplicate of this bug. ***
*** Bug 577661 has been marked as a duplicate of this bug. ***
*** Bug 585524 has been marked as a duplicate of this bug. ***
*** Bug 587358 has been marked as a duplicate of this bug. ***
*** Bug 592629 has been marked as a duplicate of this bug. ***
*** Bug 595530 has been marked as a duplicate of this bug. ***
*** Bug 599121 has been marked as a duplicate of this bug. ***
*** Bug 599125 has been marked as a duplicate of this bug. ***
*** Bug 630492 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > Logging in directly as root from X Windows is not supported with SELinux, It > is considered too dangerous and the amount/type of policy that would needed to > be written, would allow too much access. > > > Either put the machin in permissive mode when you login as root, or login as a > normal user and use su or sudo to reach root. So tell me again why should not be allowed to trash my own machine....
You can go right a head. I would tell you to disable SELinux or put it in permissive mode and go to town. But a security mechanism is not going to allow what looks like apps attacking the /root directory and other capabilities that come along with logging in as root.