Hi, I also suffered from this problem on Debian squeeze: "Warning: Cannot convert string "-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct Warning: Missing charsets in String to FontSet conversion Warning: Cannot convert string "-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*, -*-*-*-*-*-*-*-120-*-iso10646-1, -*-*-*-*-*-*-*-120-*-jisx0208.1983-0, -*-*-*-*-*-*-*-120-*-jisx0201.1976-0" to type FontSet Warning: Missing charsets in String to FontSet conversion Warning: Unable to load any usable fontset Warning: Missing charsets in String to FontSet conversion Warning: Unable to load any usable fontset
Fatal error (11)." I found a workaround, but this workaround may not work for others though as the system setup I use is a bit special: I use NX (http://www.nomachine.com, it's a remote control software) to connect to the PC on which I use Debian/xemacs. NX adds its own fonts to the font path. Anyway, the workarounds I found are: - "export LANG=C;xemacs" by default I use de_DE.UTF-8 LANG - "xset fp default; xemacs" when I check with "xset q" the font path before and after the difference is that the entry /usr/NX/share/fonts/TTF/ right at the beginning of the font path gets removed. The fonts.dir file in that directory looks like this: luximr.ttf -b&h-Luxi Mono-medium-r-normal--0-0-0-0-m-0-iso8859-1 [...] luximb.ttf -b&h-Luxi Mono-bold-r-normal--0-0-0-0-m-0-iso8859-1 [...] [and so on] This directory includes a few fonts of the luxi fonts family, so it looks like those fonts are causing this problem. xemacs21-nomule works fine without any workaround. Frank -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
