View previous topic :: View next topic |
Author |
Message |
bratwurst n00b
Joined: 24 May 2005 Posts: 6 Location: Sweden
|
Posted: Mon Aug 08, 2011 7:35 pm Post subject: [Solved] Some keys won't work in terminal |
|
|
Hello *,
this time I got myself into a mess, that I can't seem to be able to clean up.
It probably started with a recent 'etc-update', when I probably did some changes I should not have done
As soon as I log in (using the console on a terminal, xterm or even a console during interactive startup) some keys stop working (examples are: 'e', 'i', 's', 'd' and some more).
When pressing 'e','i' and 's' nothing happens; pressing 'd' shows '$'.
Before I am logged in i.e. when I type the username *all* keys work.
So now I boot from a LiveCD and chroot into the installation - with the same effect. The only thing that I can do right now is call previously written scripts as argument to chroot.
It's not really convenient.
When I invoke showkey in my script the keys show proper responses. So I checked /etc/conf.d/keymaps :
Code: | # Use keymap to specify the default console keymap. There is a complete tree
# of keymaps in /usr/share/keymaps to choose from.
keymap="de-latin1"
windowkeys="YES"
extended_keymaps=""
dumpkeys_charset=""
fix_euro="NO" |
Looked okay to me. Same with /etc/rc.conf:
Code: | # Global OpenRC configuration settings
rc_parallel="NO"
rc_interactive="YES"
rc_shell=/sbin/sulogin
rc_depend_strict="YES"
# Set unicode to YES to turn on unicode support for keyboards and screens.
unicode="YES"
rc_tty_number=12
|
This is what env said:
Code: |
MANPATH=/usr/local/share/man:/usr/share/man:/usr/share/binutils-data/i686-pc-linux-gnu/2.18/man:/usr/share/gcc-data/i486-pc-linux-gnu/4.1.2/man:/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2/man:/usr/qt/3/doc/man
CONSOLE=/dev/console
TERM=linux
loop=/image.squashfs
looptype=squashfs
QTDIR=/usr/qt/3
PRELINK_PATH_MASK=/usr/lib/gstreamer-0.10
LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:su=37;41:sg=30;43:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.svgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.pdf=00;32:*.ps=00;32:*.txt=00;32:*.patch=00;32:*.diff=00;32:*.log=00;32:*.tex=00;32:*.doc=00;32:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:
INIT_VERSION=sysvinit-2.86
GDK_USE_XFT=1
GUILE_LOAD_PATH=/usr/share/guile/1.8
initrd=gentoo.igz
PAGER=/usr/bin/less
CONFIG_PROTECT_MASK=/etc/udev/rules.d /etc/fonts/fonts.conf /etc/gconf /etc/terminfo /etc/revdep-rebuild
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/i486-pc-linux-gnu/gcc-bin/4.1.2:/usr/i686-pc-linux-gnu/gcc-bin/4.1.2:/usr/qt/3/bin
vga=791
RUNLEVEL=3
PWD=/root
DISTCC_LOG=
EDITOR=/bin/nano
QMAKESPEC=linux-g++
PREVLEVEL=N
DCCC_PATH=/usr/lib/distcc/bin
DISTCC_VERBOSE=0
SHLVL=2
HOME=/
BOOT_IMAGE=gentoo
PYTHONPATH=/usr/lib/portage/pym
LESS=-R -M --shift 5
CVS_RSH=ssh
GCC_SPECS=
LESSOPEN=|lesspipe.sh %s
PKG_CONFIG_PATH=/usr/qt/3/lib/pkgconfig
CDBOOT=1
INFOPATH=/usr/share/info:/usr/share/binutils-data/i686-pc-linux-gnu/2.18/info:/usr/share/gcc-data/i486-pc-linux-gnu/4.1.2/info:/usr/share/gcc-data/i686-pc-linux-gnu/4.1.2/info
OPENGL_PROFILE=xorg-x11
LDPATH=/usr/local/lib:/usr/lib/opengl/xorg-x11/lib:/usr/i686-pc-linux-gnu/lib:/usr/lib/gcc/i486-pc-linux-gnu/4.1.2:/usr/lib/gcc/i686-pc-linux-gnu/4.1.2:/usr/lib/nspr:/usr/lib/nss:/usr/lib/qt4:/usr/qt/3/lib
_=/usr/bin/chroot
|
I would have expected the keymap there - but I'm not sure.
Here's my emerge info : http://pastebin.com/LQFM2efD
Any idea is appreciated.
Regards,
bratwurst
Last edited by bratwurst on Mon Aug 22, 2011 12:12 pm; edited 1 time in total |
|
Back to top |
|
|
tryn Guru
Joined: 21 Dec 2002 Posts: 325 Location: 39.885° N. -88.913° W.
|
Posted: Tue Aug 09, 2011 6:20 pm Post subject: |
|
|
You might try doing this.
Rebuild ( x11-base/xorg-server ) also run this command to see what drivers you need to rebuild ( qlist -I -C x11-drivers )
Then rebuild them after the xorg-server rebuild.
If I remember correctly I saw something about a person might need to do this after a recent e-build that I did. Which I didn't need to do but might be your problem. At least worth a try. |
|
Back to top |
|
|
bratwurst n00b
Joined: 24 May 2005 Posts: 6 Location: Sweden
|
Posted: Tue Aug 09, 2011 10:15 pm Post subject: |
|
|
Hi tryn,
thanks for your reply.
I saw posts like that as well and have already tried...without success |
|
Back to top |
|
|
bratwurst n00b
Joined: 24 May 2005 Posts: 6 Location: Sweden
|
Posted: Sun Aug 14, 2011 10:09 pm Post subject: |
|
|
....downgraded baselayout -> no success.....
still looking for a fix. Anyone? |
|
Back to top |
|
|
rndusr Guru
Joined: 04 Dec 2005 Posts: 392
|
Posted: Sun Aug 14, 2011 10:59 pm Post subject: |
|
|
You could back up your /etc, and unpack the /etc from the latest stage3 tarball onto it by Code: | tar -xvjf stage3*.tar.bz2 etc -C / |
This will get back sane configs which you can adjust.
If it does not work you can always go back to the backed up, broken version you now have. _________________ If you've got nothing nice to say, you're probably not alone... |
|
Back to top |
|
|
s_bernstein Apprentice
Joined: 11 Mar 2006 Posts: 172 Location: Bremen, Germany
|
Posted: Mon Aug 15, 2011 3:09 pm Post subject: |
|
|
So, before you trash your system alltogether, lets try to debug it:
- You are in Sweden but using a german keyboard layout. Is that correct?
- You said you can login. Do you use a graphical login, like gdm?
- What happen with the keyboard in another application, like an editor (p. ex. gedit)?
- What happen, if you login as another / a new user?
This will give you a better idea, where to look for the error.
There are different places to setup your keyboard:
- /etc/conf.d/keymaps is for your terminal (not the virtual terminals under X)
- In /etc/X11/xorg.conf[.d] you setup your keyboard for Xorg, which will be used by gdm
- If you use gnome or kde as a desktop manager, you have to setup your keyboard in the respective settings for gnome or kde
- Also look for an .xmodmap in your home directory, and if there is one, try to rename it
Good luck |
|
Back to top |
|
|
bratwurst n00b
Joined: 24 May 2005 Posts: 6 Location: Sweden
|
Posted: Tue Aug 16, 2011 10:08 pm Post subject: |
|
|
Thanks for your ideas.
@PanzerKanzler: I would want to try that if it turns out, that nothing else helps. I also have two other Gentoo installations that don't show the problem, so I would probably start from their /etc/
@s_bernstein:
Quote: | You are in Sweden but using a german keyboard layout. Is that correct? |
Yep.
Quote: | You said you can login. Do you use a graphical login, like gdm? |
It happens using the console as well as xterm using fluxbox.
It even happens when chrooting into my system from a LiveCD, which probably means it's not udev/hal/.... or any service
Quote: | What happen with the keyboard in another application, like an editor (p. ex. gedit)? |
I am not 100% sure. I am on the road at the moment and will try ASAP (2-3 days).
Quote: | What happen, if you login as another / a new user? |
Tried as root and my usual user. I will try to create a new user and login.
Quote: | /etc/conf.d/keymaps is for your terminal (not the virtual terminals under X) |
looks sane to me (see original post)
Quote: | In /etc/X11/xorg.conf[.d] you setup your keyboard for Xorg, which will be used by gdm |
Uses the correct layout for german keyboard.
I use the same config on other installations without problems.
Quote: | If you use gnome or kde as a desktop manager, you have to setup your keyboard in the respective settings for gnome or kde |
Since the problem also occurs using the console, I think this is noth the source of problems.
Quote: | Also look for an .xmodmap in your home directory, and if there is one, try to rename it |
I will try that ASAP. But isn't .xmodmap only used in X?
I broke my Gentoo installations many many times through the last years - but this problem just doesn't want to disappear....
Thanks again for your answers. |
|
Back to top |
|
|
rndusr Guru
Joined: 04 Dec 2005 Posts: 392
|
Posted: Tue Aug 16, 2011 11:04 pm Post subject: |
|
|
Before you forget to do it, make sure to backup your currently broken /etc. Things might get even worse, even though it is unlikely.
I would not use /etc from system B to rescue system A if:
system B has packages that system A does not have, or if
system A and system B use different architectures.
Otherwise, you can just go ahead.
Don't remove the broken /etc, but overwrite the files in it (this is the default behaviour of both tar and cp).
Since you cannot type the commands locally, I suggest you do it via ssh from another computer. Code: | ssh root@trasigdator.se [command] |
_________________ If you've got nothing nice to say, you're probably not alone... |
|
Back to top |
|
|
s_bernstein Apprentice
Joined: 11 Mar 2006 Posts: 172 Location: Bremen, Germany
|
Posted: Wed Aug 17, 2011 4:27 am Post subject: |
|
|
Yes, you are right. If it happens on console it has nothing to with your X setup or xmodmap.
Quote: |
Quote: | What happen, if you login as another / a new user? |
Tried as root and my usual user. I will try to create a new user and login.
|
I just had another idea. Try to use another shell for the user. Because your login is working, I think there is something broken in either your own bash profile in your home directory or in your global profile. Somethings get screwed up while loading your shell. Maybe your bash is broken, have you tried a stable version? Maybe compiling without ccache - shouldn't be a problem, but who knows.
Also, maybe you check /etc/inputrc and /home/<user>/.inputrc. But I think it is unlikely that this is causing your problem.
Last edited by s_bernstein on Mon Aug 22, 2011 12:49 pm; edited 1 time in total |
|
Back to top |
|
|
bratwurst n00b
Joined: 24 May 2005 Posts: 6 Location: Sweden
|
Posted: Mon Aug 22, 2011 12:10 pm Post subject: [Solved] Some keys won't work in terminal |
|
|
You helped me fix it!
Creating a new user did not make any difference.
But when I used another Shell (zsh) the problem did not occur.
The next thing I did was to diff the stage 3 /etc/bash/ files with mine. I found differences in /etc/bash/basrc, but using the file from stage 3 does not eliminate my problem.
I also checked /etc/skel/*, but there were no differences.
Then I tried to diff the complete etc directory, which turned out to be a lot, but I found that /etc/inputrc was messed up my current version contained garbage.
Once replaced everything works again.
So both your contributions were very valuable! Thank You! |
|
Back to top |
|
|
s_bernstein Apprentice
Joined: 11 Mar 2006 Posts: 172 Location: Bremen, Germany
|
Posted: Mon Aug 22, 2011 12:50 pm Post subject: |
|
|
Happy to help. |
|
Back to top |
|
|
rndusr Guru
Joined: 04 Dec 2005 Posts: 392
|
Posted: Mon Aug 22, 2011 4:44 pm Post subject: |
|
|
Det var så lite så
I imagined it would be too difficult to find the offending file, but apparently you were able to do it. _________________ If you've got nothing nice to say, you're probably not alone... |
|
Back to top |
|
|
|