Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cups (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1525558
Title:
cups cannot start after system update: missing conf (with fix)
Status in cups package in Ubuntu:
Confirmed
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1525558/+subscriptions
--
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
