Gdk-WARNING **: Missing charsets in FontSet creation




16 years ago
13 years ago


(Reporter: saugart, Assigned: smontagu)



Firefox Tracking Flags

(Not tracked)



(1 attachment)



16 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130

I just upgraded from Mozilla 1.2-beta to mozilla-1.2.1.
Now, I get six repetitions of the following warning message every time the X
focus goes into the Mozilla window:

Gdk-WARNING **: Missing charsets in FontSet creation

Gdk-WARNING **:     ISO8859-1

Gdk-WARNING **:     ISO8859-1

When I start Mozilla and get the "User Profile Manager" box, I get eight
repetitions of the message.

Reproducible: Always

Steps to Reproduce:
Start up mozilla
Actual Results:  
see above

Expected Results:  
I assume  a warning means there's something worth warning about.  I would like
Mozilla to be happy with the setup and I'd like to fix any problem that this may

I would be glad to provide any additional data that may help.
I will attach the output of the "xlsfonts" command.

Comment 1

16 years ago
Created attachment 110903 [details]
output of the "xlsfonts" command.


16 years ago
Keywords: 4xp, fonts, verifyme

Comment 2

16 years ago
==> Intl
Assignee: asa → smontagu
Component: Browser-General → Internationalization
Keywords: 4xp, fonts, verifyme
QA Contact: asa → ylong

Comment 3

16 years ago
The warnings are coming from Gdk, not Mozilla. I tried searching Google and found among others. You might also try
asking on the netscape.public.mozilla.unix newsgroup.

Comment 4

14 years ago
Hi Steven

I don't see this problem with a recent build of Mozilla - Mozilla/5.0 (X11; U;
Linux i686; en-US; rv:1.8b) Gecko/20050302

Are you able to confirm whether or not you can still reproduce this with a
recent version of Mozilla?

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.