cups-browsed/systemd question
Hi,
in the bug report cited below it is reported that systemd shutdown can
hang on cups-browsed and a suggestion is made how to solve the problem
by modifying the .service file.
Before simply overtaking this change I want to ask more people with
systemd experience, Tim, OdyX, what do you think? Is this the correct fix?
Till
-------- Forwarded Message --------
Subject: [Bug 1266] New: [cups-filters] systemd shutdown can hang on
cups-browsed.service without avahi-daemon
Date: Sat, 28 Feb 2015 22:27:45 +0000
From: bugzilla-daemon@bugs.linuxfoundation.org
To: till.kamppeter@gmail.com
https://bugs.linuxfoundation.org/show_bug.cgi?id=1266
Bug #: 1266
Summary: [cups-filters] systemd shutdown can hang on
cups-browsed.service without avahi-daemon
Product: OpenPrinting
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: cups-filters
AssignedTo: till.kamppeter@gmail.com
ReportedBy: james@nurealm.net
CC: lars@uebernic.de
Classification: Unclassified
cups-filters 1.0.65, on Arch linux
Last I shut down my system, I saw a "waiting on stop job". The log shows:
avahi-daemon[381]: Disconnected from D-Bus, exiting.
avahi-daemon[381]: Got SIGTERM, quitting.
topaz cupsd[380]: Unable to communicate with avahi-daemon: An unexpected
D-Bus
error occured
systemd[1]: Stopped D-Bus System Message Bus.
followed a minute and a half later with:
systemd[1]: cups-browsed.service stop-sigterm timed out. Killing.
systemd[1]: cups-browsed.service: main process exited, code=killed,
status=9/KILL
systemd[1]: Stopped Make remote CUPS printers available locally.
systemd[1]: Unit cups-browsed.service entered failed state.
systemd[1]: cups-browsed.service failed.
I suspect that cups-browsed.service may need
Requires=avahi-daemon.service
or
RequiresOverridable=avahi-daemon.service
rather than simply
Wants=avahi-daemon.service
as is used currently, this with systemd 219.
--
Configure bugmail: https://bugs.linuxfoundation.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
Reply to: