User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a6pre) Gecko/20070620 Mnenhy/0.7.5.0 SeaMonkey/2.0a1pre Build Identifier: X11; U; Linux i686; en-US; rv:1.9a6pre) Gecko/2007062013 Mnenhy/0.7.5.0 SeaMonkey/2.0a1pre When defining an aliased font as your standard KDE font, SM falls back to use a serif font. "Sans Serif" e.g. on SuSE Linux is not really an installed font (You can't see it using kcontrol ->System settings -> Fonts (even if you checked the button to see bitmap fonts there). It just refers to another, really installed, font (maybe "Adobe Helvetica" here, but I'm not sure.). On openSuSE 10.2 "Sans Serif" is the standard font for KDE. Reproducible: Always Steps to Reproduce: 1. Define "Sans Serif" as standard font for KDE 2. Start SeaMonkey Actual Results: See that a serif font is used for the UI. Expected Results: A Sans Serif font should be used as fall back as the "Sans Serif" font does not exist. As SeaMonkey maybe cannot find out where "Sans Serif" refers to it should at least be able to recognize a font with something like 'sans' in its name. I also reported some symptoms at bug 382570. But it seems that the problems there are Windows related.

Does it look like bug 379886?

(In reply to comment #1) > Does it look like bug 379886? No. That bug is about wrong fonts in content (e.g. on websites). The prefpanel toggles font.name.* prefs. This bug here is talking about wrong fonts for the chrome GUI.