touch-packages team mailing list archive

[Timo Aaltonen <tjaalton@xxxxxxxxxx>]

Hello Pali, or anyone else affected,

Accepted systemd into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.14 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Trusty)
       Status: In Progress => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  Update force_release for Dell Latitudes

Status in systemd package in Ubuntu:
  Fix Released
Status in udev package in Ubuntu:
  Invalid
Status in udev source package in Precise:
  Triaged
Status in systemd source package in Trusty:
  Fix Committed
Status in systemd source package in Vivid:
  Fix Released

Bug description:
  Wireless HW switch on Dell Latitude notebooks generate key press event
  via AT Translated Set 2 keyboard, but does *not* generate release key
  event. This means that operating systems and applications see key
  still pressed.

  Scan code of that problematic key is 136 (0x88).

  Fixing this problem can be done via force_release option of atkbd
  kernel driver (by adding 136 scan code to list)

  Kernel developers told me that now only userspace (udev package)
  maintains list of those problematic scan codes and so udev needs to be
  extended/patched to add new values to atkbd kernel driver at runtime.
  See: https://lkml.org/lkml/2015/4/5/157

  Currenly there is file /lib/udev/keymaps/force-release/dell-touchpad
  which contains some force_release scan code for all dell latitude
  notebooks handled by file /lib/udev/rules.d/95-keyboard-force-
  release.rules by rule:

  ENV{DMI_VENDOR}=="Dell Inc.",
  ATTR{[dmi/id]product_name}=="*Latitude*|*Precision*", RUN+="keyboard-
  force-release.sh $devpath dell-touchpad"

  Can you extend either /lib/udev/keymaps/force-release/dell-touchpad or
  /lib/udev/rules.d/95-keyboard-force-release.rules to include also scan
  code 136 (0x88)? Because without is there are problems with HW
  wireless switch!

  This problem was tested on Ubuntu 12.04.5 LTS Precise release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441849/+subscriptions