This seems to be a some kind of desktop/laptop power/resource saving
feature that does not take Web UI to the account. CUPS will immediately
start up again if I open the printing dialog or something.

When I read Stephan's error log as well as my own, it reads:

"I [30/Aug/2016:08:42:33 +0200] Printer sharing is off and there are no jobs 
pending, will restart on demand.
I [30/Aug/2016:08:42:33 +0200] Scheduler shutting down normally."

Maybe some kind of xinetd setup would make it possible to shut CUPS down
but start it up when one tries to access the web UI.

Please do not expire this bug, that is not a solution. and Stephan has
provided the requested error log. WONTFIX would be a better solution if
this is the way it is intended to work.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1598300

Title:
  cups hang after a while

Status in cups package in Ubuntu:
  Incomplete

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: 
enabled)|
  |   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 
package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to