Your message dated Sat, 14 Feb 2009 19:02:01 +0100
with message-id <[email protected]>
and subject line Closing unreproducible bug
has caused the Debian Bug report #492081,
regarding [Lenny] Keyboard mapping problem on login
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
492081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492081
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: console-data

Version: 2:1.07-4

Hello,

I have some problems on my Debian Lenny (kernel 2.6.25) when I want to log in 
from a console or from a X session.
- From console, here what's happening :

A first login attempt looks like :
--------------
Debian login: tom
password: *****

Login incorrect

Debian login: ^[t ^[o ^[m
password: ****
--------------

So, when i first try to log in, i can enter my nickname correctly, but the 
given password (which contains @) fails. At the next prompt, when i type "tom", 
something like "^[t ^[o ^[m appears and, noway to log in. Travelling on 
consoles make me succeed in finding one (or more) console(s) on which I can 
login. The problem is not attached to a specific console because a successfull 
login in console tty3 for instance can be followed later by an unsucessfull one 
for the same tty3.

- From Kdm, a first login attempt succeed, but, when I close my session and try 
to re-open it, the @ caractère are replaces by "à", meaning that the right Alt 
key doesn't act as expected. (right-Alt + 0) should gives @, (Shift + 0) gives 
"à". This happened every time, after closing the first session. To correct 
this, i need to restart the server X.

- My locales are set to "fr...@euro" and my keymap is "fr azerty latin9 (pc / 
azerty / French / Same as X11 (latin 9) / Standard)". I tried another keyboard 
whitout results. Xorg.conf used an "xorg pc105 fr latin9 keyboard". I first 
used the "lv3:ralt:switch" option but saw on the Net that it could cause 
problems. Desactivates it didn't solve the problem under kdm.

 
I don't know exactly which package is concerned (console-data, login, kdm, ...) 
and I didn't see anything in logs exept in kdm.log :
--------------
expected keysym, got circumflex: line 257 of fr
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
--------------
which appears to be a common error. 

I have not meet yet some problems when I log in remotely from ssh.

Thanks to help solving this problem.

Here are some other information :

# locale
lang=fr...@euro
LC_CTYPE="fr...@euro"
LC_NUMERIC="fr...@euro"
LC_TIME="fr...@euro"
LC_COLLATE="fr...@euro"
LC_MONETARY="fr...@euro"
LC_MESSAGES="fr...@euro"
LC_PAPER="fr...@euro"
LC_NAME="fr...@euro"
LC_ADDRESS="fr...@euro"
LC_TELEPHONE="fr...@euro"
LC_MEASUREMENT="fr...@euro"
LC_IDENTIFICATION="fr...@euro"
LC_ALL=

# dpkg-reconfigure console-data
Looking for keymap to install:
fr-latin9
assuming iso-8859-1 cedilla
assuming iso-8859-1 acute
assuming iso-8859-1 diaeresis
assuming iso-8859-1 brokenbar
assuming iso-8859-1 threequarters
assuming iso-8859-1 onehalf
assuming iso-8859-1 onequarter
assuming iso-8859-1 brokenbar

Regards,
------------------
moa :)
http://www.npdci.fr

________________________________
 Envoyé avec Yahoo! Mail.
Une boite mail plus intelligente. 


      
_____________________________________________________________________________ 
Envoyez avec Yahoo! Mail. Une boite mail plus intelligente http://mail.yahoo.fr

--- End Message ---
--- Begin Message ---
This bug has never been reproducible by anyone....and is even not
proven to be in console-data. Many later contributions in the bug log
just added confusion.

I see nothing possible except closing it.

Please reopen only with a simple reproducible test case...


-- 


Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to