Bug 15854 - keyboard support for cherry linux cymotion is getting worse
Summary: keyboard support for cherry linux cymotion is getting worse
Status: RESOLVED MOVED
Alias: None
Product: xkeyboard-config
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: xkb
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2008-05-07 05:40 UTC by Alexander Jenisch
Modified: 2018-12-28 00:36 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Alexander Jenisch 2008-05-07 05:40:08 UTC
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...
Comment 1 Sergey V. Udaltsov 2008-12-23 08:51:43 UTC
I'm afraid your complains are somewhat vague:

1. What exactly is your XKB configuration: driver, ruleset, model, layout(s), options(s)

2. Which keys do not work? What do they produce in xev utility?
Comment 2 GitLab Migration User 2018-12-28 00:36:21 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/42.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.