cups cannot start after system update: missing conf (with fix)

Bug #1525558 reported by Benoît Rouits
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

cups daemon does not start after update and reboot on December 12 2015.
message of /etc/init.d/cups status:
● cups.service - CUPS Scheduler
   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
   Active: failed (Result: start-limit) since sam. 2015-12-12 20:01:39 CET; 5min ago
     Docs: man:cupsd(8)
  Process: 1569 ExecStart=/usr/sbin/cupsd -l (code=exited, status=1/FAILURE)
 Main PID: 1569 (code=exited, status=1/FAILURE)

déc. 12 20:01:39 grim systemd[1]: Started CUPS Scheduler.
déc. 12 20:01:39 grim systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE
déc. 12 20:01:39 grim systemd[1]: cups.service: Unit entered failed state.
déc. 12 20:01:39 grim systemd[1]: cups.service: Failed with result 'exit-code'.
déc. 12 20:01:39 grim systemd[1]: cups.service: Start request repeated too quickly.
déc. 12 20:01:39 grim systemd[1]: Failed to start CUPS Scheduler.
déc. 12 20:01:39 grim systemd[1]: cups.service: Failed with result 'start-limit'.

uname -a:
Linux grim 4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11 11:39:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

fix with a symbolic link: ln -s /etc/cups/cupsd.conf.O /etc/cups/cupsd.conf and cups starts well.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in cups (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.