Bug#699392: xscreensaver requires xfonts-100dpi or xfonts-75dpi

[Matthew Gabeler-Lee]

On Tue, 30 Apr 2019, Jamie Zawinski wrote:

Ok, I'm not really sure what's going on here.

This makes me feel better ;)

Possibly the problem is that your font cache needs to be regenerated with 
fc-cache?

$ grep -r helvetica /usr/share/fonts/X11
/usr/share/fonts/X11/misc/fonts.alias:variable     
-*-helvetica-bold-r-normal-*-*-120-*-*-*-*-iso8859-1 

(and no other matches)

This didn't make sense with my first round at the diagnostics you asked for
below, so I tried restarting the X session after removing the xfonts-100dpi
and doing things over again.

Tried that, didn't impact things. There's definitely a sign something is wonky in that area, however, given:

What do you get with:

xlsfonts -fn '-*-helvetica-bold-r-*-*-*-180-*-*-*-*-iso8859-1'

Before the X restart, I got 3 answers for '-adobe-helvetica-...'.  After the
restart, I get:

xlsfonts: pattern "-*-helvetica-bold-r-*-*-*-180-*-*-*-*-iso8859-1" unmatched

xlsfonts -fn '-adobe-helvetica-bold-r-normal--0-0-100-100-p-0-iso8859-1'

Before the restart, I got one answer.  After I get:

xlsfonts: pattern "-adobe-helvetica-bold-r-normal--0-0-100-100-p-0-iso8859-1" 
unmatched

Does text show if you do:

xterm -fn '-*-helvetica-bold-r-*-*-*-180-*-*-*-*-iso8859-1'

xterm: cannot load font "-*-helvetica-bold-r-*-*-*-180-*-*-*-*-iso8859-1"

This one didn't change before/after restarting X.













-arabic-newspaper-medium-r-normal--19-140-100-100-p-0-iso10646-1
-mutt-clearlyu alternate glyphs-medium-r-normal--19-140-100-100-p-0-iso10646-1
-mutt-clearlyu arabic-medium-r-normal--19-140-100-100-p-0-iso10646-1
-mutt-clearlyu pua-medium-r-normal--19-140-100-100-p-0-iso10646-1
-mutt-clearlyu-medium-r-normal--19-140-100-100-p-0-iso10646-1



</essay>, hope this helps!

--
        -- Matt
"Reality is that which, when you stop believing in it, doesn't go away".
                -- Philip K. Dick
GPG fingerprint: 0061 15DF D282 D4A9 57CE  77C5 16AF 1460 4A3C C4E9

I get text, looks like the standard "fixed" font ... but presumably that's related to this error: I've re-collected the debug output from the prior round of this from the clean restart of the X server in the hopes that might help provide less confusing diagnostics. Notably now helvetica doesn't appear at all in the output of xlsfonts. The two variants of medium listed as "substituted ..." in the xscreensaver debug output produce "interesting" results in xterm: -*-*-medium-r-*-*-*-180-*-*-p-*-iso10646-1 => giant xterm with huge square characters (as judged by the size of the cursor block), but all the characters are blank -*-*-medium-r-*-*-*-140-*-*-p-*-iso10646-1 => same idea, just slightly less huge. Huge here being approximately 3x the height & 4x the width of the characters in xterm's default font. xlsfonts on each of these patterns produces this output (substituting the 140 point size as appropriate for that case): I can't select the first one in xfontsel for whatever reason, which seems odd. In fact, if I get xfontsel to -*-*-medium-r-*-*-*-*-*-*-p-*-iso10646-1, there are _no_ fonts at ptSz 180 or 140. If I select one of the ptSz values that exists for the "arabic" one, I don't get any text. Same happens with "mutt-clearlyu alternate glyphs", and mostly so with "... arabic" (there's a couple funky characaters rendered, but nothing in the latin alphanumerics). "mutt-clearlyu pua" renders mostly as tofu (as opposed to totally blank space). "mutt-clearlyu" renders as an ugly but legible font with the expected characters all there.

fonts.2.txt.gz
Description: fonts.2.txt.gz

xscreensaver.debug.2.log.gz
Description: xscreensaver.debug.2.log.gz