Hide Forgot
kdm (and may be other dms as well) create names pipes in the /var/run/xdmctl directory. According to file_contexts, /var/run/xdmctl is supposed to be xdm_var_run_t (which is the correct thing, IMHO), but it ends up being created as just var_run_t instead. I am guessing that something like type_transition xdm_t var_run_t:dir xdm_var_run_t; is needed. (Note that the same thing for :file already exists in policy.conf). Another workaround is adding type_transition xdm_t var_run_t:fifo_file xdm_var_run_t; which allows creating named pipes in /var/run/xdmctl even when it is marked var_run_t.
Fixed in selinux-policy-strict-1.13.2-7.src.rpm
Fixed in Rawhide
I'm getting this error with FC4 and selinux-policy-targeted-1.27.1-2.18. Is this be fixed in targeted?
After upgrading a bunch of kde packages which includes kdebase-3.5.1-1.4.fc4.kde. The message "rm: cannot remove '/var/run/xdmctl/dmctl' is a directory" no longer appears during boot. File context for /var/run/xdmctl has not changed it is still var_run_t.
My bad. I need to resist immediate updating of bug reports. The message "rm: cannot remove '/var/run/xdmctl/dmctl': Is a directory" reappeared after upgrading the following packages: xorg-x11-6.8.2-37.FC4.49.2.i386.rpm xorg-x11-deprecated-libs-6.8.2-37.FC4.49.2.i386.rpm xorg-x11-deprecated-libs-devel-6.8.2-37.FC4.49.2.i386.rpm xorg-x11-devel-6.8.2-37.FC4.49.2.i386.rpm xorg-x11-font-utils-6.8.2-37.FC4.49.2.i386.rpm xorg-x11-libs-6.8.2-37.FC4.49.2.i386.rpm xorg-x11-Mesa-libGL-6.8.2-37.FC4.49.2.i386.rpm xorg-x11-Mesa-libGLU-6.8.2-37.FC4.49.2.i386.rpm xorg-x11-tools-6.8.2-37.FC4.49.2.i386.rpm xorg-x11-twm-6.8.2-37.FC4.49.2.i386.rpm xorg-x11-xauth-6.8.2-37.FC4.49.2.i386.rpm xorg-x11-xdm-6.8.2-37.FC4.49.2.i386.rpm xorg-x11-xfs-6.8.2-37.FC4.49.2.i386.rpm If this bug has been fixed why does this message still occur when KDM is enabled?
What avc messages are you seeing? Dan
There are no AVC messages in /var/log/audit/audit.log regarding this error. The error message appears immediately after "Enabling local filesystem quotas" is displayed which is several processes before auditd is started.
Is /var/run/xdmctl/dmctl a directory? Does this happen if you setenforce 0? If yes then this is not an SELinux problem.
1. The file_context for /var/run/xdmctl changed to xdm_var_run_t after upgrading to selinux-policy-targeted-1.27.1-2.22. So as far as this bug is concerned all is fixed. 2. /var/run/xdmctl/dmctl is a directory. When selinux=0 is set in grub the error still occurs. Therefore not a selinux, but a KDM problem. I'll check to see if it is worthwhile entering a bug with KDE.