touch-packages team mailing list archive

[Dev-rindeal+bugs-kde-org <293213@xxxxxxxxxxxxxxxxxx>]

For anyone who stumbles upon this bug in quest of finding a solution to
get the keys finally working, there is this utility - xbindkeys, which
you can use until this bug gets resolved.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/293213

Title:
  Qt and kde4libs don't support various multimedia keys

Status in kdelibs:
  Confirmed
Status in Kubuntu Default Settings:
  Invalid
Status in kde4libs package in Ubuntu:
  Fix Released
Status in kubuntu-default-settings package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  Fix Released
Status in Fedora:
  Fix Released

Bug description:
  Binary package hint: kubuntu-default-settings

  13:05 < jdong>     state 0x0, keycode 233 (keysym 0x1008ff02, 
                 XF86MonBrightnessUp), same_screen YES,
  13:05 < jdong>     state 0x0, keycode 232 (keysym 0x1008ff03, 
                 XF86MonBrightnessDown), same_screen YES,

  
  These are the brightness adjustment keys on my Macbook as reported by xev.

  Yet /usr/share/kubuntu-default-settings/kubuntu.xmodmap remaps them
  as:

  keycode 232 = XF86Stop
  keycode 233 = XF86Forward

  
  The result is that brightness keys do not work in Kubuntu.

  
  IMO we shouldn't be blindly mapping keys like this that aren't standardized -- they should be per-keyboard quirks, not system-wide defaults!

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdelibs/+bug/293213/+subscriptions