Keith Packard wrote:
That 'shouldn't' happen either -- the first application should place all of the relevant font informatio in ~/.fonts.cache-1 and application startup time should get back to normal immediately. If not, then there's still a bug in fontconfig.
thomas@a147097 ~ $ ls -l .fonts.cache-1 -rw-r--r-- 1 thomas thomas 55723 2004-10-01 03:03 .fonts.cache-1 that's quite old...
I did apt-get --reinstall install xfonts-base xfonts-75dpi xfonts-100dpi, and guess what, the problem started again. Then running fc-cache as root fixed it (again). I had to run it as root, did not work as user. So perhaps the scripts of those packages should check for the presence of fontconfig and update the cache?Looking through the scripts for the packages you have installed to locate one which touches font directories and which doesn't call fc-cache would probably identify it reasonably quickly.
But why does FC check bitmap fonts anyway? (I did not change any FC configuration) mfg Thomas