That might be the usual problem with packages removed but not using the purge option. (leaving things in rC state). Would not be the first time this causes issues generally speaking. But the ifupdown hook might get improved. Not that it will likely be used post Xenial with systemd- networkd taking over.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1742712 Title: package removal leave scripts that fail lacking the binaries Status in ubuntu-fan package in Ubuntu: New Bug description: Today I saw on IRC this reported: raub@desktop:~$ sudo ifdown --force br0 && sudo brctl delbr br0 /etc/network/if-down.d/ubuntu-fan: 29: /etc/network/if-down.d/ubuntu-fan: /usr/sbin/fanctl: not found run-parts: /etc/network/if-down.d/ubuntu-fan exited with return code 127 bridge br0 doesn't exist; can't delete it I checked what that could be and found an interesting case. When ubuntu-fan is installed all is fine, we have a hook /etc/network/if-down.d/ubuntu-fan and a binary /usr/sbin/fanctl But if a user removed the package, then we get into trouble. The hook is in /etc and therefore by default considered to be a conffile. Therefore we only have the hook left which fails by: /usr/sbin/fanctl: not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1742712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
