[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#829573: marked as done (cups-browsed: Not restarted after a cups upgrade)

Your message dated Sat, 8 Jul 2017 12:55:42 +0100
with message-id <08072017114917.74926d908e27@desktop.copernicus.org.uk>
and subject line Re: Bug#829573: cups-browsed: Not restarted after a cups upgrade
has caused the Debian Bug report #829573,
regarding cups-browsed: Not restarted after a cups upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
829573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829573
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cups-browsed
Version: 1.9.0-2
Severity: important



After an upgrade to cups 2.1.4-2 on unstable cups-browsed fails to
restart. This was confirmed with

  systemctl restart cups-browsed
  apt-get --reinstall install cups-daemon
  systemctl status cups-browsed

Removing 'Requires=cups.service' from cups-browsed.service restores
the expected behaviour after 'systemctl daemon-reload'.

Regards,

Brian.

--- End Message ---
--- Begin Message --- 
found 829573 1.11.6-3
thanks


On Mon 04 Jul 2016 at 12:25:23 +0100, Brian Potkin wrote:

> After an upgrade to cups 2.1.4-2 on unstable cups-browsed fails to
> restart. This was confirmed with
> 
>   systemctl restart cups-browsed
>   apt-get --reinstall install cups-daemon
>   systemctl status cups-browsed
> 
> Removing 'Requires=cups.service' from cups-browsed.service restores
> the expected behaviour after 'systemctl daemon-reload'.

Removing 'Requires=cups.service' was an observation, not a request. I
know why it there.

On stretch (cups-browsed 1.11.6-3) the same behaviour occurs. Upgrading
to cups-browsed 1.14.1-1 from unstable does not alter the situation.

When it comes a sid (cups-browsed 1.14.1-1) machine we have:

root@test:~# systemctl status cups-browsed.service
• cups-browsed.service - Make remote CUPS printers available locally
   Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2017-07-08 12:26:33 BST; 17min ago
 Main PID: 1317 (cups-browsed)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/cups-browsed.service
           └─1317 /usr/sbin/cups-browsed

• cups-browsed.service - Make remote CUPS printers available locally
   Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2017-07-08 12:46:40 BST; 8s ago
 Main PID: 21468 (cups-browsed)
   CGroup: /system.slice/cups-browsed.service
           └─21468 /usr/sbin/cups-browsed

Jul 08 12:46:40 test systemd[1]: Started Make remote CUPS printers available locally.

for before and after cups-daemon being reinstalled.

Some other system component (systemd?) appears to be involved. Hence
closing the report.
 
Regards,
 
Brian.

--- End Message ---
Reply to: