[Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-12-22 Thread Dimitri John Ledkov
** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: init-system-helpers (Ubuntu) Status: Confirmed => Invalid ** Changed in: cups (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: cups (Ubuntu) Milestone: None =>

[Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-12-04 Thread Martin Pitt
> In CUPS everything is OK and as intended. No -- as above, the maintainer scripts need to stop cups.{socket,path} first before stopping cups.service. Also, as it seems you can entirely drop that .path unit as it's fairly useless -- we don't start cups on demand, but it always starts on boot (in

[Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-12-04 Thread Till Kamppeter
** Changed in: cups (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1642966 Title: package cups-daemon 2.1.3-4 failed to

[Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-12-01 Thread Till Kamppeter
Added also an init-system-helpers task, as this package contains the deb-systemd-invoke debhelper. ** Also affects: init-system-helpers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed

[Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2016-12-01 Thread Till Kamppeter
Adding systemd task, as cupsd itself shuts down correctly independent of the presence or absence of the keepalive file. There must be some problem in systemd's shutdown process. For the systemd experts/maintainers: See comment #18 and comment #21 for a reproducer and some explanation of what is