FS#4964 - fontconfig: no fonts found

Attached to Project: Arch Linux
Opened by paul (paul1) - Wednesday, 05 July 2006, 06:05 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Jan de Groot (JGC)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

New install, startx fails "no fonts found, this probably means that the fontconfig library is not properly configured. The fonts.conf is the default, and xorg-fonts-type1 is installed.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 09 August 2006, 20:39 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Wednesday, 05 July 2006, 06:18 GMT
What is the exact message, Xorg doesn't give these exact messages usually. Also, what font paths did you specify in /etc/X11/xorg.conf?
Comment by paul (paul1) - Wednesday, 05 July 2006, 15:44 GMT
exact message:
"No fonts found; this probably means that the font config library is not correctly configured. You may need to edit the fonts.conf configuration file. More information can be found in the fontconfig(3) manual page and on http://fontconfig.org."
"FreeFontPath : FPE "/usr/share/fonts/misc" refcount is 2, should be 1: fixing."
Comment by paul (paul1) - Wednesday, 05 July 2006, 16:09 GMT
This fixed it
[code] fc-cache -f -v [/code]

However: xterm / xfce terminal don't work
"xterm: Error 32, errno 2: No such file or directory"
"Reason: get_pty: not enough ptys"
"FreeFontPath: FPE "/usr/share/fonts/misc" refcount is 2, should be 1; fixing."

config_unix98_ptys=y
config_legacy_ptys=y
config_legacy_pty_count=256
Comment by paul (paul1) - Wednesday, 05 July 2006, 18:10 GMT
Fixed the pty problem (fstab wasn't correct), you can close this bug.
Comment by name withheld (Gullible Jones) - Wednesday, 26 July 2006, 02:22 GMT
Bug still exists. Didn't disappear until I reinstalled fontconfig, which seems to tie in with this:

http://bugs.archlinux.org/task/4712
Comment by Jan de Groot (JGC) - Thursday, 03 August 2006, 20:11 GMT
This is caused by fonts only generating fonts.cache-1 files for their own directory, while fontconfig searches in /usr/share/fonts/fonts.cache-1, which should be a cache file with listings of all directories below it. Since the fonts don't generate the file, the fonts.cache-1 file won't get created/updated until you either run fc-cache -f by hand, or reinstall fontconfig (fontconfig has it in post_install).

Modifying most fonts to solve this issue now.

Loading...