477487 - Intermittently incorrect font smoothing profile

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[aremo]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009020406 Red Hat/3.0.6-1.el5 Firefox/3.0.6
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009020406 Red Hat/3.0.6-1.el5 Firefox/3.0.6

Firefox will sometimes start up with an incorrect (i.e.: very thin and light) font smoothing profile, whereas stronger smoothing or no smoothing are chosen in GNOME's "Font" preference panel.

Reproducible: Sometimes

Steps to Reproduce:
1. Quit Firefox
2. Launch Firefox

Actual Results:  
The font smoothing is sometimes incorrect. When it *is* incorrect, it's always a thin and light smoothing, whereas stronger smoothing or no smoothing are chosen in GNOME's "Fonts" preference panel.

Expected Results:  
Same font smoothing as the other apps.

At this point:

1. quitting Firefox
2. launching GNOME's "Fonts" preference panel and closing it (no need to tweak)
3. restarting Firefox

Cures the problem (for this launch).

Comment 1

[aremo]

Correction: you *do* need to tweak after opening GNOME's "Fonts" preference panel -- choose another smoothing style then switch back to the desired one. This cures the problem for the next Firefox launch.

Comment 2

[Tyler Downer [He/Him]]

This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.

Comment 3

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.