Not the same reason between cups and apport; note the different error message, 'unknown job' vs. 'failed to start'.
Is /etc/init/cups.conf intact on the affected system? For apport, this is definitely a bug in apport. The apport.conf checks for $enabled or $force_start being set to 1; if neither of these is set, the pre-start job exits non-zero which is an *error* exit, and upstart propagates that error to the caller. This wasn't being propagated before due solely to bugs in the way dh_installinit was calling upstart jobs in the maintainer scripts, ignoring all errors. The line should be rewritten as: [ "$enabled" = "1" ] || [ "$force_start" = "1" ] || stop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/711497 Title: package cups 1.4.5-1ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs