On 2014-11-06 20:18:12 +0100, Didier 'OdyX' Raboud wrote: > Le vendredi, 3 octobre 2014, 01.37:16 Vincent Lefevre a écrit : > > On 2014-10-02 18:19:02 +0200, Didier 'OdyX' Raboud wrote: > > > Le jeudi, 2 octobre 2014 17.01:23, vous avez écrit : > > > > During an upgrade, the reload invoked by the cups-filters postinst > > > > script failed: > > > Do you use apparmor ? > > > > No. > > > > > Does this happen with cups-daemon 1.7.5-4 too? > > > > No failures during this upgrade. > > Can you reliably reproduce this bug? I can't and suspect it's > probability is reduced since 1.7.5-7 in which I disabled the socket- > activation of CUPS.
Well, I think why the reload failed: a reason may be that the cupsd daemon was no longer running. In this case, I can reproduce the two messages I obtained during the upgrade: ypig:/home/vlefevre# service cups stop [ ok ] Stopping Common Unix Printing System: cupsd. so that cupds is now stopped. ypig:/home/vlefevre# service cups stop [ ok ] Stopping Common Unix Printing System: cupsd. ypig:/home/vlefevre# service cups reload [FAIL] Reloading Common Unix Printing System: cupsd failed! i.e. I get "ok" with stop even when cupds is already stopped, then I get the reload failure. Before doing that, I saw that cupsd was no longer running, while I hadn't stopped it. So, if this problem occurred before, this could explain the reload failure. I don't know whether cups stopped before the upgrade to cups 1.7.5-7 (and wasn't restarted) or cups failed to be restarted during the upgrade. Unfortunately, there is nothing in the logs about this. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
