Bug#254027: installation-reports TC1 on Acer TravelMate 800

[Christian Perrier <bubulle@debian.org>]

clone 254027 -1
reassign -1 base-config
retitle -1 High-ASCII characters do not display properly after 2nd reboot with kernel 2.6
reassign 254027 prebaseconfig
retitle 254027 Seems to unmount ext2/ext3 uncleanly, forcing a fs check after reboot
thanks

> 1) if you select fr_FR during installation but it's probably the same with 
> some others langages with special characters (US is ok)
> if you pressed a key like 'é' (french character) when you enter the IP 
> then you get stuck with a frozen field and have to reboot. (some filter is 
> needed here)

This is #251550. Currently assigned to cdebconf, but according to
Eugeniy Meshcheryakov it should be assgined to whiptail.

Eugeniy, are you completely sure ? If so, we must assign this
important bug to whiptail

> 2) if you select 2.6 kernel and fr_FR during installation but it's probably 
> the same with some others langages (US is ok and 2.4 is ok)
> This one is quite serious for common user. 2.6 only (2.4 is OK) but nothing 
> to do with UNICODE. It's another problem.
> Just after the first reboot after the installation keys like 'é' are 
> displayed correctly but if you boot again 'é' are displayed 'õ'
> Same problem for all "special" characters. Seems that a script is played at 
> the first reboot but not for the others reboot.
> But it must be something more ##!## because only kernel 2.6 is affected by 
> this.

I'm currently trying to confirm that one. I suspect this is related to
be the console font problem in #253211 (huge bug log...)


> 
> 3) during the first reboot after installation a check forced is done for 
> not cleanly unmounted partition and you have to reboot after the check.
> ok after the check so not to serious (problem only with etx2, reiserfs is 
> ok)
> 
> These problems are easy to reproduce at least on beta 4 and on snapshot 
> 20040610.

ext3 is also checked (indeed a journal recovery happens)

The place file systems are unmounet is prebaseconfig, so assigning
this bug to it...

The unmount operation is "umount -a || true"