I tried this on zesty, and in comment #20 Robie tried on xenial, and we
both get:
> Warning: Stopping cups.service, but it can still be activated by:
> cups.path
(I additionally get cups.socket there too). Thus:
> However, in the real world failure case, cups.path is stopped before
> cups.service, so I don't think that can be it.
This actually is not the case in zesty (haven't checked yakkety) any
more -- cups-daemon.prerm does not stop cups.path any more. Thus I
wonder what happens in xenial, as there clearly is a stop.
I cannot yet reproduce this in a clean xenial VM with either robie's
recipe from comment #18 or a repeated "apt-get install --reinstall cups-
daemon". I also tried with tight races like
touch /var/cache/cups/org.cups.cupsd; systemctl stop cups.service
(and also swapping around the commands).
For someone who can reproduce this, can you please do the following:
sudo systemd-analyze set-log-level debug
[... steps to reproduce the bug ...]
sudo systemd-analyze set-log-level info
sudo journalctl -b > /tmp/journal.txt
and attach /tmp/journal.txt here?
** Changed in: cups (Ubuntu)
Status: Confirmed => Incomplete
--
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
