190083 - Mozilla on Linux cannot find any fonts

Status: RESOLVED FIXED

(Core :: Layout: Text and Fonts, defect)

Description

[tenthumbs]

With a CVS build from this morning, mozilla can't find any fonts for the Western
encoding. ????? It had no problems yesterday. This is a stock XFree86 4.2.0 with
no extra fonts.

Setting severity to major.

Comment 1

[tenthumbs]

Attachment: prefs panel showing mozilla can't find fonts

OF course mozilla actually does find a default serif font that's way too small.
Setting NS_FONT_DEBUG=FFF seems to show that mozilla is actually finding fonts.

Comment 2

[Christian :Biesinger (don't email me, ping me on IRC)]

I see that too. In Addition, all fonts displayed in the browser appear way too
small.

Comment 3

[Christian :Biesinger (don't email me, ping me on IRC)]

this is a recent regression

Comment 4

[tenthumbs]

Yesterday's morning build worked so this is quite new.

FWIW, mozilla actually does find fonts. I prefer sans-serif and at least 
part of mozilla has no trouble finding fonts. 

FindFont(a/0x0061), nsFontMetricsGTK.cpp 6212
    FindStyleSheetSpecificFont, nsFontMetricsGTK.cpp 5758
        familyName = adobe-helvetica-iso8859-1, nsFontMetricsGTK.cpp 
5771
        TryNode aName = adobe-helvetica-iso8859-1, nsFontMetricsGTK.cpp 
5618
        load font adobe-helvetica-iso8859-1, nsFontMetricsGTK.cpp 4807
bitmap font:_______ adobe-helvetica-iso8859-1
                    desired=12, scaled=12, bitmap=12, 
nsFontMetricsGTK.cpp 3313
FindFont(0061)[adobe-helvetica-iso8859-1, helvetica, ]
returns -adobe-helvetica-medium-r-normal--12-120-75-75-p-*-iso8859-1

but it's never used.

Comment 5

[Peter Janes]

It's very recent.  Linux build 2003012208 has it, I think 2003012205 did, and
2003012122 didn't.  The comments above indicate fonts are too small; in my case,
the default font is far too large (about twice my regular setting of 11px).

Comment 6

[Per Ångström]

Not only CVS builds affected - changing Summary.

Comment 7

[R.K.Aa.]

why is this filed as a layout bug? Seems to me the component should be preferences.

I backed out the recent checkins for these bugs without any effect though:
bug 169489, bug 115539, bug 97622, bug 189740

Comment 8

[R.K.Aa.]

related to bug 190118? ("Charset menu items missing descriptive language name")

Comment 9

[tenthumbs]

Note that I do not see this on the chrome, only the document.

Comment 10

[tenthumbs]

From the last good build I had it appears that whatever changed happened between
Jan. 21, 0700 PST and Jan. 22, 0500.

Comment 11

[R.K.Aa.]

Windows users see bug 190155

Comment 12

[Peter Henderson]

What I'm seeing with build 2003012208 on RH7.3 is that the fonts are all the
correct fonts, but they are too small. (Perhaps the minimum point size is being
ignored.) As the screenshot shows, the prefs UI doesn't display any fonts, but
the fonts still seem to be found and displayed properly in the browser. The page
fonts are too small, but chrome fonts appear fine.

Comment 13

[Boris Zbarsky [:bzbarsky]]

to ftang, since smontagu is not around.

Comment 14

[Peter Janes]

Seems to have gone away in build 2003012308.  Perhaps due to the properties
parsing bug, which I can't find right now but apparently caused a lot of other
problems?

Comment 15

[R.K.Aa.]

It didn't "go away" - it was fixed :) See dependency bug.
Resolving as fixed, since that patch fixed it here too.