Package: procps Version: 2:3.3.11-3 Scenario:
# apt-get upgrade Setting up procps (2:3.3.11-3) ... Job for systemd-sysctl.service failed because the control process exited with error code. See "systemctl status systemd-sysctl.service" and "journalctl -xe" for details. invoke-rc.d: initscript procps, action "start" failed. dpkg: error processing package procps (--configure): subprocess installed post-installation script returned error exit status 1 Problem: # journalctl -xe systemd[1]: Starting Apply Kernel Variables... systemd-sysctl[11882]: Couldn't write ':windows:M::MZ::/usr/bin/wine:' to 'fs/binfmt_misc/register', ignoring: Invalid argument systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: Failed to start Apply Kernel Variables. In this particular case (as far as I can see) binfmt_misc module rejects to register a handler if there is already one (which was registered at system startup). As a result a lot of the packages could not be configured, because they depend on procps. I would expect that procps performs systemd-sysctl.service restart, but does not stop package installation if it fails. -- With best regards, Dmitry
