Le 29/06/2017 à 23:11, Michael Biebl a écrit : > Picked the wrong line from git blame indeed, this is the correct one > > https://github.com/systemd/systemd/commit/5104943722 > > It's been there since v230 so not a recent change.
Indeed. Looking at my dpkg log on my laptop, the problem started
while I had udev 232-X (but I do not remember exactly when it
started, sorry)
/var/log$ ( zcat dpkg.log*.gz ; cat dpkg.log dpkg.log.1 ) | grep udev | sort |
grep " installed udev"
2016-06-01 16:50:25 status installed udev:amd64 230-2
2016-06-21 11:37:44 status installed udev:amd64 230-2
2016-06-25 14:30:34 status installed udev:amd64 230-3
2016-06-29 21:27:01 status installed udev:amd64 230-3
2016-07-23 23:01:15 status installed udev:amd64 230-7
2016-07-27 17:22:35 status installed udev:amd64 231-1
2016-08-18 22:07:54 status installed udev:amd64 231-3
2016-08-19 00:07:02 status installed udev:amd64 231-4
2016-08-26 17:29:46 status installed udev:amd64 231-4
2016-08-28 09:45:33 status installed udev:amd64 231-5
2016-08-30 16:25:08 status installed udev:amd64 231-5
2016-09-13 21:31:52 status installed udev:amd64 231-6
2016-09-19 14:10:17 status installed udev:amd64 231-6
2016-10-07 23:22:59 status installed udev:amd64 231-9
2016-10-27 17:54:17 status installed udev:amd64 231-10
2016-11-11 10:27:57 status installed udev:amd64 232-3
2016-11-21 13:34:28 status installed udev:amd64 232-5
2016-11-28 19:55:54 status installed udev:amd64 232-6
2016-12-06 11:02:46 status installed udev:amd64 232-7
2016-12-12 11:22:09 status installed udev:amd64 232-7
2016-12-22 20:36:19 status installed udev:amd64 232-8
2017-01-18 13:57:47 status installed udev:amd64 232-10
2017-01-29 18:38:41 status installed udev:amd64 232-14
2017-02-07 11:17:58 status installed udev:amd64 232-15
2017-02-16 21:26:03 status installed udev:amd64 232-18
2017-03-24 09:56:09 status installed udev:amd64 232-21
2017-04-03 16:39:28 status installed udev:amd64 232-22
2017-04-21 21:28:24 status installed udev:amd64 232-22
2017-05-11 08:18:01 status installed udev:amd64 232-23
2017-06-01 09:27:36 status installed udev:amd64 232-24
2017-06-09 09:28:52 status installed udev:amd64 232-25
2017-06-27 13:52:01 status installed udev:amd64 233-9
2017-06-27 14:56:33 status installed udev:amd64 233-9
I just downgraded udev and libudev1 to 232-22 that were installed at
a time I'm sure I had not this problem. Now, I still observe the
problem with this version.
So:
- this is not a change in 60-keyboard.hwdb/udev that trigger the
regression
- but the installed rule in 60-keyboard.hwdb seems wrong on my
hardware.
Can it be an hardware problem? (a key that do not report the
same code anymore?)
I will check with a friend that also have a ZBook laptop
Regards,
Vincent
--
Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org
GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo: deb http://people.debian.org/~vdanjean/debian unstable main
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
