Hide Forgot
Description of problem: If second keyboard (bluetooth mac keyboard) is attached, it is not recognized as keyboard, but core pointer, so it does not produce valid key events Version-Release number of selected component (if applicable): Fedora 16 with all updates installed to date How reproducible: Plug mac bluetooth keyboard, proceed with bluetooth pairing (enter pin and so on), find that keyboard is detected, but does not work Additional info: Keyboard is detected as core pointer: $ xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎜ ↳ Wacom Intuos4 6x9 stylus id=13 [slave pointer (2)] ⎜ ↳ Wacom Intuos4 6x9 eraser id=14 [slave pointer (2)] ⎜ ↳ Wacom Intuos4 6x9 cursor id=15 [slave pointer (2)] ⎜ ↳ Wacom Intuos4 6x9 pad id=16 [slave pointer (2)] ⎜ ↳ creator’s keyboard id=17 [slave pointer (2)] ^^^^^^^^^^^^^^^^^^^^^^^^^^ ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Power Button id=8 [slave keyboard (3)] ↳ LITEON Technology USB Multimedia Keyboard id=9 [slave keyboard (3)] ↳ LITEON Technology USB Multimedia Keyboard id=10 [slave keyboard (3)] ↳ YAMAHA Corporation YAMAHA KX id=12 [slave keyboard (3)] It work like numeric pad of the usual 105-keys keyboard, i.e. pressing some keys ends up printing numbers in terminal or in keyboard setup applet. And also it provides a pointer (sometimes it is even visible on desktop), which breaks sloppy focus. Keyboards works well in gdm, at least I'm able to enter password correctly. But it does not work in X. xev does not show any key event. hid_apple kernel module is loaded, bluetooth correctly says that it found keyboard, only X is in charge.
Sometimes (rarely) it starts working properly after bluetooth (re)pairing, but after some time it switches back to 'numeric-pad-only' mode, when only keys around JKL work as on numeric pad.
Can you attach the evtest description for this device please?
ok, what I need is your gnome keyboard configuration and the output of xkbcomp -xkb $DISPLAY - I'm actually typing this on a wireless apple keyboard now and it seems to work just fine. The attachment as pointer shouldn't have much effect.
Pressing control/option/command may end up 'stucking' in this event. I.e. I can press 'd' on mac keyboard or on usb one and it will emit ctl+d event closing my terminal and so on Running evtest heals this for some time, but eventually it starts again Here is its output, everything looks ok as well as all keys I press Input driver version is 1.0.1 Input device ID: bus 0x5 vendor 0x5ac product 0x239 version 0x50 Input device name: "creator’s keyboard" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 1 (KEY_ESC) Event code 2 (KEY_1) Event code 3 (KEY_2) Event code 4 (KEY_3) Event code 5 (KEY_4) Event code 6 (KEY_5) Event code 7 (KEY_6) Event code 8 (KEY_7) Event code 9 (KEY_8) Event code 10 (KEY_9) Event code 11 (KEY_0) Event code 12 (KEY_MINUS) Event code 13 (KEY_EQUAL) Event code 14 (KEY_BACKSPACE) Event code 15 (KEY_TAB) Event code 16 (KEY_Q) Event code 17 (KEY_W) Event code 18 (KEY_E) Event code 19 (KEY_R) Event code 20 (KEY_T) Event code 21 (KEY_Y) Event code 22 (KEY_U) Event code 23 (KEY_I) Event code 24 (KEY_O) Event code 25 (KEY_P) Event code 26 (KEY_LEFTBRACE) Event code 27 (KEY_RIGHTBRACE) Event code 28 (KEY_ENTER) Event code 29 (KEY_LEFTCTRL) Event code 30 (KEY_A) Event code 31 (KEY_S) Event code 32 (KEY_D) Event code 33 (KEY_F) Event code 34 (KEY_G) Event code 35 (KEY_H) Event code 36 (KEY_J) Event code 37 (KEY_K) Event code 38 (KEY_L) Event code 39 (KEY_SEMICOLON) Event code 40 (KEY_APOSTROPHE) Event code 41 (KEY_GRAVE) Event code 42 (KEY_LEFTSHIFT) Event code 43 (KEY_BACKSLASH) Event code 44 (KEY_Z) Event code 45 (KEY_X) Event code 46 (KEY_C) Event code 47 (KEY_V) Event code 48 (KEY_B) Event code 49 (KEY_N) Event code 50 (KEY_M) Event code 51 (KEY_COMMA) Event code 52 (KEY_DOT) Event code 53 (KEY_SLASH) Event code 54 (KEY_RIGHTSHIFT) Event code 55 (KEY_KPASTERISK) Event code 56 (KEY_LEFTALT) Event code 57 (KEY_SPACE) Event code 58 (KEY_CAPSLOCK) Event code 59 (KEY_F1) Event code 60 (KEY_F2) Event code 61 (KEY_F3) Event code 62 (KEY_F4) Event code 63 (KEY_F5) Event code 64 (KEY_F6) Event code 65 (KEY_F7) Event code 66 (KEY_F8) Event code 67 (KEY_F9) Event code 68 (KEY_F10) Event code 69 (KEY_NUMLOCK) Event code 70 (KEY_SCROLLLOCK) Event code 71 (KEY_KP7) Event code 72 (KEY_KP8) Event code 73 (KEY_KP9) Event code 74 (KEY_KPMINUS) Event code 75 (KEY_KP4) Event code 76 (KEY_KP5) Event code 77 (KEY_KP6) Event code 78 (KEY_KPPLUS) Event code 79 (KEY_KP1) Event code 80 (KEY_KP2) Event code 81 (KEY_KP3) Event code 82 (KEY_KP0) Event code 83 (KEY_KPDOT) Event code 85 (KEY_ZENKAKUHANKAKU) Event code 86 (KEY_102ND) Event code 87 (KEY_F11) Event code 88 (KEY_F12) Event code 89 (KEY_RO) Event code 90 (KEY_KATAKANA) Event code 91 (KEY_HIRAGANA) Event code 92 (KEY_HENKAN) Event code 93 (KEY_KATAKANAHIRAGANA) Event code 94 (KEY_MUHENKAN) Event code 95 (KEY_KPJPCOMMA) Event code 96 (KEY_KPENTER) Event code 97 (KEY_RIGHTCTRL) Event code 98 (KEY_KPSLASH) Event code 99 (KEY_SYSRQ) Event code 100 (KEY_RIGHTALT) Event code 102 (KEY_HOME) Event code 103 (KEY_UP) Event code 104 (KEY_PAGEUP) Event code 105 (KEY_LEFT) Event code 106 (KEY_RIGHT) Event code 107 (KEY_END) Event code 108 (KEY_DOWN) Event code 109 (KEY_PAGEDOWN) Event code 110 (KEY_INSERT) Event code 111 (KEY_DELETE) Event code 113 (KEY_MUTE) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 116 (KEY_POWER) Event code 117 (KEY_KPEQUAL) Event code 119 (KEY_PAUSE) Event code 120 (KEY_SCALE) Event code 121 (KEY_KPCOMMA) Event code 122 (KEY_HANGUEL) Event code 123 (KEY_HANJA) Event code 124 (KEY_YEN) Event code 125 (KEY_LEFTMETA) Event code 126 (KEY_RIGHTMETA) Event code 127 (KEY_COMPOSE) Event code 128 (KEY_STOP) Event code 129 (KEY_AGAIN) Event code 130 (KEY_PROPS) Event code 131 (KEY_UNDO) Event code 132 (KEY_FRONT) Event code 133 (KEY_COPY) Event code 134 (KEY_OPEN) Event code 135 (KEY_PASTE) Event code 136 (KEY_FIND) Event code 137 (KEY_CUT) Event code 138 (KEY_HELP) Event code 140 (KEY_CALC) Event code 142 (KEY_SLEEP) Event code 150 (KEY_WWW) Event code 152 (KEY_SCREENLOCK) Event code 158 (KEY_BACK) Event code 159 (KEY_FORWARD) Event code 161 (KEY_EJECTCD) Event code 163 (KEY_NEXTSONG) Event code 164 (KEY_PLAYPAUSE) Event code 165 (KEY_PREVIOUSSONG) Event code 166 (KEY_STOPCD) Event code 168 (KEY_REWIND) Event code 173 (KEY_REFRESH) Event code 176 (KEY_EDIT) Event code 177 (KEY_SCROLLUP) Event code 178 (KEY_SCROLLDOWN) Event code 179 (KEY_KPLEFTPAREN) Event code 180 (KEY_KPRIGHTPAREN) Event code 183 (KEY_F13) Event code 184 (KEY_F14) Event code 185 (KEY_F15) Event code 186 (KEY_F16) Event code 187 (KEY_F17) Event code 188 (KEY_F18) Event code 189 (KEY_F19) Event code 190 (KEY_F20) Event code 191 (KEY_F21) Event code 192 (KEY_F22) Event code 193 (KEY_F23) Event code 194 (KEY_F24) Event code 204 (KEY_DASHBOARD) Event code 208 (KEY_FASTFORWARD) Event code 224 (KEY_BRIGHTNESSDOWN) Event code 225 (KEY_BRIGHTNESSUP) Event code 227 (KEY_SWITCHVIDEOMODE) Event code 228 (KEY_KBDILLUMTOGGLE) Event code 229 (KEY_KBDILLUMDOWN) Event code 230 (KEY_KBDILLUMUP) Event code 240 (KEY_UNKNOWN) Event code 256 (BTN_0) Event code 257 (BTN_1) Event code 464 (KEY_FN) Event type 3 (EV_ABS) Event code 40 (ABS_MISC) Value 0 Min 0 Max 255 Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) Event type 17 (EV_LED) Event code 0 (LED_NUML) Event code 1 (LED_CAPSL) Event code 2 (LED_SCROLLL) Event code 3 (LED_COMPOSE) Event code 4 (LED_KANA) Event type 20 (EV_REP) Testing ... (interrupt to exit) Event: time 1326649926.753088, type 17 (EV_LED), code 2 (LED_SCROLLL), value 0 Event: time 1326649926.753090, type 17 (EV_LED), code 0 (LED_NUML), value 0 Event: time 1326649926.753090, -------------- SYN_REPORT ------------ Event: time 1326649930.493103, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70018 Event: time 1326649930.493107, type 1 (EV_KEY), code 22 (KEY_U), value 1 Event: time 1326649930.493108, -------------- SYN_REPORT ------------ uEvent: time 1326649930.693028, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70018 Event: time 1326649930.693031, type 1 (EV_KEY), code 22 (KEY_U), value 0 Event: time 1326649930.693032, -------------- SYN_REPORT ------------ Event: time 1326649931.330584, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70017 Event: time 1326649931.330590, type 1 (EV_KEY), code 20 (KEY_T), value 1 Event: time 1326649931.330592, -------------- SYN_REPORT ------------ tEvent: time 1326649931.505468, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70017 Event: time 1326649931.505471, type 1 (EV_KEY), code 20 (KEY_T), value 0 Event: time 1326649931.505472, -------------- SYN_REPORT ------------ Event: time 1326649931.805409, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70015 Event: time 1326649931.805413, type 1 (EV_KEY), code 19 (KEY_R), value 1 Event: time 1326649931.805414, -------------- SYN_REPORT ------------ rEvent: time 1326649931.892891, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70008 Event: time 1326649931.892895, type 1 (EV_KEY), code 18 (KEY_E), value 1 Event: time 1326649931.892896, -------------- SYN_REPORT ------------ eEvent: time 1326649931.942898, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70008 Event: time 1326649931.942901, type 1 (EV_KEY), code 18 (KEY_E), value 0 Event: time 1326649931.942901, -------------- SYN_REPORT ------------ Event: time 1326649931.967848, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70015 Event: time 1326649931.967851, type 1 (EV_KEY), code 19 (KEY_R), value 0 Event: time 1326649931.967852, -------------- SYN_REPORT ------------ Event: time 1326649932.455457, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70021 Event: time 1326649932.455460, type 1 (EV_KEY), code 5 (KEY_4), value 1 Event: time 1326649932.455461, -------------- SYN_REPORT ------------ 4Event: time 1326649932.580418, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70021 Event: time 1326649932.580421, type 1 (EV_KEY), code 5 (KEY_4), value 0 Event: time 1326649932.580422, -------------- SYN_REPORT ------------ Event: time 1326649932.867913, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001a Event: time 1326649932.867917, type 1 (EV_KEY), code 17 (KEY_W), value 1 Event: time 1326649932.867917, -------------- SYN_REPORT ------------ wEvent: time 1326649933.030406, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7001a Event: time 1326649933.030409, type 1 (EV_KEY), code 17 (KEY_W), value 0 Event: time 1326649933.030410, -------------- SYN_REPORT ------------ Event: time 1326649934.880535, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70014 Event: time 1326649934.880539, type 1 (EV_KEY), code 16 (KEY_Q), value 1 Event: time 1326649934.880540, -------------- SYN_REPORT ------------ qEvent: time 1326649934.967942, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70014 Event: time 1326649934.967946, type 1 (EV_KEY), code 16 (KEY_Q), value 0 Event: time 1326649934.967947, -------------- SYN_REPORT ------------ Event: time 1326649935.343030, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70014 Event: time 1326649935.343035, type 1 (EV_KEY), code 16 (KEY_Q), value 1 Event: time 1326649935.343036, -------------- SYN_REPORT ------------ qEvent: time 1326649935.443028, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70014 Event: time 1326649935.443032, type 1 (EV_KEY), code 16 (KEY_Q), value 0 Event: time 1326649935.443032, -------------- SYN_REPORT ------------ ^C[zbr@gavana ~]$
Created attachment 555368 [details] xkbcomp output
gnome keyboard has 2 layouts (en/ru, changed via left ctl+shift), bunch of modified shortcuts, but without starting external applications which can mess up with input events
Fn+F6 turned mac keyboard from numeric pad into usual layout, although not vice versa
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.