What was in your /etc/cups/client.conf (now /etc/cups/client.conf_bak)?
If it pointed to a CUPS on a remote machine, all your CUPS access (from
applications/command line, not web interface) was directed to the remote
machine with a different CUPS setup. Now you are using always the CUPS
on your local machine.
Note that client.conf is deprecated but still working as originally
intended (and so often an admin's nightmare).
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
cups hang after a while
Status in cups package in Ubuntu:
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
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~touch-packages
Post to : email@example.com
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp