After waiting 4-5 minutes for fonts-config to update the fontconfig cache files, it then started doing the same thing for 32bit cache files? Um... Aren't fonts architecturally neutral? Why two separate caches? Also, the 64-bit cache seemed to go w/o probs, but the 32bit files: Creating fonts.{scale,dir} files ............ /usr/share/fonts-config/conf.avail/12-suse-hinting-bc.conf unchanged /usr/share/fonts-config/conf.avail/17-suse-bitmaps.conf unchanged Creating cache files for fontconfig ................................................................... Creating 32bit cache files for fontconfig ./usr/share/fonts/100dpi: error scanning /usr/share/fonts/75dpi: error scanning ./usr/share/fonts/OTF: error scanning ./usr/share/fonts/TTF: error scanning /usr/share/fonts/Type1: error scanning /usr/share/fonts/Windows: error scanning .........../usr/share/fonts/misc/sgi: error scanning ...../usr/share/fonts/truetype: error scanning ................/usr/share/fonts/Type1: error scanning ....../usr/share/fonts/OTF: error scanning ./usr/share/fonts/TTF: error scanning ........... So on top of my puzzle about doing 2 separate caches for 32 and 64 bits, looks like the 32bit ver doesn't do the same thing the 64bit version does...(???) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org