[Bug 1193147] Re: 95-keyboard-force-release.rules doesn't detect Latitude 6430U or 3330

[Martin Pitt]

Fixed upstream for all Latitude/Precision models now (better to err on
the side of applying it to too many models):
http://cgit.freedesktop.org/systemd/systemd/commit/?id=f6c9f322

Subscribing sponsors for the precise update.

** Also affects: systemd (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: udev (Ubuntu Precise)
   Importance: Undecided
       Status: New

** Also affects: systemd (Ubuntu Precise)
   Importance: Undecided
       Status: New

** No longer affects: systemd (Ubuntu Precise)

** Changed in: udev (Ubuntu)
       Status: New => Invalid

** Changed in: systemd (Ubuntu)
       Status: New => Fix Committed

** Changed in: udev (Ubuntu Precise)
       Status: New => Triaged

** Summary changed:

- 95-keyboard-force-release.rules doesn't detect Latitude 6430U or 3330
+ [keymap] Touchpad key broken on Dell Latitude 6430U and 3330

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1193147

Title:
  [keymap] Touchpad key broken on Dell Latitude 6430U and 3330

Status in “systemd” package in Ubuntu:
  Fix Committed
Status in “udev” package in Ubuntu:
  Invalid
Status in “udev” source package in Precise:
  Triaged

Bug description:
  Precise's udev package doesn't detect that the Dell Latitude 6430U or
  3330 need keyboard force release synthesis. This causes undesirable
  behavior on these two systems. Quantal and upstream udev have an
  updated rule to handle the 6430U. Neither have such a rule to handle
  the 3330. We only ship Ubuntu pre-load systems with an LTS release
  installed, so the fix needs to be in Precise. Here is a patch to
  address both.

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