[Bug 171685] keyboard stops working in kde
Hanno
mannequinZOD at abwesend.de
Thu Apr 9 16:12:41 BST 2009
https://bugs.kde.org/show_bug.cgi?id=171685
Hanno <mannequinZOD at abwesend.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mannequinZOD at abwesend.de
--- Comment #52 from Hanno <mannequinZOD abwesend de> 2009-04-09 17:12:34 ---
SORRY FOR WRITING CAPITALISED; BUT MY SMALL 'E' KEY STOPPED WORKING COMPLETELY.
SHIFT+E STILL WORKS. ALL OTHER KEYS WORK.
IT HAPPENS AS SOON AS I LOGIN INTO X. I USE A NVIDIA CARD, KDE 4.2.69 AND
OPENSUSE 11.1
I NOTICED STRANGE FOCUS IN AND OUT EVENTS IN XEV, WHICH DO NOT HAPPEN WHEN I
PRESS OTHER KEYS AS WELL AS KEYMAPNOTIFY EVENTS
XEV
>>>>>>>>>>>>OUTPUT FOR PRESSING E.G. THE KEY 'r'
KeyPress event, serial 34, synthetic NO, window 0x6400001,
root 0x13b, subw 0x6400002, time 19462844, (26,36), root:(873,61),
state 0x0, keycode 27 (keysym 0x72, r), same_screen YES,
XLookupString gives 1 bytes: (72) "r"
XmbLookupString gives 1 bytes: (72) "r"
XFilterEvent returns: False
KeyRelease event, serial 34, synthetic NO, window 0x6400001,
root 0x13b, subw 0x6400002, time 19462939, (26,36), root:(873,61),
state 0x0, keycode 27 (keysym 0x72, r), same_screen YES,
XLookupString gives 1 bytes: (72) "r"
XFilterEvent returns: False
>>>>>>>>>>>>>>OUTPUT FOR PRESSING SMALL 'E'
FocusOut event, serial 34, synthetic NO, window 0x6400001,
mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 34, synthetic NO, window 0x6400001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys: 59 0 0 4 0 0 0 0 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 34, synthetic NO, window 0x6400001,
root 0x13b, subw 0x6400002, time 19464673, (26,36), root:(873,61),
state 0x0, keycode 26 (keysym 0x65, e), same_screen YES,
XLookupString gives 1 bytes: (65) "e"
XFilterEvent returns: False
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list