On Fri, Dec 02, 2016 at 10:19:24AM -0000, Martin Pitt wrote: > It sounds like cups.service gets stopped, but around the same time > something tries to start it again, possibly via either cups.path or > cups.socket. In generally, if you need to prevent a service from > restarting, you need to first stop all "auto-activating" units (path, > socket, timer) as well, and before stopping the .service.
In my failure example, I wonder if cupsd itself is triggering systemd to start it as it shuts down (by creating the keepalive file briefly after receiving the shutdown signal but before quitting). However, in the real world failure case, cups.path is stopped before cups.service, so I don't think that can be it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
