selinux-policy-strict-1.17.2-1 I'm seeing the following at startup. I have to boot to runlevel 3 because X won't start since it "could not open default font 'fixed'". Service xfs is reported running but non functional. Aug 25 23:27:36 k6-joy xfs: xfs startup succeeded Aug 25 23:27:36 k6-joy kernel: audit(1093469256.744:0): avc: denied { getattr } for pid=2171 exe=/usr/X11R6/bin/xfs path=/tmp/.font-unix dev=hda6 ino=425186 scontext=system_u:system_r:xfs_ttcontext=system_u:object_r:initrc_tmp_t tclass=dir Aug 25 23:27:36 k6-joy xfs[2171]: cannot establish any listening sockets Aug 25 23:27:37 k6-joy xfs[2171]: ignoring font path element /usr/X11R6/lib/X11/fonts/Speedo (unreadable) Running a fixfiles relabel did not fix this issue. Removing /tmp/.font-unix by hand and rebooting doesn't fix the situation: root 2372 0.5 0.8 12196 2304 ? Ss 01:11 0:00 /usr/bin/gdm-binary -nodaemon root 2917 0.1 0.4 5312 1120 ? Ss 01:11 0:00 /bin/sh/etc/X11/gdm/XKeepsCrashing root 2934 0.0 0.0 2432 252 ? S 01:11 0:00 /usr/libexec/gdmopen -l /bin/sh -c /etc/X11/gdm/XKeepsCrashing -noopen root 2947 0.3 0.4 5168 1124 tty8 Ss+ 01:11 0:00 /bin/sh/etc/X11/gdm/XKeepsCrashing -noopen root 3007 0.0 0.3 5020 1016 tty8 S+ 01:11 0:00 /usr/bin/dialog --yesno I cannot start the X server (your graphicalinterface). It is likely that it is not set up correctly. Would youlike to view the X server output to diagnose the problem? 10 50 [root@k6-joy tmp]# ls -aZd .font-unix drwxrwxrwt root root system_u:object_r:initrc_tmp_t .font-unix
On Thu, 2004-08-26 at 14:06, Stephen Smalley wrote: /etc/init.d/xfs needs to restorecon /tmp/.font-unix after re-creating it (previously, it was getting re-created by xfs itself, and the policy automatically put it into the right type using a file_type_auto_trans rule from xfs_t).
Created attachment 103644 [details] Restorecon patch for xfs startup script This patch will work whether or not SELinux is enabled, since restorecon will exit 0 if it is not enabled.
Why was this report closed a duplicate? And a duplicate of which bug would it be?
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.