For those affected, you can install the version in proposed for the time
being (see comment 21), until we decide how to manage this (see comment
27). As I understand it, this is the exact fix that will eventually land
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
CUPS web interface stops responding after a while
Status in cups package in Ubuntu:
Status in cups source package in Xenial:
after 6 minutes or so, cups is not responding.
it do not produce error on the log, just stop working, worse, it exit with 0
|root@cupsmachine :~# systemctl status cups
|● cups.service - CUPS Scheduler
| Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset:
| Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago
| Docs: man:cupsd(8)
| Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited,
| Main PID: 28686 (code=exited, status=0/SUCCESS)
|juil. 01 10:30:01 appli-client systemd: Started CUPS Scheduler.
I got to launch it again, so I have finish with a cron job like
*/10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' &&
systemctl start cups
but it is a dirty solution. I have no idea of what make it stop.
NB: I have seen problems related to apparmor, this machine has no apparmor
If you want to use the CUPS web interface in Xenial and therefore set
"WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
when it is idle and then an attempt to access http://localhost:631/
via a web browser fails. People get confused as other access to CUPS
Take a CUPS setup on Xenial with no shared print queues and CUPS only
listening on the domain socket. Activate the web interface via
Now you are able to access the web interface via
http://localhost:631/. Wait for some minutes without accessing CUPS
until the CUPS daemon shuts down automatically. Try to open the web
interface again and it will not work.
With the fixed CUPS package CUPS will not auto-shutdown when the web
interface is activated.
Low, as we are removing a simple distro patch to get back to the
original, upstream behavior.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~touch-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp