I recently upgraded world. I'm having some problem with X where it will send weird keys and wreck havoc with my gui applications and terminals, especially with vim. It does a lot of weird things, some of them worse than others, so I'll just list the things I noticed: 1. The delay before the key repeat is noticably slower than it used to be. 2. The page up key puts out an 'o' along with page up, which wrecks havoc with vim. 3. The page down key puts out a tilde arong with page down, which changes the case of things in vim. 4. Right control sees to put out a page down along with control. 5. ctrl+alt+backspace no longer works 6. It seems that one of my keys prints out the contents of my terminal to the *physical* printer located upstairs, and I think it's using lpr because it spit out a whole bunch of lpr errors. I don't want to figure out which key it is because it already printed out an entire $30 ream of card stock. 7. I no longer know what the lpr error said, because the following error is flooding my terminal, and continues to be generated with every keystroke in Chromium: [16680:16680:2793711118890:ERROR:base/file_util_posix.cc(724)] Couldn't fstat 23, errno 9 8. My script to disable caps lock no longer works. It is as follows: xmodmap -e "remove Lock = Caps_Lock" xmodmap -e "clear Mod3" xmodmap -e "add Mod3 = Caps_Lock" 9. Pressing page down in any gui application opens a context menu. 10. My mouse is noticeably faster, which is slightly annoying. I tried it with both urxvt and xterm, in and out of screen, but I still have the same problems. No problems with the keyboard outside of X. Tried another keyboard, same problems. I use dvorak as a keymap. There's some weird keymap stuff in /var/log/Xorg.0.log. I'll attach it. Any ideas? Reproducible: Always Steps to Reproduce:
Created attachment 239207 [details] /var/log/Xorg.0.log
Your xorg.conf must be full of hacks - the biggest being 'Option "AllowEmptyInput" "off"' (that one was never meant to be used the way people used it). Reading upgrade guides helps, understanding them helps even more. Personally, I'd go straight to xorg-server 1.8, as explaining hal configuration takes awhile and in 1.8 it's no longer used, in favor of udev backend. Not only is your keyboard registered twice, but it's set up using conflicting settings - have a look at old forum threads about it.
(In reply to comment #2) > Your xorg.conf must be full of hacks - > the biggest being 'Option "AllowEmptyInput" "off"' > (that one was never meant to be used the way people used it). > Reading upgrade guides helps, understanding them helps even more. I'll admit, I have the 'Option "AllowEmptyInput" "off"' set in my xorg.conf. I set it once upon a time because x11vnc wouldn't handle keyboard input properly without it. Honestly, I don't know what the option does exactly. I tried turning it off, but then it ignored my dvorak keymap setting entirely! > Personally, I'd go straight to xorg-server 1.8, as explaining > hal configuration takes awhile and in 1.8 it's no longer used, > in favor of udev backend. I tried upgrading to 1.8, and then I found my solution on the arch linux wiki: Section "InputClass" Identifier "Keyboard Defaults" MatchIsKeyboard "yes" Option "XkbLayout" "dvorak" EndSection This InputClass config only seems to work with 1.8 or greater, as I tried it on 1.7 and it didn't work. Oh, and I found the printer thing was caused by a print screen key being sent to urxvt whenever I pressed the up key. The following line in ~/.Xdefaults disables the feature(thanks to someone on the arch linux forums): URxvt.print-pipe: echo "echoing print"
