[locale] non-UTF8 fallen out of NLS data files (hoary regr.)

[Lucas Nussbaum]

On an up to date Breezy system, after setting locale to a non-UTF-8 one (example
: fr_FR) in GDM, I get messages like :

***nussbaum@alabama:~$ gvim

(gvim:13894): Gdk-WARNING **: locale not supported by Xlib

(gvim:13894): Gdk-WARNING **: cannot set locale modifiers

or :

***nussbaum@alabama:~$ xterm
Warning: locale not supported by Xlib, locale set to C

Accents chars work in some programs (xterm, gnome-terminal) but not in others
(aterm for example).

[Mathieu Bérard (mathieu-berard)]

I have encountered the very same problem.

In /usr/share/X11/locale/ compose.dir, locale.alias and local.dir
support for the fr_FR@euro locale (for example) is missing.

picking those three files from xlibs-data 6.8.2-10 (from hoary)
workaround this bug for me.

[Fabio Marzocca (thesaltydog)]

The same is for me. My locale is it_IT and every localized program I start from
terminal, I get these messages:
Gdk-WARNING **: locale not supported by Xlib at /usr/lib/perl5/Gtk2.pm line 59.
Gdk-WARNING **: cannot set locale modifiers at /usr/lib/perl5/Gtk2.pm line 59.

[Fabio Marzocca (thesaltydog)]

I have then fixed this by setting it_IT.UTF-8 as the default locale, and
re-booting the system.

[Colin Watson (cjwatson)]

*** Bug 21888 has been marked as a duplicate of this bug. ***

[Matt Zimmerman (mdz)]

Raising severity (regression from Hoary)

[Matt Zimmerman (mdz)]

*** Bug 22729 has been marked as a duplicate of this bug. ***

[Daniel Stone (daniels)]

*** Bug 22794 has been marked as a duplicate of this bug. ***

[Daniel Stone (daniels)]

fixed in breezy

[Chris Moore (dooglus)]

It's not fixed for me. Is the update somewhere waiting to be uploaded? If so,
shouldn't the bug be 'pending upload' rather than 'fixed'?

[Daniel Stone (daniels)]

libx11-6 1:6.2.1+cvs.20050722-8 fixes the problem

[Chris Moore (dooglus)]

I see it now. It seems that the bug was marked FIXED at 6:29 UTC (7:29 bugzilla
time) but the fix is timestamped 8:20 UTC, almost 2 hours later.

Doesn't FIXED mean that I should be able to see the fix in the repository? Or
should I always allow a couple of hours before testing fixed bugs?

[Daniel Stone (daniels)]

worst case, it can be two or three hours before you have binary packages off the
main mirror. also, I stuffed up the first upload, so it got rejected, which
meant another couple of hours of delay. in any case, patience is a virtue.
it's never going to work the second it's marked fixed, and there's not much any
of us can do about that.