> Interestingly, "cups.service: Start request repeated too quickly." appears on a successful run.
This would usually happen if you try things in a loop, (5 or more restarts in 10s); run "systemctl reset-failed <unit>" in between to reset the counter. The journal shows an obvious loop, and at that point the log doesn't tell much because you are running into the restart limit. And could you extend your reproducer to run journalctl --quiet --lines=0 --show-cursor and the beginning, and at the end journalctl -c "s=... (cursor obtained from above)" so that we only see the bits that happen during one run, not the whole noise around 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
