XFS has as of late taken on the behavior of rescanning font directories every time it's reloaded (i.e. when starting up or doing a manual restart on the initscript), even when nothing has changed. I don't remember it doing this before. A typical output is: scales log # /etc/init.d/xfs restart * Stopping X Font Server... [ ok ] * Scanning font directories... [ ok ] * Indexing font directories... * /usr/share/fonts/75dpi... [ ok ] * /usr/share/fonts/corefonts... [ ok ] * /usr/X11R6/lib/X11/fonts/corefonts... [ ok ] * /usr/X11R6/lib/X11/fonts/75dpi... [ ok ] * Updating FC cache... [ ok ] * Starting X Font Server... But that's not all. I then get lots of warnings in my log file: scales log # tail everything/current Mar 28 20:56:40 [xfs] terminating_ Mar 28 20:56:58 [xfs] CONFIG: unknown parameter "cache-hi-mark"_ Mar 28 20:56:58 [xfs] CONFIG: unknown parameter "cache-low-mark"_ Mar 28 20:56:58 [xfs] CONFIG: unknown parameter "cache-balance"_ Mar 28 20:56:58 [xfs] ignoring font path element /usr/share/fonts/util (unreadable)_ Mar 28 20:56:58 [xfs] ignoring font path element /usr/share/fonts/local (unreadable)_ Mar 28 20:56:58 [xfs] ignoring font path element /usr/local/share/fonts (unreadable)_ Mar 28 20:56:58 [xfs] ignoring font path element /usr/share/fonts (unreadable)_ Mar 28 20:56:58 [xfs] ignoring font path element /usr/X11R6/lib/X11/fonts (unreadable)_ Mar 28 20:56:58 [xfs] ignoring font path element /usr/share/fonts/default (unreadable)_ I don't know why cache-{hi,low}-mark, etc, causes problems -- I certainly didn't add them in there myself, so I would imagine they were in there by default. Additionally, all those font paths that it states are unreadable are perfectly readable (for instance, /usr/share/fonts/util is owned by root:root with 755 permissions). I don't know why XFS is so upset... Reproducible: Always Steps to Reproduce: 1. Start/Restart the xfs init script. 2. 3. Actual Results: Lots of warnings, and excessive amounts of rescanning/recaching font directories. Expected Results: The opposite of the actual results? :-) scales log # emerge info Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20041102-r1, 2.6.11-ck3 i686) ================================================================= System uname: 2.6.11-ck3 i686 Intel(R) Pentium(R) M processor 1700MHz Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Mar 20 2005, 11:41:26)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium3 -pipe -fomit-frame-pointer" 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/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="x86 X a52 aac acpi aim alsa apache2 apm arts audiofile avi bash-completion berkdb bitmap-fonts bluetooth bzlib calendar cdparanoia cdr crypt cups curl divx4linux dvd dvdr dvdread emboss encode esd exif expat fam ffmpeg flac font-server foomaticdb fortran ftp gd gdbm gif gphoto2 gpm gstreamer gtk gtk2 hal icq imagemagick imapimlib jabber java javascript jikes joystick jpeg kde libg++ libwww mad maildir mbox mikmod mime mmap mmx motif mozilla mp3 mpeg msn mysql mysqli ncurses nls nptl oggoggvorbis opengl oscar oss pam pdflib perl php png pnp python qt quicktime readline recode samba sdl sharedext sharedmem slang slp sndfile sockets spell sse ssl svg svga sysfs tcpd tetex threads tiff tokenizer truetype truetype-fonts type1-fonts unicode usb vcd wifi wxwindows xine xml2 xosd xpm xv xvid yahoo zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Unreadable doesn't necessarily mean permissions. It can mean the fonts aren't installed properly, or they're corrupt.
That's true, although I'm not sure how either would have happened, as everything was built from portage and not touched since. Any ideas how to fix these problems?
Considering your kernel, I can only assume you're running 6.8.2. Has this problem occurred only after upgrading, and did you notice it right after or did it take some time to appear?
Created attachment 54960 [details, diff] xfs.diff Try this small patch to the xfs init script.
Anyway that should help some stuff related to incorrect font setup. Also you need to specify the directories fonts are actually in within /etc/X11/fs/config, because it's not recursive. So if fonts aren't in those dirs, pull the dirs from the config.
That patch didn't do too much, just caused something new to be printed out (only once): * Re-caching dependency info (mtimes differ)... Anyways, I looked at that config file. I noticed that there were redundant entries -- for instance, on my Gentoo system /usr/X11R6/lib/X11/fonts is the same thing as /usr/share/fonts so I got rid of two of the lines and now I only get the complaints about /usr/share/fonts/75dpi and /usr/share/fonts/corefonts. I don't know when the problem appeared exactly, but I do know that corefonts, at least, were installed (through Portage) after my initial system build. Maybe the 75-dpi fonts were too -- so maybe what's happening is that when the new fonts were emerged they didn't integrate with XFS correctly? I'm thinking of re-emerging XFS and seeing if that fixes problems unless you'd rather I didn't and keep trying to figure out what's going wrong as my system currently is. Thanks for your help so far.
xfs is part of xorg-x11, as are the 75 dpi fonts. I wouldn't expect re-merging to fix things, but there's the off chance that it could. If you could check the contents of the fonts.* files in the relevant directories and confirm that there _are_ some contents besides "0," I'd appreciate it. I've got these files, and I don't get your error messages: donnie@supernova ~ $ ls /usr/share/fonts/75dpi/fonts.* -l -r--r--r-- 1 root root 3066 Mar 4 21:50 /usr/share/fonts/75dpi/fonts.alias -rw-r--r-- 1 root root 218960 Mar 4 21:51 /usr/share/fonts/75dpi/fonts.cache-1 -rw-r--r-- 1 root root 165343 Mar 4 21:51 /usr/share/fonts/75dpi/fonts.dir -rw-r--r-- 1 root root 89234 Feb 3 20:41 /usr/share/fonts/75dpi/fonts.list -rw-r--r-- 1 root root 2 Mar 4 21:50 /usr/share/fonts/75dpi/fonts.scale donnie@supernova ~ $ ls /usr/share/fonts/corefonts/fonts.* -l -rw-r--r-- 1 root root 26447 Mar 4 21:51 /usr/share/fonts/corefonts/fonts.cache-1 -rw-r--r-- 1 root root 59376 Mar 4 21:51 /usr/share/fonts/corefonts/fonts.dir -rw-r--r-- 1 root root 1163 Feb 3 20:49 /usr/share/fonts/corefonts/fonts.list -rw-r--r-- 1 root root 59376 Mar 4 21:51 /usr/share/fonts/corefonts/fonts.scale
Hmm. When I booted up my laptop this morning I no longer get re-caching behavior. I also no longer get it when I do a restart on the /etc/init.d/xfs script. Nothing has changed since I wrote the previous comment, other than that I turned my computer off last night and restarted it this morning... Perhaps your patch did fix things, but for some reason the behavior didn't appear until a reboot? I'm not sure why this would be... Anyways, as I can't currently replicate the problem, feel free to close this bug report if you want. I can re-open it if problems start up again. For the record: jeff@scales jeff $ ls /usr/share/fonts/75dpi/fonts.* -l -r--r--r-- 1 root root 3066 Mar 20 18:00 /usr/share/fonts/75dpi/fonts.alias -rw-r--r-- 1 root root 218960 Mar 31 22:06 /usr/share/fonts/75dpi/fonts.cache-1 -rw-r--r-- 1 root root 165343 Mar 31 22:06 /usr/share/fonts/75dpi/fonts.dir -rw-r--r-- 1 root root 89234 Mar 31 22:06 /usr/share/fonts/75dpi/fonts.list -rw-r--r-- 1 root root 2 Mar 28 17:00 /usr/share/fonts/75dpi/fonts.scale jeff@scales jeff $ ls /usr/share/fonts/corefonts/fonts.* -l -rw-r--r-- 1 root root 26447 Mar 31 22:06 /usr/share/fonts/corefonts/fonts.cache-1 -rw-r--r-- 1 root root 42426 Mar 31 22:06 /usr/share/fonts/corefonts/fonts.dir -rw-r--r-- 1 root root 1198 Mar 31 22:06 /usr/share/fonts/corefonts/fonts.list -rw-r--r-- 1 root root 42426 Mar 31 22:06 /usr/share/fonts/corefonts/fonts.scale
Sometimes when binaries are in use they don't get replaced until you reboot, so this may have been the case. I'll close it for now per your request.
Just to add a quick comment-- I didn't actually replace the binaries...the only things that were done between when it didn't work and when it did were to add the patch to the init script and to remove two font directories from the XFS config file. So doing a restart on the init script should have worked, I would have thought, unless some part of it never fully shut down. Just wanted to make that clear in case it warrants further exploration... :-) Thanks for all your help.
