Red Hat Bugzilla – Bug 64277
Problems with non ISO 8859-1 encoding
Last modified: 2008-05-01 11:38:02 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.0.0-9; Linux)
Description of problem:
When I try to open a GTK or QT app (up2date, kate - those are just examples) I
get the following errors:
Qt: Locales not supported on X server
(up2date:21735): Gdk-WARNING **: locale not supported by Xlib
(up2date:21735): Gdk-WARNING **: can not set locale modifiers
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start X (no matter if GNOME, KDE or Window Maker)
2. Try to run an application from the console
3. see the results
Actual Results: posted above
Expected Results: Should work ;)
One of the other things that happends and can be seen with gfontsel - is that
I see fonts names on the list (doesn't matter which encoding), but I cannot
preview them - some of them, and even when previewed, I get errors like:
Cannot open font: -monotype-arial-media-r-normal-*12-*-*-*-p-*-iso8859-8 (just
I'm not sure that it belongs to locale config or to XFree..
Probably an XFree bug, but there is some important information
missing here ... what locale are you trying to use? What
is the output of "echo $LANG"?
Also, how did you set the locale? In the installer? Through
locale-config? Through GDM?
For your first question:
hetz]$ echo $LANG
For the second question - I didn't try to change the localte - however I did
select Hebrew and English on the beta4 installer.
Is this an upgrade from an earlier beta? We had some problems
with /etc/sysconfig/i18n being generated incorrectly earlier
The immediate bug seems to be an X one
/usr/X11R6/lib/X11/locale/locale.alias has an alias
But locale.dir in the same directory doesn't have an entry
for en_US.ISO8859-15. (Like locale.alias, this seems to
have every entry duplicated twice, once without the comma,
once with the comma, and probably requires both to
If this is a beta4 install, the various locale encodings weren't all there for
beta4, but they should all be fine for the final release.
OK, updated to final RH 7.3 - bug seems to be gone. Please close this bug.