← Back to team overview

kernel-packages team mailing list archive

[Bug 61413] Re: Logitech DiNovo MediaPad should not toggle Numlock


** Tags added: bluez-classic

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.

  Logitech DiNovo MediaPad should not toggle Numlock

Status in bluez package in Ubuntu:

Bug description:

  * Fujitsu/Siemens Amilo M3438G laptop
  * Logitech DiNovo MediaPad via bluetooth

  Short summary:

  Putting the Logitech MediaPad in numerical mode also toggles Numlock,
  making laptop keyboards with numerical keypad emulation on the regular
  keys unusable. Logitech MediaPad should not toggle hardware Numlock,
  but input should still be recognized properly.

  Longer description:

  The MediaPad is basically an external numerical keypad. The laptop
  does not have a separate numeric keypad, but uses numlock to toggle
  some regular keys to numeric mode. So I'm using the MediaPad for this

  The keypad has three "mode" buttons: numerical, navigation and
  calculator (the last one is built in and does not communicate with the

  Problem is that, when I put the MediaPad into numerical input mode,
  Ubuntu takes this as toggling Numlock on (and navigation takes it
  off), which means that when using the MediaPad I can't use large parts
  of my laptop keyboard normally.

  So, I would like to be able to use my MediaPad in numerical mode
  without toggling hardware Numlock.

  I'm sure this could be solved technically, by noticing (via udev?)
  that it's a MediaPad doing the toggle and doing some remapping.

  What I'm not as sure of is if it would have any other implications for
  applications, if anything needs to know that Numlock is toggled or not
  (for input of numbers vs navigation, that is).

  When using either a laptop or the DiNovo regular keyboard, there is no
  conflict with those since they don't have a numeric part, and I would
  think that it would be extremely uncommon to use a full-size keyboard
  and the MediaPad together, since that would, well, not make any sense.

To manage notifications about this bug go to: