[Natty] Encoding issue on TTY

[Nicolas Delvaux]

Binary package hint: kbd

See the attached screenshot.
(it only happen in a TTY)

No problem on Maverick.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: kbd 1.15-1ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Mon Apr 4 21:00:43 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110311)
ProcEnviron:
 LANGUAGE=fr_FR:en
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: kbd
UpgradeStatus: Upgraded to natty on 2011-03-21 (14 days ago)

[Andrey Bondarenko (abone)]

The bug might be related to console-setup package and bug 668812. I use ru_RU.UTF-8 locale and my fonts in framebuffer tty are also broken. Manually starting setupcon fixes the problem. Also, in natty console-setup init scripts were rewritten as upstart jobs and I cannot find setupcon calls in them.

[Andrey Bondarenko (abone)]

I've found that in Natty framebuffer console is fonts set up by initramfs.
Also in Natty initramfs-tools framebuffer becomes optional since version 0.98.8
and you have to add undocumented option FRAMEBUFFER=y to /etc/initramfs-tools/initramfs.conf
to enable this behaviour.

Can you add FRAMEBUFFER=y into your /etc/initramfs-tools/initramfs.conf then run:

update-initramfs -u

Then reboot and check if console font encoding is ok. This works for me, at least.

[Andrey Bondarenko (abone)]

Reported issue with initramfs as bug 789141. I hope to get an anwser from initramfs developers.

[Nicolas Delvaux (malizor)]

 I don't have this problem anymore (from a fresh install).

Maybe this happens only with some locals?

[Andrey Bondarenko (abone)]

Maybe, you are right. Anyway, I'm traced my problem to its root cause bug 789141 and yours issue have disappeared. I think we should close this but, because we cannot reproduce it anymore. If some one have similar problem, that looks like this bug, feel free to reopen the bug.

[Nicolas Delvaux (malizor)]

Closing as "Fix released", because it was a valid bug ;-)