On Wed, 2019-01-02 at 10:32 -0500, Ted To wrote:
> My experience was that a reboot allowed qcontrol to be installed but it
> certainly makes sense that reloading devices could fix the install as
> well. I'm willing to help test this -- would I install the stretch
> qcontrol (not backported), reboot and then try to install the backported
> qcontrol?
I think so, yes. After installing the stretch qcontrol and rebooting
you should run:
udevadm info -q all /dev/input/by-path/platform-gpio_keys-event
And confirm that it does _not_ have a line like:
E: TAGS=:power-switch:systemd:
specifically either there should be no TAGS line or if there is one it
should not have "systemd" in it. I think that correctly replicates the
state before the failing update.
I guess you've have seen it while I was writing this mail, but note my
follow up where I decided that the correct command was:
udevadm trigger -s platform -y gpio_keys && dpkg --configure -a
Thanks!
Ian.
