When starting in normal mode, '#' works as delete and '@' works as delete line on console, while AltGr doesn't work at all on X. On the other hand, there is no problem when starting in single mode Reproducible: Always Steps to Reproduce: 1. Try to write '#' character 2. 3. Actual Results: Seems like have pushed delete key Expected Results: Print '#', leaving rest of the line intact "loadkeys -q windowkeys es" doesn't give any message nor fixes anything I've just finished moving system from one partition to another, and I've not had any other problem apart from this. Several minutes ago, I booted the system and found I had forgotten update LILO, so I booted with "root=/dev/hda2" option correctly (I had been booting from the old hda5 partition until then, and boot partitions have identical data, since one is a copy from the other), and found keyboard was working perfectly. Then I executed lilo and rebooted. Keymap started failing again.
please paste both: the version of xfree, as well as emerge info
Additional Info: --- XFree --- $ XFree86 -version XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.18-bf2.4 i686 [ELF] Module Loader present --- Emerge --- $ emerge info Portage 2.0.47-r8 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r2) ================================================================= System uname: 2.4.20-gentoo-r1 i686 Celeron (Covington) GENTOO_MIRRORS="http://gentoo.oregonstate.edu/ http://distro.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb:/usr/kde/3.1/share/config:/usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="" USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg kde gnome libg++ libwww mikmod mmx mpeg ncurses nls pdflib png quicktime spell xml2 xmms xv zlib gdbm berkdb slang readline svga tcltk java guile X sdl gpm tcpd pam ssl perl python esd imlib oggvorbis gtk qt motif opengl gphoto2 ldap pda arts samba truetype" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=pentium2 -O3 -pipe" CXXFLAGS="-march=pentium2 -O3 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
I have noticed that '#' and '@' only fail in one special case when using the in console: 1. Boot 2. Switch to tty1 (I start with kdm) 3. Push '#' instead of login (can be combined with other characters, of course). It won't work 4. login As a result, '#' won't work, but '@' will do 5. logoff 6. At the login prompt, write anything containing a '@'. It won't work 7. login As a result, '@' won't work, but '#' will do! If you combine '#' and '@' pulsations at the login prompt, them both will fail at command prompt after login. They won't work again until you logoff and relogin without touching these keys. (This "bad keymap state" will remain even if you have login failures. You must login and logoff in order to repair it again)
What version of pam-login? Try to update to the unstable version ?
Pablo? tried the unstable PAM version yet?
pablo, please reopen this bug when you have some feedback,
no more info
