I had the same problem in Ubuntu 16.04.1. After some testing I removed
all (3) printers and all cups-related packages and reinstalled them. And
now (without any additonal changes) all works fine. The only difference:
The first time I used a port forwarding to the remote print server like
"ssh -L 1631:127.0.0.1:632 someuser@somehost" and a local URl
"127.0.0.1:1631" (because i worked as an unpriviliged user and have a
local CUPS daemon on 631). At some cups-Admin-Pages there where error
pages like "You have to use 127.0.0.1:631...". The second time i stopped
my local cupsd and called "ssh -L 631:127.0.0.1:631 someuser@somehost"
as privileged user.
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
cups hang 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
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~desktop-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp