Red Hat Bugzilla – Bug 120885
xorg-x11 changes give MapVidMem problems accessing /dev/mem
Last modified: 2007-11-30 17:10:40 EST
Description of problem: policy-1.11.2-3 installed. xorg-x11-*-6.7.0-0.4 installed With enforcing=1 and runlevel=5 boot, gdm (and X) have a problem during startup causing X not to start. The problem is that MapVidMem cannot access /dev/mem: crw-r-----+ root kmem system_u:object_r:memory_device_t /dev/mem I am attaching the last 200 lines from /var/log/messages which have the relevant "denied" messages.
Created attachment 99428 [details] /var/log/messages
This is a file context file problem caused by Xorg running under the wrong context. You need policy-1.11.2-3 and to restorecon /usr/bin/X11/Xorg /var/log/Xorg*
As I explained elsewhere, you need to run: restorecon /usr/X11R6/bin/Xorg rather than restorecon /usr/bin/X11/Xorg since /etc/security/selinux/src/policy/* only specified /usr/X11R6/bin/Xorg for xserver_exec_t
BTW, this info needs posting on the mailing list. Just installing the new policy (assume it will be in tomorrows development), does not fix things. One thing I have learned out of this is that the complete path to a file makes a really big difference as to what attributes it is assigned and symlinks can really screw things up. I seem to remember that Mike Harris mentioned wanting to get rid of all the X11 and /usr/X11R6 stuff and put everything into /usr/bin ... that sure would make things simpler.