Bug 21002 - Cherry keyboard model B.Unlimited not available for selection.
Summary: Cherry keyboard model B.Unlimited not available for selection.
Status: RESOLVED FIXED
Alias: None
Product: xkeyboard-config
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: low minor
Assignee: xkb
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2009-04-01 11:13 UTC by Jeff Meldrum
Modified: 2009-04-04 19:03 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Jeff Meldrum 2009-04-01 11:13:14 UTC
The Cherry wireless keyboard model B.Unlimited is not available for selection. The B.Unlimited keyboard is a business wireless keyboard and should be on the list with the other Cherry models. The regular keys work with Generic PC104 but the 4 special keys (calculator, email, home and lock) do not function.
The keys show up through xev as:
xev# | description | icon on the key
161      Unknown       Calculator     
236      Unknown       Email  
178      Unknown       Home
115      Super_L       Lock
Also if possible, a desktop display of the status LEDs would be nice since the keyboard does not have any.
Thank you for reviewing this bug report.
Comment 1 Sergey V. Udaltsov 2009-04-01 14:15:51 UTC
In order to map keycodes to keycode names I have to get some more information. For example, your keyboard driver (and ruleset). Could you please provide:

xprop -root | grep XKB
Comment 2 Jeff Meldrum 2009-04-01 14:32:41 UTC
bugzilla-daemon@freedesktop.org wrote:
> http://bugs.freedesktop.org/show_bug.cgi?id=21002
>
>
> Sergey V. Udaltsov <svu@gnome.org> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>            Keywords|                            |NEEDINFO
>
>
>
>
> --- Comment #1 from Sergey V. Udaltsov <svu@gnome.org>  2009-04-01 14:15:51 PST ---
> In order to map keycodes to keycode names I have to get some more information.
> For example, your keyboard driver (and ruleset). Could you please provide:
>
> xprop -root | grep XKB
>
>
>   
Hi Sergey
The command outputs the following:
xprop -root | grep XKB
_XKB_RULES_NAMES(STRING) = "xfree86", "pc104", "us", "", ""
If you need further information, please do not hesitate to ask. I will
provide ASAP.
Thank you for looking into this matter.
Regards,
Jeff Meldrum
Comment 3 Sergey V. Udaltsov 2009-04-01 14:40:52 UTC
> _XKB_RULES_NAMES(STRING) = "xfree86", "pc104", "us", "", ""
Ok, you're using ruleset xfree86. In that case, 
161=<I21>       Calculator     
236=<I6C>       Email  
178=<I32>       Home
115=<LWIN>      Lock

First 3 keys are covered by any cherry model. Did you try them? For example, Cherry Blue Line

The last one is really giving left window keycode. I do not actually understand what is "Lock" in your case?

> a desktop display of the status LEDs would be nice since the
keyboard does not have any.
This has nothing to do with xk-c, you should file a bug in your favourite DE's bugzilla.
Comment 4 Jeff Meldrum 2009-04-01 16:51:22 UTC
bugzilla-daemon@freedesktop.org wrote:
> http://bugs.freedesktop.org/show_bug.cgi?id=21002
>
> --- Comment #3 from Sergey V. Udaltsov <svu@gnome.org>  2009-04-01 14:40:52 PST ---
>   
>> _XKB_RULES_NAMES(STRING) = "xfree86", "pc104", "us", "", ""
>>     
> Ok, you're using ruleset xfree86. In that case, 
> 161=<I21>       Calculator     
> 236=<I6C>       Email  
> 178=<I32>       Home
> 115=<LWIN>      Lock
>
> First 3 keys are covered by any cherry model. Did you try them? For example,
> Cherry Blue Line
>   
Hi Sergey
No but I will now. I did not originally because the keyboard layout had
more special keys than the B.Unlimited when I searched the Cherry site
and google.
> The last one is really giving left window keycode. I do not actually understand
> what is "Lock" in your case?
>   
The key icon shows a padlock, so I am assuming it is to either to lock
the desktop or for encryption. I cannot find any documentation on the key.
On rechecking with xev  the padlock key produced this result:
$KeyRelease event, serial 34, synthetic NO, window 0x3e00001,
$   root 0x1a6, subw 0x0, time 26678615, (-234,-23), root:(1264,805),
$   state 0x50, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
$   XLookupString gives 0 bytes:
$   XFilterEvent returns: False
$
$KeyRelease event, serial 34, synthetic NO, window 0x3e00001,
$   root 0x1a6, subw 0x0, time 26678615, (-234,-23), root:(1264,805),
$   state 0x10, keycode 46 (keysym 0x6c, l), same_screen YES,
$   XLookupString gives 1 bytes: (6c) "l"
$   XFilterEvent returns: False
Apparently it represents 2 symbols, just I missed that when I first ran
xev. I rechecked three times just to be sure. It seems strange and
puzzling that 2 values are coming up for a single keystroke.  All the
other special keys and standard keys function just show one result per
key stroke through xev.
>> a desktop display of the status LEDs would be nice since the keyboard does not have any.
>>     
> This has nothing to do with xk-c, you should file a bug in your favourite DE's
> bugzilla.
>   
Thank you for pointing me in the right direction. Please accept my
apologizes on reporting it to xk-c.
Regards,
Jeff Meldrum
Comment 5 David Cameron Staples 2009-04-01 18:02:44 UTC
From the xev info, the keyboard is cheating. It's sending <WIN>+<L> with that keypress, which under windows is the shortcut to lock the session.

You would have to use the keyboard shortcuts manager of your window manager to map this *combination* of keys to lock the session.

Under KDE, for example, simply (!) go to "System Settings" > "Keyboard & Mouse" > "Keyboard Shortcuts", under the tab "Shortcut Schemes", there'll be a list of actions under the subtab "Global Actions". Under Desktop is "Lock Session", which defaults to <ALT>+<CTRL>+<L>. Select this line, click on button below which says "Alt+Ctrl+L", on the window that pops up click "Advanced", click in the box next to "Alternate Shortcut", and press that button. It should show "Win+L", and pressing that button, or <WIN>+L, or <ALT>+<CTL>+<L>, should lock your session.
Comment 6 Jeff Meldrum 2009-04-01 18:12:36 UTC
bugzilla-daemon@freedesktop.org wrote:
> http://bugs.freedesktop.org/show_bug.cgi?id=21002
>
>
>
>
>
> --- Comment #5 from David Cameron Staples <staples@cs.mu.oz.au>  2009-04-01 18:02:44 PST ---
> >From the xev info, the keyboard is cheating. It's sending <WIN>+<L> with that
> keypress, which under windows is the shortcut to lock the session.
>
> You would have to use the keyboard shortcuts manager of your window manager to
> map this *combination* of keys to lock the session.
>
> Under KDE, for example, simply (!) go to "System Settings" > "Keyboard & Mouse"
>   
>> "Keyboard Shortcuts", under the tab "Shortcut Schemes", there'll be a list of
>>     
> actions under the subtab "Global Actions". Under Desktop is "Lock Session",
> which defaults to <ALT>+<CTRL>+<L>. Select this line, click on button below
> which says "Alt+Ctrl+L", on the window that pops up click "Advanced", click in
> the box next to "Alternate Shortcut", and press that button. It should show
> "Win+L", and pressing that button, or <WIN>+L, or <ALT>+<CTL>+<L>, should lock
> your session.
>
>
>   
Hi David
Thank you for clarifying the lock key. It now makes sense to me and now
I can assign that key in my desktop/window managers.
Have a good one.
Regards,
Jeff Meldrum
Comment 7 Sergey V. Udaltsov 2009-04-02 15:14:46 UTC
So. did other Cherry model work for your 3 keys?
Comment 8 Jeff Meldrum 2009-04-03 08:47:35 UTC
bugzilla-daemon@freedesktop.org wrote:
> http://bugs.freedesktop.org/show_bug.cgi?id=21002
>
>
>
>
>
> --- Comment #7 from Sergey V. Udaltsov <svu@gnome.org>  2009-04-02 15:14:46 PST ---
> So. did other Cherry model work for your 3 keys?
>
>
>   
Hi Sergey
I am happy to report that the Cherry Blueline keyboard selection works
with the calculator, email and home keys.
The padlock key appears to be a combination off the left Win-key and
letter "L" to lock the desktop outputting both 115 and 46 through xev
when pressed (I missed the second output the first time I reported it).
I thank you for your efforts and appreciate your time.
Jeff Meldrum
Comment 9 Sergey V. Udaltsov 2009-04-03 16:06:06 UTC
Anyway, I've created fake model cherrybunlim, feel free to test from git.
Comment 10 Jeff Meldrum 2009-04-04 19:03:12 UTC
bugzilla-daemon@freedesktop.org wrote:
> http://bugs.freedesktop.org/show_bug.cgi?id=21002
>
>
> Sergey V. Udaltsov <svu@gnome.org> changed:
>
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|NEW                         |RESOLVED
>          Resolution|                            |FIXED
>
>
>
>
> --- Comment #9 from Sergey V. Udaltsov <svu@gnome.org>  2009-04-03 16:06:06 PST ---
> Anyway, I've created fake model cherrybunlim, feel free to test from git.
>
>
>   
Hi Sergey, I will try it out and let you know.
Thank you, regards
Jeff Meldrum


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.