On 10/2/06, Anton Zinoviev <[EMAIL PROTECTED]> wrote:
On Mon, Oct 02, 2006 at 10:37:46PM +0200, Thue Janus Kristensen wrote:
> >
> >and then send to me the contents of the files /tmp/locale.out and
> >/etc/default/console-setup?
>
> These are attached.
Acording to locale.out your active locale is en_US.UTF-8. The next
thing we must ensure is that this locale is generated in your system.
Open the file /etc/locale.gen and make sure there are lines for all
locales you may want to use. For example
en_US.UTF-8 UTF-8
en_US ISO-8859-1
en_DK.UTF-8 UTF-8
en_DK ISO-8859-1
da_DK.UTF-8 UTF-8
da_DK ISO-8859-1
Then run as root the command "locale-gen".
I does look right, and includes en_US.UTF-8. I have just rerun
locale.gen, and the bug still occurs.
Anyway, since the console does display the right characters once I
have run setupcon then it indicates that the locale does exist.
> I get the same wrong characters whether I type them or cat them from
> /tmp/danishtest
This means the keyboard setup is OK.
> To be precise, the characters actually written to screen are
> http://en.wikipedia.org/wiki/%CE%9C (lowercase)
> http://en.wikipedia.org/wiki/%C2%B0
> http://en.wikipedia.org/wiki/Sigma (lowercase)
This happens when the kernel thinks the font has ISO-8859-1 encoding
but instead it is with CP437. I don't know what might cause this
because the font in your setup of console-setup has 512 symbols and
because of that it is clearly not ISO-8859-1 nor CP437.
Do you have installed some other package that tries to set the console?
kbd does have the init-script /etc/init.d/console-screen.kbd.sh ,
which is run on start. But kbd is recommended by console-setup, and
required by console-common, and so should not conflict with
console-setup?
In order to find out when the font brokes or whether it is loaded
properly at all you may want to use dpkg-reconfigure in order to
change the font to some that is easily distinguished from the boot
font. For example Fixed with size 13 (you will need to change the
codeset from Uni1 to Lat15). Then try to see during the boot proces
whether the font of console-setup loades (the corresponding message
should be "Setting up console font and keymap"). Then try to see if
this font remains unchanged until X starts. Return to the console
immediately and see if the font is already broken. If not, perhaps
the font brokes when you log in? In this case the problem is caused
by some of your startup scripts (~/.profile, ~/.bash_profile,
~/.bashrc, etc.).
The font does load during boot.
I have a very innocent .zshrc and /etc/zsh/, nothing which should
cause these kinds of problems. Besides, the problems already exist on
the login promt, before any shell startup scripts are run.
> I tried the tests in a console, after X started and I switched to the
> console. Please say if I should try them inside a boot which does not
> start X.
Perhaps not. I am almost sure the problem will remain with a boot
which does not start X, but who knows...
Anton Zinoviev
As I can see the font is correct until X starts I assume this is the case.
Regards, Thue
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
