keyboard support for cherry linux cymotion is getting worse
Submitted by Alexander Jenisch
Assigned to xkb..@..bat.ru
Description
the support for my keyboard of choice is getting worse and worse. by now, it even causes crashes. sometimes only of certain applications sometimes the whole pc. for example: a few minutes ago i had to restart my pc, because amarok would first hang and later crash and take half of my keyboard with it. i mapped my "media" keys to the top right via kde to amarok, so that i can conveniently use start/stop/foward/... for amarok's control. i pressed the forward button and it started "hang". as if they key was still pressed (which it isn't). amarok crashed and all of a sudden, i couldn't use any modifier keys any more. after restarting X (kde 3.5.9+kdm) it was still the same. i rebooted the machine. i still can't use certain key combos. like i'm unable to produce a "pipe" right now. following errors show up in kdm.log:
expected keysym, got XF86KbdLightOnOff: line 70 of pc expected keysym, got XF86KbdBrightnessDown: line 71 of pc expected keysym, got XF86KbdBrightnessUp: line 72 of pc expected keysym, got XF86KbdLightOnOff: line 70 of pc expected keysym, got XF86KbdBrightnessDown: line 71 of pc expected keysym, got XF86KbdBrightnessUp: line 72 of pc expected keysym, got XF86MonBrightnessDown: line 149 of inet expected keysym, got XF86MonBrightnessUp: line 150 of inet expected keysym, got XF86KbdLightOnOff: line 153 of inet expected keysym, got XF86KbdBrightnessDown: line 154 of inet expected keysym, got XF86KbdBrightnessUp: line 155 of inet expected keysym, got XF86Info: line 914 of inet The XKEYBOARD keymap compiler (xkbcomp) reports:
Warning: Type "ONE_LEVEL" has 1 levels, but
<RALT>has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server expected keysym, got XF86KbdLightOnOff: line 70 of pc expected keysym, got XF86KbdBrightnessDown: line 71 of pc expected keysym, got XF86KbdBrightnessUp: line 72 of pc expected keysym, got XF86MonBrightnessDown: line 149 of inet expected keysym, got XF86MonBrightnessUp: line 150 of inet expected keysym, got XF86KbdLightOnOff: line 153 of inet expected keysym, got XF86KbdBrightnessDown: line 154 of inet expected keysym, got XF86KbdBrightnessUp: line 155 of inet expected keysym, got XF86Info: line 914 of inet The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type "ONE_LEVEL" has 1 levels, but<RALT>has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Duplicate shape name "" Using last definition Warning: Duplicate shape name "" Using last definition Warning: Duplicate shape name "" Using last definition Warning: Duplicate shape name "" Using last definition Warning: Duplicate shape name "" Using last definition Warning: Duplicate shape name "" Using last definition Warning: Duplicate shape name "" Using last definition Warning: Duplicate shape name "" Using last definition Warning: Duplicate shape name "" Using last definition Warning: Duplicate shape name "" Using last definition Warning: Duplicate shape name "" Using last definition Warning: Duplicate shape name "" Using last definition Warning: Duplicate shape name "" Using last definition Warning: Duplicate shape name "" Using last definition Error: Section defined without a name Definition ignored Error: Section defined without a name Definition ignored Error: Section defined without a name Definition ignored Error: Section defined without a name Definition ignored Warning: Multiple doodads named "" Using first definition Warning: Multiple doodads named "" Using first definition Warning: Multiple doodads named "" Using first definition Warning: Multiple doodads named "" Using first definition Warning: Multiple doodads named "" Using first definition Warning: Multiple doodads named "" Using first definition Errors from xkbcomp are not fatal to the X server
those 2 years ago i had my keyboard working perfectly and i even submitted a patch for my keyboard. i am not entirely sure, if this is a xorg or a kde problem though...