Latest systemd updates break touchpad disable hotkey on Dell laptops

Oops, indeed: There are a fair number of broken keycodes, and Dell is affected by these: http://paste.ubuntu.com/6040682/

Thanks for the report!

Can you please put the attached file into /lib/udev/hwdb.d/, then run

  sudo dpkg-reconfigure udev

and then reboot and check if this fixes it? Thanks!

For the record, I went through all similar cases in the hwdb file and I believe I caught all of these cases now (only two).

I just tried it on my Latitude 6430u and it so far has not had any effect. All other hotkeys still work but touchpad hotkey doesn't respond.

Kent, this needs some more debugging then. With the updated hwdb in place, can you please run

  udevadm info --export-db > /tmp/udev.txt

and attach /tmp/udev.txt here?

And the output of the following might help, too:

  for e in /sys/class/input/event*; do udevadm test-builtin keyboard $e; done

Here's the output from export-db

Here's the output from the shell command

Ah, I see what's wrong. The DMI modalias doesn't have any spaces in the vendor/product name. Updated hwdb file attached, please wash, rinse, repeat?

Ok. Making some progress, here.

With the new hwdb update it looks as if the hotkey does respond, but, not like one would expect :-) The touchpad hotkey now behaves like it did in the past before we put the keyboard-force-release rules in place. i.e., things appear to get 'stuck' whenever we press the hotkey.

Here's what I observed my Latitude:

1) Press touchpad hotkeys (Fn+F5 in this case).
2) It appears to have no effect
3) Try to type something into the terminal with the keyboard. Nothing happens.
4) Reboot.
5) Upon logging back in, we regain use of the keyboard but the touchpad is disabled.
6) Press the touchpad hotkeys again. The touchpad doesn't come back and we lose control of the keyboard again.
7) Reboot again and the touchpad and keyboard start working.

With the new packages, can we just put the old rules back in for this or will something new have to be cooked up?

Thanks for your help!

With the new hwdb in place, can you please do

  udevadm info --export-db > /tmp/udev.txt

again and attach /tmp/udev.txt and also give me the output of

  for e in /sys/class/input/event*; do udevadm test-builtin keyboard $e; done

again?

> With the new packages, can we just put the old rules back in for this

Not quite, I'm afraid. Let's just fix this properly.

Here's the new udevadm output

And the re-run of the test-builtin keyboard script

Third time's the charm!

Indeed it is! The touchpad hotkey is now working again on my Latitude. Attaching output from the "udevadm test-builtin keyboard" script.

I'll also test this on an Inspiron laptop later today to make sure it's fixed, too.

The fixes also work for the Inspiron laptop. Touchpad hotkey functionality is restored and not hotkeys appear to have regressed.

Started discussing the remaining problem upstream: http://lists.freedesktop.org/archives/systemd-devel/2013-September/012977.html

Previously attached hwdb.d was just a workaround for this problem.

I discussed the problem with upstream, and attached hwdb.d keymap is now an actual fix instead of a workaround (for Samsung models, too). I tested it with udevadm hwdb --test, but if you want to test it on actual hardware again to make triple sure, I'd appreciate. Thanks!

Fixed in my local packaging tree. Will upload after beta-1 freeze.

Hi Martin,

Your latest hwdb.d keymap doesn't seem to introduce any new problems on my test laptops. Everything still appears to work OK.

This bug was fixed in the package systemd - 204-0ubuntu11

---------------
systemd (204-0ubuntu11) saucy; urgency=low

  * Refresh debian/extra/60-keyboard.hwdb from upstream. Fixes keymap
    regressions on Dell and Samsung models. (LP: #1218433)
 -- Martin Pitt <email address hidden> Fri, 06 Sep 2013 15:24:02 +0200