[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#254167: acknowledged by developer (Re: Bug#254027: installation-reports TC1 on Acer TravelMate 800)

Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
#254167: High-ASCII characters do not display properly after 2nd reboot with kernel 2.6,
which was filed against the base-config package.

It has been closed by one of the developers, namely
Christian Perrier <bubulle@debian.org>.

Their explanation is attached below.  If this explanation is
unsatisfactory and you have not received a better one in a separate
message then please contact the developer, by replying to this email.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Received: (at 254167-done) by bugs.debian.org; 14 Jun 2004 06:27:37 +0000
>From bubulle@kheops.frmug.org Sun Jun 13 23:27:37 2004
Return-path: <bubulle@kheops.frmug.org>
Received: from onera.onera.fr [144.204.65.4] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BZkwS-0002pY-00; Sun, 13 Jun 2004 23:27:37 -0700
Received: from cc-mykerinos.onera (localhost [127.0.0.1])
        by onera.onera.fr  with ESMTP id i5E6RYqC002373;
        Mon, 14 Jun 2004 08:27:34 +0200 (MEST)
Received: from localhost (mykerinos.kheops.frmug.org [127.0.0.1])
	by mykerinos.kheops.frmug.org (Postfix) with ESMTP id 88FA323290;
	Mon, 14 Jun 2004 07:01:33 +0200 (CEST)
Received: from mykerinos.kheops.frmug.org ([127.0.0.1])
	by localhost (mykerinos [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 03214-02; Mon, 14 Jun 2004 07:01:22 +0200 (CEST)
Received: by mykerinos.kheops.frmug.org (Postfix, from userid 7426)
	id 5F98823285; Mon, 14 Jun 2004 07:01:22 +0200 (CEST)
Date: Mon, 14 Jun 2004 07:01:22 +0200
From: Christian Perrier <bubulle@debian.org>
To: Christian Perrier <bubulle@debian.org>, 254167-done@bugs.debian.org
Cc: Olivier ROLAND <olivier.roland@laposte.net>
Subject: Re: Bug#254027: installation-reports TC1 on Acer TravelMate 800
Message-ID: <20040614050122.GB3072@mykerinos.kheops.frmug.org>
References: <[🔎] 40CB2212.5060107@laposte.net">[🔎] 40CB2212.5060107@laposte.net> <[🔎] 20040613121512.GC21782@mykerinos.kheops.frmug.org">[🔎] 20040613121512.GC21782@mykerinos.kheops.frmug.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
In-Reply-To: <[🔎] 20040613121512.GC21782@mykerinos.kheops.frmug.org">[🔎] 20040613121512.GC21782@mykerinos.kheops.frmug.org>
X-message-flag: Outlook is a good virus spreading tool. It can send mail, too.
X-pot_a_miel: honeypot@kheops.frmug.org
User-Agent: Mutt/1.5.6+20040523i
X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at mykerinos
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by onera.onera.fr id i5E6RYqC002373
Delivered-To: 254167-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

  
2) if you select 2.6 kernel and fr_FR during installation but it's pr=
      
obably=20
  
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 n=
      
othing=20
  
to do with UNICODE. It's another problem.
Just after the first reboot after the installation keys like '=E9' ar=
      
e=20
  
displayed correctly but if you boot again '=E9' are displayed '=F5'
Same problem for all "special" characters. Seems that a script is pla=
      
yed at=20
  
the first reboot but not for the others reboot.
But it must be something more ##!## because only kernel 2.6 is affect=
      
ed by=20
  
this.
      
=20
I'm currently trying to confirm that one. I suspect this is related to
be the console font problem in #253211 (huge bug log...)
    

This problem is not there on the latest sid_d-i build. With the 2.6
install, everything is OK on the french install=A0: I can type "=E9" at
the command line and they are properly outputted

Hence, closing this bug.
I'm sorry but I can reproduce this bug with the last daily built CD image (13-Jun-2004).
First boot is ok, second boot no. I have check all and confirm that bug on my system.
Any clue for deeper investigation ? Is there someone else to reproduce that bug ?


Reply to: