The character "d" is not recognized in console or xterm

rwfoo · 06-16-2007, 12:17 PM

Hi

I am running fedora 7 with kernel 2.6.21-1.3228.fc7 on my IBM thinkpad T60.

For some reason virtual consoles and xterm is no longer able to interpret the action when a type the letter "d". All other characters on my US keyboard show up fine on the terminal.

This started, I think, after the latest update to the present kernel, however, the system under the earlier kernel does the same now.

It is not a hardware problem as you can see. I have no problems in the gnome environment in general (except for xterm) and in applications started from the virtual console such as VIM.

At the login stage under xterm and virtual consoles the letter d, however, will be displayed without problem.

In the console or xterm if I first pres ^v and then "d" the letter d will also be displayed.

So I guess something is wrong with how the console or xterm interprets that key since ^v sends the next character typed directly thru to the device driver with no action or interpretation.

I have not (deliberately) reassigned the key or tried to make behave differently.

This is the output when start xev and press d:

Code:

KeyRelease event, serial 29, synthetic NO, window 0x3600001,
    root 0x3f, subw 0x0, time 883472991, (358,-81), root:(368,16),
    state 0x0, keycode 40 (keysym 0x64, d), same_screen YES,
    XLookupString gives 1 bytes: (64) "d"
    XFilterEvent returns: False

I have searched the internet but nothing seems to pertain to this
problem as they mostly regards getting special characters to work.

Do anyone have a more permanent solution than just writing ^v everytime the letter d is needed?

PTrenholme · 07-14-2007, 09:37 PM

Strange. May we presume you've tried different fonts? (You didn't mention your font settings in xterm or the "virtual" consoles you've tried.) If that presumption is true, then it seems quite strange indeed, and there's little I could suggest.

If the presumption is not correct, have you checked to see if the font you're using is the most current release of the font? Perhaps a flawed font was loaded with the kernel upgrade or some later activity. You could try reloading the font. (I believe, but am not sure, that both kernels would use the same font directory, so a font problem would appear to "back-propagate" to the older kernel.)