Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

For some inexplicable reason the capital d key on my Ubuntu system is no longer producing output. Hitting caps lock and then d produces a D. I've tried multiple keyboards and the issue is the same. There's nothing bound to Shift+d under System > Preferences > Keyboard Shortcuts. xev produces the following:

shift + a

KeyPress event, serial 36, synthetic NO, window 0x4c00001,
    root 0x27a, subw 0x0, time 31268952, (130,-16), root:(1000,525),
    state 0x10, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 36, synthetic NO, window 0x4c00001,
    root 0x27a, subw 0x0, time 31269376, (130,-16), root:(1000,525),
    state 0x11, keycode 38 (keysym 0x41, A), same_screen YES,
    XLookupString gives 1 bytes: (41) "A"
    XmbLookupString gives 1 bytes: (41) "A"
    XFilterEvent returns: False

KeyRelease event, serial 36, synthetic NO, window 0x4c00001,
    root 0x27a, subw 0x0, time 31269584, (130,-16), root:(1000,525),
    state 0x11, keycode 38 (keysym 0x41, A), same_screen YES,
    XLookupString gives 1 bytes: (41) "A"
    XFilterEvent returns: False

KeyRelease event, serial 36, synthetic NO, window 0x4c00001,
    root 0x27a, subw 0x0, time 31269608, (130,-16), root:(1000,525),
    state 0x11, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

shift + d

KeyPress event, serial 36, synthetic NO, window 0x4c00001,
    root 0x27a, subw 0x0, time 31102792, (115,-13), root:(985,528),
    state 0x10, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

FocusOut event, serial 36, synthetic NO, window 0x4c00001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 36, synthetic NO, window 0x4c00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 36, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   0   64  0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

KeyRelease event, serial 36, synthetic NO, window 0x4c00001,
    root 0x27a, subw 0x0, time 31103104, (115,-13), root:(985,528),
    state 0x11, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False
share|improve this question

migrated from serverfault.com Jan 15 '12 at 3:18

This question came from our site for professional system and network administrators.

add comment

1 Answer 1

The FocusOut and FocusIn events mean that focus is being pulled by something else. Most likely you have Shift-D assigned as some sort of window manager hotkey.

Review your window manager keybindings and find the offending entry then you should be good.

share|improve this answer
    
How do I review my WM keybindings? –  Jonathan Jan 15 '12 at 18:31
    
What window manager do you use? –  qbi Mar 30 '12 at 23:23
    
I thank you for the answer, but I am a normal user. I don't know what does WM keybindings mean, could you kindly explain? –  user73840 Jun 28 '12 at 16:13
    
WM → Window Manager –  MikeyB Jun 28 '12 at 20:24
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.