I have done some tests and have found a solution. Please try it out.

Edit the file (with sudo):


adding a line


in the "[Socket]" section. The file should look like this then:

Description=CUPS Scheduler



Now make sure that this does not produce any editor backup files, like
/lib/systemd/system/cups.socket~ or
/lib/systemd/system/cups.socket.backup. Remove such files now.

Now restart systemd with the command

sudo systemctl daemon-reload

Now systemd does not only restart CUPS via the domain socket but also
via port 631, meaning that it also gets started when trying to access
via the web interface (or any other application which accesses only via
port 631).

Please try it out.

If you do not want to wait everytime until CUPS stops by itself for
doing the tests, you can stop it with

sudo systemctl stop cups

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:

Bug description:
  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, 
status=0/SUCCESS)        |
  | Main PID: 28686 (code=exited, status=0/SUCCESS)                             
  |juil. 01 10:30:01 appli-client systemd[1]: 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     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to