"/etc/init.d/xfs start" gives an error after an upgrade to xorg-x11-6.8.0-r4 and doesn't start. I have xfs in my use flags and have tried re-emerging xorg-x11 several times. Reproducible: Always Steps to Reproduce: 1.upgrade xorg-x11-6.8.0-r4 2.give command "/etc/init.d/xfs start" 3. Actual Results: * Scanning font directories ... find: /usr/share/fonts/encodings/fonts.dir: No such file or directory [ ok ] * Indexing font directories ... * /usr/share/fonts/ukr ... [ ok ] * /usr/local/share/fonts/TTF ... [ ok ] * /usr/X11R6/lib/X11/fonts/TTF ... [ ok ] * Updating FC cache ... [ ok ] * Starting X Font Server ... start-stop-daemon: stat /usr/X11R6/bin/xfs: No such file or directory [ !! ] Expected Results: The X Font Server should have started. Portage 2.0.51-r8 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-shadow-workstation-r1 i686) ================================================================= System uname: 2.6.9-shadow-workstation-r1 i686 Pentium III (Coppermine) Gentoo Base System version 1.6.7 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Dec 4 2004, 12:36:43)] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.3 sys-devel/binutils: 2.15.94.0.1, 2.15.92.0.2-r1 sys-devel/libtool: 1.5.2-r7 virtual/os-headers: 2.6.8.1-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium3 -mtune=i686 -O2 -funroll-loops -pipe -fno-unit-at-a-time" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium3 -mtune=i686 -O2 -funroll-loops -pipe -fno-unit-at-a-time" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://open-systems.ufl.edu/mirrors/gentoo/ http://mirror.clarkson.edu/pub/distributions/gentoo/ http://gentoo.chem.wisc.edu/gentoo/ http://mirrors.acm.cs.rpi.edu/gentoo/ http://mirror.datapipe.net/gentoo http://mirror.uni-c.dk/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="X alsa arts avi berkdb bitmap-fonts cdr crypt cups encode esd f77 fam flacfoomaticdb fortran gdbm gif gimp gimpprint gphoto2 gstreamer gtk gtk2 imagemagick imap imlib java jpeg kde ldap libg++ libwww mad maildir mikmod motif mpeg ncurses nls nptl nptlonly oav oggvorbis opengl oss pdflib perl png ppds python qt quicktime readline samba sdl slang spell ssl svga tcltk tcpd tetex tiff truetype x86 xfs xml xml2 xmms xv zlib"
It is a ~ (=testing) ebuild and the flag name changed afaik, since it collided with xfs (the fs). Please reopen, if this is not the case.
yes... a quick look at the IUSE reveals among other the new USE flags: font-server truetype-fonts type1-fonts
