Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just reinstalled FC4 on my laptop, and obviously something is different this time.
For certain keys - double quote, single quote and tilde ( ¨ ´ ~ ) at least I have to double press the key to make it appear on screen. If I don double press it, it puts the keyboard into some mode for typing special characters.
I don even know where to begin to look to change this option. In KDE Control Center, under ¨Regional & Accessability¨ -> ¨Keyboard Layout¨ I have selected ¨Laptop/Notebook Dell Inspiron 8xxx¨ and activated the (us) keymap.
Let me know what other information I might need to post, or if I should try changing anything.
You could try running 'xev' in a terminal window to see what X is doing with the keystrokes. Put the focus in the xev window and type. Here is what I get for double-quote (along with the shift-key). Standard US keyboard.
KeyPress event, serial 28, synthetic NO, window 0x3200001,
root 0x3b, subw 0x0, time 88060397, (148,6), root150,32),
state 0x0, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES,
XLookupString gives 0 bytes: ""
KeyPress event, serial 28, synthetic NO, window 0x3200001,
root 0x3b, subw 0x0, time 88063646, (148,6), root150,32),
state 0x1, keycode 48 (keysym 0x22, quotedbl), same_screen YES,
XLookupString gives 1 bytes: """
You can change the mapping from keycodes to keysyms using 'xmodmap'. Check the man page. Strange problem tho'.
Here is xev output from holding shift, tapping the quote key, and releasing shift. I don't particularly understand what it all means, but I also found something else interesting.
If I go into control center and uncheck the "Enable keyboard layouts" box, special keys start to work fine, but then my media buttons do nothing (Mute, Play, Stop, etc...)
Anyway, here is the output. I think it is odd that three actions (hold, tap, release) actually generated four events... but again, I am clueless as to what this actually means.
Code:
KeyPress event, serial 31, synthetic NO, window 0x3400001,
root 0x46, subw 0x0, time 16853741, (173,-9), root:(850,12),
state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 31, synthetic NO, window 0x3400001,
root 0x46, subw 0x0, time 16855749, (173,-9), root:(850,12),
state 0x11, keycode 48 (keysym 0xfe57, dead_diaeresis), same_screen YES,
XLookupString gives 2 bytes: (c2 a8) "�"
XmbLookupString gives 0 bytes:
XFilterEvent returns: True
KeyRelease event, serial 31, synthetic NO, window 0x3400001,
root 0x46, subw 0x0, time 16855809, (173,-9), root:(850,12),
state 0x11, keycode 48 (keysym 0xfe57, dead_diaeresis), same_screen YES,
XLookupString gives 2 bytes: (c2 a8) "�"
KeyRelease event, serial 31, synthetic NO, window 0x3400001,
root 0x46, subw 0x0, time 16857133, (173,-9), root:(850,12),
state 0x11, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
XLookupString gives 0 bytes:
Do you have the same problem when logging in to the console, or is it exclusive to X? Does it matter which terminal program you use? Is "deadkeys" enabled?
X-windows inserts an extra mapping keycodes (physical keys) to keysyms (symbolic keys) which is easily modified. Executing the command
xmodmap -e 'keycode 48 = apostrophe quotedbl'
should make the quote/doublequote key work correctly.
You can see current settings using 'xmodmap -pke'. The whole set-up is quite complex. Have a look in /etc/X11/xkb for all the config files for different languages etc. You can use xev to find out the keycodes. Xmodmap can be run in a startup script.
Better if you find what went wrong in your keyboard configuration, but you can always do this as a last resort.
The keymapping issue was only in X, not on traditional terminal.
I disabled Keyboard Layout in the KDE Control Center, and everything works properly...
except for the "media" buttons. This is a new Dell Inspiron 6000, and it has the following buttons along the edge: Mute, Vulume Up, Volume Down, Play/Pause, Next, Previous, Stop. Any hints on setting these up to be recognized by X so I can make them shortcuts in mplayer, KMix, etc...?
Hello whysyn,
I can only try a kind of diagnosis of your problem:
IMHO, it seems that, during the installation, you have enabled
the "dead key" technique and the keys you must type twice are
indeed the enabled "dead" keys.
For more details you can google a little or have a look at
Monk15 post and at my reply:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.