Description of problem: # yum update Updating : xorg-x11-xinit-1.0.9-16.fc12.x86_64 78/172 warning: user mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: user mockbuild does not exist - using root Version-Release number of selected component (if applicable): xorg-x11-xinit-1.0.9-16.fc12.x86_64 How reproducible: Always. Steps to Reproduce: 1. rpm -qlv xorg-x11-xinit Actual results: # rpm -qlv xorg-x11-xinit -rw-r--r-- 1 root root 547 Jul 13 17:47 /etc/X11/Xmodmap -rw-r--r-- 1 root root 493 Jul 13 17:47 /etc/X11/Xresources drwxr-xr-x 2 root root 0 Jul 13 17:47 /etc/X11/xinit -rwxr-xr-x 1 root root 2030 Jul 13 17:47 /etc/X11/xinit/Xclients drwxr-xr-x 2 root root 0 Jul 13 17:47 /etc/X11/xinit/Xclients.d -rwxr-xr-x 1 root root 3547 Jul 13 17:47 /etc/X11/xinit/Xsession -rwxr-xr-x 1 root root 1486 Jul 13 17:47 /etc/X11/xinit/xinitrc -rw-r--r-- 1 root root 1965 Jul 13 17:47 /etc/X11/xinit/xinitrc-common drwxr-xr-x 2 root root 0 Jul 13 17:47 /etc/X11/xinit/xinitrc.d -rwxr-xr-x 1 root root 543 Jul 13 17:47 /etc/X11/xinit/xinitrc.d/localuser.sh -rwxr-xr-x 1 mockbuilroot 6116 Jul 13 17:47 /usr/bin/ck-xinit-session -rwxr-xr-x 1 mockbuilroot 4423 Jul 13 17:47 /usr/bin/startx -rwxr-xr-x 1 mockbuilroot 14152 Jul 13 17:47 /usr/bin/xinit -rwxr-xr-x 1 mockbuilroot 132 Jul 13 17:47 /usr/libexec/xinit-compat drwxr-xr-x 2 root root 0 Jul 13 17:47 /usr/share/doc/xorg-x11-xinit-1.0.9 -rw-r--r-- 1 root root 1148 May 21 2008 /usr/share/doc/xorg-x11-xinit-1.0.9/COPYING -rw-r--r-- 1 root root 26924 May 21 2008 /usr/share/doc/xorg-x11-xinit-1.0.9/ChangeLog -rw-r--r-- 1 root root 270 May 21 2008 /usr/share/doc/xorg-x11-xinit-1.0.9/README -rw-r--r-- 1 root root 2466 Jul 13 17:47 /usr/share/man/man1/startx.1.gz -rw-r--r-- 1 root root 3128 Jul 13 17:47 /usr/share/man/man1/xinit.1.gz Expected results: Proper file ownership. Additional info: Bug seems fixed in fc13, but still present in fc12.
*** This bug has been marked as a duplicate of bug 623702 ***
*** This bug has been marked as a duplicate of bug 617640 ***