Bug#234119: Setting LANG=no_NO.UTF-8 cause many programs to kill the X server
Package: locales
Version: 2.3.2.ds1-11
I use debian testing, dist-upgraded last week.
I've been using the no_NO (Norwegian) locale for a long time.
I want to switch to using utf-8, so I tried using the no_NO.UTF-8 locale.
I have of course generated this with locale-gen. This is the _only_
choice of norwegian locales when running localeconf, someone who
use localeconf and don't know about /etc/enironment could get
a lot of trouble:
Some programs, such as mlterm, works fine with this locale.
But many kills the xserver when I start them, that isn't exactly fun
and makes the UTF-8 locale unuseable.
gimp and powershell are among the programs that cause this. I straced
gimp, and it seemed to be surprised that the X server disappeared. The
trace ended with
ERROR **: X connection to :1.0 broken (explicit kill or server shutdown).
So gimp didn't crash, but tricked X somehow.
Seems like it doesn't matter what locale the X server runs under.
I can run X with no_NO.UTF-8 and set LANG=no_NO in an xterm,
gimp and others will then run fine. Running gimp (or others)
with LANG=no_NO.UTF-8 cause that X crash though.
I am not sure that this is the correct package for which to report the bug,
but the locale is a common problem here.
Many different (but not all) programs cause the X crash with this locale.
And it happens with at least three different kinds of xservers: The matrox xserver,
the framebuffer xserver, and the radeon xserver.
I am using the experimental xserver-xfree86-dri-trunk in order to get
useable opengl support for tuxracer. I use linux kernel 2.6.2.
Helge Hafting
Reply to: