sed'ing and writing files to /etc/ in udev rules is evil, bad, and wrong. also, calling systemctl in an udev rule is bound to fail, this should at least be ENV{SYSTEMD_WANTS}+="hplip-printer@003:006.service".
It seems you don't even have a HP printer, do you? Or is this
Bus 003 Device 006: ID 03f0:2514 Hewlett-Packard
actually a printer in disguise? (lsusb says that it's a hub). If it's a printer, could you check if turning it off makes a difference?
Could you please check if moving /lib/udev/rules.d/56-hpmud.rules aside helps?
Ah-haa! For the first two workers I found these gems in the log:
Apr 01 13:58:57 alice systemd-udevd[458]: timeout '/bin/sh -c 'if [ -f /usr/bin/systemctl ]; then /usr/bin/systemctl --no-block start hplip-printer@ 003:006. service; else /usr/bin/nohup /usr/bin/ hp-config_ usb_printer 003:006 ; fi &'' d/dll.conf; if [ $? -eq 0 ];then sed -i -e s/^#hpaio/hpaio/ /etc/sane. d/dll.conf; else grep -q ^hpaio /etc/sane. d/dll.conf; if [ $? -ne 0 ];then echo hpaio >>/etc/ sane.d/ dll.conf; fi;fi'' [5784] exit with return code 0
Apr 01 13:58:57 alice systemd-udevd[458]: '/bin/sh -c 'grep -q ^#hpaio /etc/sane.
sed'ing and writing files to /etc/ in udev rules is evil, bad, and wrong. also, calling systemctl in an udev rule is bound to fail, this should at least be ENV{SYSTEMD_ WANTS}+ ="hplip- printer@ 003:006. service" .
It seems you don't even have a HP printer, do you? Or is this
Bus 003 Device 006: ID 03f0:2514 Hewlett-Packard
actually a printer in disguise? (lsusb says that it's a hub). If it's a printer, could you check if turning it off makes a difference?
Could you please check if moving /lib/udev/ rules.d/ 56-hpmud. rules aside helps?