Cups won't start The 2019 Stack Overflow Developer Survey Results Are In ...
Take groceries in checked luggage
Hiding Certain Lines on Table
Would an alien lifeform be able to achieve space travel if lacking in vision?
Can the prologue be the backstory of your main character?
How to colour the US map with Yellow, Green, Red and Blue to minimize the number of states with the colour of Green
Is above average number of years spent on PhD considered a red flag in future academia or industry positions?
How to stretch delimiters to envolve matrices inside of a kbordermatrix?
Single author papers against my advisor's will?
Why did all the guest students take carriages to the Yule Ball?
Keeping a retro style to sci-fi spaceships?
Sort a list of pairs representing an acyclic, partial automorphism
Typeface like Times New Roman but with "tied" percent sign
When did F become S in typeography, and why?
Windows 10: How to Lock (not sleep) laptop on lid close?
What is this lever in Argentinian toilets?
Did the new image of black hole confirm the general theory of relativity?
Can a novice safely splice in wire to lengthen 5V charging cable?
Make it rain characters
Did the UK government pay "millions and millions of dollars" to try to snag Julian Assange?
How can I define good in a religion that claims no moral authority?
What was the last x86 CPU that did not have the x87 floating-point unit built in?
Do warforged have souls?
Why does this iterative way of solving of equation work?
What do you call a plan that's an alternative plan in case your initial plan fails?
Cups won't start
The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)CUPS service not working, can't find any logsHow to resolve “service start-limit-hit”Service “ntopng” won't startAppArmor systemd startup errorDisable CUPS and CUPS-BROWSED in 16.04Why does my systemd service shut down immediately after running?Systemd doesn't restart monit after killIs there a way to create a detached BYOBU session on system boot?OpenVPN riddling syslog with errors, but otherwise seems to work flawlesslyBoot time takes more than 5 minutes after moving partitions in Ubuntu 18.04systemd-tmpfiles won't startsamba not starting from systemctl: timeout
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have Ubuntu 16.04 which has been perfect until now.
It has been printing perfectly since day one but the other day I got an error which I stupidly failed to write down and I didn't go look at /var/log/syslog
.
The error was something about a cups directory gone missing. At this point I had not been messing with any configuration, it just broke all by itself.
I thought rather than me manually create whatever has gone missing, I will fix it by removing and re-installing software.
I removed and re-installed both HP's print software "hplip" and "cups". This seems to have wrecked cups completely. It no longer starts.
Below is the systemctl status
output for cups
, before and after a start command:
$ systemctl status cups
cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2016-11-06 10:06:50 GMT; 55min ago
Docs: man:cupsd(8)
Process: 1029 ExecStart=/usr/sbin/cupsd -l (code=exited, status=1/FAILURE)
Main PID: 1029 (code=exited, status=1/FAILURE)
Nov 06 10:06:50 vw-desk2 systemd[1]: Started CUPS Scheduler.
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Unit entered failed state.
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Failed with result 'exit-code'.
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Start request repeated too quickly.
Nov 06 10:06:50 vw-desk2 systemd[1]: Failed to start CUPS Scheduler.
Nov 06 10:06:52 vw-desk2 systemd[1]: cups.service: Start request repeated too quickly.
Nov 06 10:06:52 vw-desk2 systemd[1]: Failed to start CUPS Scheduler.
vince@vw-desk2:~$
vince@vw-desk2:~$ systemctl start cups
vince@vw-desk2:~$
vince@vw-desk2:~$ systemctl status cups
cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2016-11-06 11:03:42 GMT; 24s ago
Docs: man:cupsd(8)
Process: 3664 ExecStart=/usr/sbin/cupsd -l (code=exited, status=1/FAILURE)
Main PID: 3664 (code=exited, status=1/FAILURE)
Nov 06 11:03:42 vw-desk2 systemd[1]: Started CUPS Scheduler.
Nov 06 11:03:42 vw-desk2 systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE
Nov 06 11:03:42 vw-desk2 systemd[1]: cups.service: Unit entered failed state.
Nov 06 11:03:42 vw-desk2 systemd[1]: cups.service: Failed with result 'exit-code'.
/var/log/syslog
doesn't say anything which jumps out at me:
Nov 6 10:11:54 vw-desk2 anacron[786]: Job `cron.daily' terminated
Nov 6 10:11:54 vw-desk2 anacron[786]: Normal exit (1 job run)
Nov 6 10:17:01 vw-desk2 CRON[3371]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Nov 6 10:19:11 vw-desk2 AptDaemon: INFO: Quitting due to inactivity
Nov 6 10:19:11 vw-desk2 AptDaemon: INFO: Quitting was requested
Nov 6 10:19:11 vw-desk2 org.debian.apt[843]: 10:19:11 AptDaemon [INFO]: Quitting due to inactivity
Nov 6 10:19:11 vw-desk2 org.debian.apt[843]: 10:19:11 AptDaemon [INFO]: Quitting was requested
Nov 6 10:21:52 vw-desk2 systemd[1]: Starting Cleanup of Temporary Directories...
Nov 6 10:21:52 vw-desk2 systemd-tmpfiles[3435]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Nov 6 10:21:52 vw-desk2 systemd[1]: Started Cleanup of Temporary Directories.
Nov 6 10:28:01 vw-desk2 CRON[3481]: (root) CMD ( test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond)
Nov 6 10:30:29 vw-desk2 systemd-timesyncd[409]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).
Nov 6 10:30:29 vw-desk2 systemd-timesyncd[409]: Synchronized to time server 91.189.89.198:123 (ntp.ubuntu.com).
Nov 6 11:03:37 vw-desk2 gnome-session[2312]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Nov 6 11:03:42 vw-desk2 systemd[1]: Started CUPS Scheduler.
Nov 6 11:03:42 vw-desk2 systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE
Nov 6 11:03:42 vw-desk2 systemd[1]: cups.service: Unit entered failed state.
Nov 6 11:03:42 vw-desk2 systemd[1]: cups.service: Failed with result 'exit-code'.
Nov 6 11:03:42 vw-desk2 kernel: [ 3413.846764] audit_printk_skb: 84 callbacks suppressed
Nov 6 11:03:42 vw-desk2 kernel: [ 3413.846767] audit: type=1400 audit(1478430222.644:39): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/cupsd" name="/run/systemd/journal/socket" pid=3664 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
On second thoughts, that last line looks like it must be relevant.
How can I get printing working again?
printing configuration systemd
add a comment |
I have Ubuntu 16.04 which has been perfect until now.
It has been printing perfectly since day one but the other day I got an error which I stupidly failed to write down and I didn't go look at /var/log/syslog
.
The error was something about a cups directory gone missing. At this point I had not been messing with any configuration, it just broke all by itself.
I thought rather than me manually create whatever has gone missing, I will fix it by removing and re-installing software.
I removed and re-installed both HP's print software "hplip" and "cups". This seems to have wrecked cups completely. It no longer starts.
Below is the systemctl status
output for cups
, before and after a start command:
$ systemctl status cups
cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2016-11-06 10:06:50 GMT; 55min ago
Docs: man:cupsd(8)
Process: 1029 ExecStart=/usr/sbin/cupsd -l (code=exited, status=1/FAILURE)
Main PID: 1029 (code=exited, status=1/FAILURE)
Nov 06 10:06:50 vw-desk2 systemd[1]: Started CUPS Scheduler.
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Unit entered failed state.
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Failed with result 'exit-code'.
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Start request repeated too quickly.
Nov 06 10:06:50 vw-desk2 systemd[1]: Failed to start CUPS Scheduler.
Nov 06 10:06:52 vw-desk2 systemd[1]: cups.service: Start request repeated too quickly.
Nov 06 10:06:52 vw-desk2 systemd[1]: Failed to start CUPS Scheduler.
vince@vw-desk2:~$
vince@vw-desk2:~$ systemctl start cups
vince@vw-desk2:~$
vince@vw-desk2:~$ systemctl status cups
cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2016-11-06 11:03:42 GMT; 24s ago
Docs: man:cupsd(8)
Process: 3664 ExecStart=/usr/sbin/cupsd -l (code=exited, status=1/FAILURE)
Main PID: 3664 (code=exited, status=1/FAILURE)
Nov 06 11:03:42 vw-desk2 systemd[1]: Started CUPS Scheduler.
Nov 06 11:03:42 vw-desk2 systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE
Nov 06 11:03:42 vw-desk2 systemd[1]: cups.service: Unit entered failed state.
Nov 06 11:03:42 vw-desk2 systemd[1]: cups.service: Failed with result 'exit-code'.
/var/log/syslog
doesn't say anything which jumps out at me:
Nov 6 10:11:54 vw-desk2 anacron[786]: Job `cron.daily' terminated
Nov 6 10:11:54 vw-desk2 anacron[786]: Normal exit (1 job run)
Nov 6 10:17:01 vw-desk2 CRON[3371]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Nov 6 10:19:11 vw-desk2 AptDaemon: INFO: Quitting due to inactivity
Nov 6 10:19:11 vw-desk2 AptDaemon: INFO: Quitting was requested
Nov 6 10:19:11 vw-desk2 org.debian.apt[843]: 10:19:11 AptDaemon [INFO]: Quitting due to inactivity
Nov 6 10:19:11 vw-desk2 org.debian.apt[843]: 10:19:11 AptDaemon [INFO]: Quitting was requested
Nov 6 10:21:52 vw-desk2 systemd[1]: Starting Cleanup of Temporary Directories...
Nov 6 10:21:52 vw-desk2 systemd-tmpfiles[3435]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Nov 6 10:21:52 vw-desk2 systemd[1]: Started Cleanup of Temporary Directories.
Nov 6 10:28:01 vw-desk2 CRON[3481]: (root) CMD ( test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond)
Nov 6 10:30:29 vw-desk2 systemd-timesyncd[409]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).
Nov 6 10:30:29 vw-desk2 systemd-timesyncd[409]: Synchronized to time server 91.189.89.198:123 (ntp.ubuntu.com).
Nov 6 11:03:37 vw-desk2 gnome-session[2312]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Nov 6 11:03:42 vw-desk2 systemd[1]: Started CUPS Scheduler.
Nov 6 11:03:42 vw-desk2 systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE
Nov 6 11:03:42 vw-desk2 systemd[1]: cups.service: Unit entered failed state.
Nov 6 11:03:42 vw-desk2 systemd[1]: cups.service: Failed with result 'exit-code'.
Nov 6 11:03:42 vw-desk2 kernel: [ 3413.846764] audit_printk_skb: 84 callbacks suppressed
Nov 6 11:03:42 vw-desk2 kernel: [ 3413.846767] audit: type=1400 audit(1478430222.644:39): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/cupsd" name="/run/systemd/journal/socket" pid=3664 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
On second thoughts, that last line looks like it must be relevant.
How can I get printing working again?
printing configuration systemd
add a comment |
I have Ubuntu 16.04 which has been perfect until now.
It has been printing perfectly since day one but the other day I got an error which I stupidly failed to write down and I didn't go look at /var/log/syslog
.
The error was something about a cups directory gone missing. At this point I had not been messing with any configuration, it just broke all by itself.
I thought rather than me manually create whatever has gone missing, I will fix it by removing and re-installing software.
I removed and re-installed both HP's print software "hplip" and "cups". This seems to have wrecked cups completely. It no longer starts.
Below is the systemctl status
output for cups
, before and after a start command:
$ systemctl status cups
cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2016-11-06 10:06:50 GMT; 55min ago
Docs: man:cupsd(8)
Process: 1029 ExecStart=/usr/sbin/cupsd -l (code=exited, status=1/FAILURE)
Main PID: 1029 (code=exited, status=1/FAILURE)
Nov 06 10:06:50 vw-desk2 systemd[1]: Started CUPS Scheduler.
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Unit entered failed state.
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Failed with result 'exit-code'.
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Start request repeated too quickly.
Nov 06 10:06:50 vw-desk2 systemd[1]: Failed to start CUPS Scheduler.
Nov 06 10:06:52 vw-desk2 systemd[1]: cups.service: Start request repeated too quickly.
Nov 06 10:06:52 vw-desk2 systemd[1]: Failed to start CUPS Scheduler.
vince@vw-desk2:~$
vince@vw-desk2:~$ systemctl start cups
vince@vw-desk2:~$
vince@vw-desk2:~$ systemctl status cups
cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2016-11-06 11:03:42 GMT; 24s ago
Docs: man:cupsd(8)
Process: 3664 ExecStart=/usr/sbin/cupsd -l (code=exited, status=1/FAILURE)
Main PID: 3664 (code=exited, status=1/FAILURE)
Nov 06 11:03:42 vw-desk2 systemd[1]: Started CUPS Scheduler.
Nov 06 11:03:42 vw-desk2 systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE
Nov 06 11:03:42 vw-desk2 systemd[1]: cups.service: Unit entered failed state.
Nov 06 11:03:42 vw-desk2 systemd[1]: cups.service: Failed with result 'exit-code'.
/var/log/syslog
doesn't say anything which jumps out at me:
Nov 6 10:11:54 vw-desk2 anacron[786]: Job `cron.daily' terminated
Nov 6 10:11:54 vw-desk2 anacron[786]: Normal exit (1 job run)
Nov 6 10:17:01 vw-desk2 CRON[3371]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Nov 6 10:19:11 vw-desk2 AptDaemon: INFO: Quitting due to inactivity
Nov 6 10:19:11 vw-desk2 AptDaemon: INFO: Quitting was requested
Nov 6 10:19:11 vw-desk2 org.debian.apt[843]: 10:19:11 AptDaemon [INFO]: Quitting due to inactivity
Nov 6 10:19:11 vw-desk2 org.debian.apt[843]: 10:19:11 AptDaemon [INFO]: Quitting was requested
Nov 6 10:21:52 vw-desk2 systemd[1]: Starting Cleanup of Temporary Directories...
Nov 6 10:21:52 vw-desk2 systemd-tmpfiles[3435]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Nov 6 10:21:52 vw-desk2 systemd[1]: Started Cleanup of Temporary Directories.
Nov 6 10:28:01 vw-desk2 CRON[3481]: (root) CMD ( test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond)
Nov 6 10:30:29 vw-desk2 systemd-timesyncd[409]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).
Nov 6 10:30:29 vw-desk2 systemd-timesyncd[409]: Synchronized to time server 91.189.89.198:123 (ntp.ubuntu.com).
Nov 6 11:03:37 vw-desk2 gnome-session[2312]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Nov 6 11:03:42 vw-desk2 systemd[1]: Started CUPS Scheduler.
Nov 6 11:03:42 vw-desk2 systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE
Nov 6 11:03:42 vw-desk2 systemd[1]: cups.service: Unit entered failed state.
Nov 6 11:03:42 vw-desk2 systemd[1]: cups.service: Failed with result 'exit-code'.
Nov 6 11:03:42 vw-desk2 kernel: [ 3413.846764] audit_printk_skb: 84 callbacks suppressed
Nov 6 11:03:42 vw-desk2 kernel: [ 3413.846767] audit: type=1400 audit(1478430222.644:39): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/cupsd" name="/run/systemd/journal/socket" pid=3664 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
On second thoughts, that last line looks like it must be relevant.
How can I get printing working again?
printing configuration systemd
I have Ubuntu 16.04 which has been perfect until now.
It has been printing perfectly since day one but the other day I got an error which I stupidly failed to write down and I didn't go look at /var/log/syslog
.
The error was something about a cups directory gone missing. At this point I had not been messing with any configuration, it just broke all by itself.
I thought rather than me manually create whatever has gone missing, I will fix it by removing and re-installing software.
I removed and re-installed both HP's print software "hplip" and "cups". This seems to have wrecked cups completely. It no longer starts.
Below is the systemctl status
output for cups
, before and after a start command:
$ systemctl status cups
cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2016-11-06 10:06:50 GMT; 55min ago
Docs: man:cupsd(8)
Process: 1029 ExecStart=/usr/sbin/cupsd -l (code=exited, status=1/FAILURE)
Main PID: 1029 (code=exited, status=1/FAILURE)
Nov 06 10:06:50 vw-desk2 systemd[1]: Started CUPS Scheduler.
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Unit entered failed state.
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Failed with result 'exit-code'.
Nov 06 10:06:50 vw-desk2 systemd[1]: cups.service: Start request repeated too quickly.
Nov 06 10:06:50 vw-desk2 systemd[1]: Failed to start CUPS Scheduler.
Nov 06 10:06:52 vw-desk2 systemd[1]: cups.service: Start request repeated too quickly.
Nov 06 10:06:52 vw-desk2 systemd[1]: Failed to start CUPS Scheduler.
vince@vw-desk2:~$
vince@vw-desk2:~$ systemctl start cups
vince@vw-desk2:~$
vince@vw-desk2:~$ systemctl status cups
cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2016-11-06 11:03:42 GMT; 24s ago
Docs: man:cupsd(8)
Process: 3664 ExecStart=/usr/sbin/cupsd -l (code=exited, status=1/FAILURE)
Main PID: 3664 (code=exited, status=1/FAILURE)
Nov 06 11:03:42 vw-desk2 systemd[1]: Started CUPS Scheduler.
Nov 06 11:03:42 vw-desk2 systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE
Nov 06 11:03:42 vw-desk2 systemd[1]: cups.service: Unit entered failed state.
Nov 06 11:03:42 vw-desk2 systemd[1]: cups.service: Failed with result 'exit-code'.
/var/log/syslog
doesn't say anything which jumps out at me:
Nov 6 10:11:54 vw-desk2 anacron[786]: Job `cron.daily' terminated
Nov 6 10:11:54 vw-desk2 anacron[786]: Normal exit (1 job run)
Nov 6 10:17:01 vw-desk2 CRON[3371]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Nov 6 10:19:11 vw-desk2 AptDaemon: INFO: Quitting due to inactivity
Nov 6 10:19:11 vw-desk2 AptDaemon: INFO: Quitting was requested
Nov 6 10:19:11 vw-desk2 org.debian.apt[843]: 10:19:11 AptDaemon [INFO]: Quitting due to inactivity
Nov 6 10:19:11 vw-desk2 org.debian.apt[843]: 10:19:11 AptDaemon [INFO]: Quitting was requested
Nov 6 10:21:52 vw-desk2 systemd[1]: Starting Cleanup of Temporary Directories...
Nov 6 10:21:52 vw-desk2 systemd-tmpfiles[3435]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Nov 6 10:21:52 vw-desk2 systemd[1]: Started Cleanup of Temporary Directories.
Nov 6 10:28:01 vw-desk2 CRON[3481]: (root) CMD ( test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond)
Nov 6 10:30:29 vw-desk2 systemd-timesyncd[409]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com).
Nov 6 10:30:29 vw-desk2 systemd-timesyncd[409]: Synchronized to time server 91.189.89.198:123 (ntp.ubuntu.com).
Nov 6 11:03:37 vw-desk2 gnome-session[2312]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
Nov 6 11:03:42 vw-desk2 systemd[1]: Started CUPS Scheduler.
Nov 6 11:03:42 vw-desk2 systemd[1]: cups.service: Main process exited, code=exited, status=1/FAILURE
Nov 6 11:03:42 vw-desk2 systemd[1]: cups.service: Unit entered failed state.
Nov 6 11:03:42 vw-desk2 systemd[1]: cups.service: Failed with result 'exit-code'.
Nov 6 11:03:42 vw-desk2 kernel: [ 3413.846764] audit_printk_skb: 84 callbacks suppressed
Nov 6 11:03:42 vw-desk2 kernel: [ 3413.846767] audit: type=1400 audit(1478430222.644:39): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/cupsd" name="/run/systemd/journal/socket" pid=3664 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0
On second thoughts, that last line looks like it must be relevant.
How can I get printing working again?
printing configuration systemd
printing configuration systemd
edited Sep 20 '17 at 10:35
David Foerster
28.6k1367113
28.6k1367113
asked Nov 6 '16 at 11:55
user835745user835745
12614
12614
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
This happened to me too. Working consistently than rebooted to nothing. I found a couple of apparmor-denied messages in syslog but nothing productive.
Then I noticed /etc/cups/cupsd.conf
had gone missing. That was the problem.
You could purse-and-install the cups-daemon
but it does ship a default-level config file that you can just copy over.
sudo cp /usr/share/cups/cupsd.conf.default /etc/cups/cupsd.conf
sudo service cups restart
add a comment |
systemd doesn't appear to be providing a lot of extra information.
I'm no cups expert but a general approach would be to attempt building a system with some integrity by uninstalling the cups packages completely, then reinstalling and then adding printers
As I said in my original question, I had already uninstalled and re-installed cups. Cups has not run since. I did this again first apt remove cups, then apt purge cups. Followed by apt install cups.
– user835745
Nov 8 '16 at 18:39
Googling tells me I should have a file named /etc/cups/cupsd.conf I don't have that file
– user835745
Nov 8 '16 at 18:42
add a comment |
I think I managed to reproduce this bug.
In my case, problems arose when I used system-config-printer tool to change one setting - preserving the printer jobs.
After that, the cupsd.conf was reduced to 22 bytes, and cupsd won't start. Replacing the faulty copsd.conf solved the starting of cupsd, but syste-config-tool (1.2.11-2ubuntu1) breakes it again when I try to change that setting on my ubunut 18.10 desktop.
On my system, the tool made cupsd.conf.0 file that was functional:
LogLevel warn
PageLogFormat
MaxLogSize 0
Port 631
Listen /run/cups/cups.sock
Browsing On
BrowseLocalProtocols dnssd
DefaultAuthType Basic
WebInterface Yes
<Location />
Order allow,deny
Allow all
</Location>
<Location /admin>
</Location>
<Location /admin/conf>
AuthType Default
Require user @SYSTEM
</Location>
<Location /admin/log>
AuthType Default
Require user @SYSTEM
Order allow,deny
</Location>
<Policy default>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Authenticate-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
# Only the owner or an administrator can cancel a job...
<Limit Cancel-Job>
Order deny,allow
Require user @OWNER @SYSTEM
</Limit>
</Policy>
<Policy authenticated>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
AuthType Default
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
<Policy kerberos>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
AuthType Negotiate
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Negotiate
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Negotiate
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f846177%2fcups-wont-start%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
This happened to me too. Working consistently than rebooted to nothing. I found a couple of apparmor-denied messages in syslog but nothing productive.
Then I noticed /etc/cups/cupsd.conf
had gone missing. That was the problem.
You could purse-and-install the cups-daemon
but it does ship a default-level config file that you can just copy over.
sudo cp /usr/share/cups/cupsd.conf.default /etc/cups/cupsd.conf
sudo service cups restart
add a comment |
This happened to me too. Working consistently than rebooted to nothing. I found a couple of apparmor-denied messages in syslog but nothing productive.
Then I noticed /etc/cups/cupsd.conf
had gone missing. That was the problem.
You could purse-and-install the cups-daemon
but it does ship a default-level config file that you can just copy over.
sudo cp /usr/share/cups/cupsd.conf.default /etc/cups/cupsd.conf
sudo service cups restart
add a comment |
This happened to me too. Working consistently than rebooted to nothing. I found a couple of apparmor-denied messages in syslog but nothing productive.
Then I noticed /etc/cups/cupsd.conf
had gone missing. That was the problem.
You could purse-and-install the cups-daemon
but it does ship a default-level config file that you can just copy over.
sudo cp /usr/share/cups/cupsd.conf.default /etc/cups/cupsd.conf
sudo service cups restart
This happened to me too. Working consistently than rebooted to nothing. I found a couple of apparmor-denied messages in syslog but nothing productive.
Then I noticed /etc/cups/cupsd.conf
had gone missing. That was the problem.
You could purse-and-install the cups-daemon
but it does ship a default-level config file that you can just copy over.
sudo cp /usr/share/cups/cupsd.conf.default /etc/cups/cupsd.conf
sudo service cups restart
edited Apr 13 '17 at 12:24
Community♦
1
1
answered Nov 16 '16 at 12:35
Oli♦Oli
224k90567768
224k90567768
add a comment |
add a comment |
systemd doesn't appear to be providing a lot of extra information.
I'm no cups expert but a general approach would be to attempt building a system with some integrity by uninstalling the cups packages completely, then reinstalling and then adding printers
As I said in my original question, I had already uninstalled and re-installed cups. Cups has not run since. I did this again first apt remove cups, then apt purge cups. Followed by apt install cups.
– user835745
Nov 8 '16 at 18:39
Googling tells me I should have a file named /etc/cups/cupsd.conf I don't have that file
– user835745
Nov 8 '16 at 18:42
add a comment |
systemd doesn't appear to be providing a lot of extra information.
I'm no cups expert but a general approach would be to attempt building a system with some integrity by uninstalling the cups packages completely, then reinstalling and then adding printers
As I said in my original question, I had already uninstalled and re-installed cups. Cups has not run since. I did this again first apt remove cups, then apt purge cups. Followed by apt install cups.
– user835745
Nov 8 '16 at 18:39
Googling tells me I should have a file named /etc/cups/cupsd.conf I don't have that file
– user835745
Nov 8 '16 at 18:42
add a comment |
systemd doesn't appear to be providing a lot of extra information.
I'm no cups expert but a general approach would be to attempt building a system with some integrity by uninstalling the cups packages completely, then reinstalling and then adding printers
systemd doesn't appear to be providing a lot of extra information.
I'm no cups expert but a general approach would be to attempt building a system with some integrity by uninstalling the cups packages completely, then reinstalling and then adding printers
answered Nov 7 '16 at 5:59
TonyTony
112
112
As I said in my original question, I had already uninstalled and re-installed cups. Cups has not run since. I did this again first apt remove cups, then apt purge cups. Followed by apt install cups.
– user835745
Nov 8 '16 at 18:39
Googling tells me I should have a file named /etc/cups/cupsd.conf I don't have that file
– user835745
Nov 8 '16 at 18:42
add a comment |
As I said in my original question, I had already uninstalled and re-installed cups. Cups has not run since. I did this again first apt remove cups, then apt purge cups. Followed by apt install cups.
– user835745
Nov 8 '16 at 18:39
Googling tells me I should have a file named /etc/cups/cupsd.conf I don't have that file
– user835745
Nov 8 '16 at 18:42
As I said in my original question, I had already uninstalled and re-installed cups. Cups has not run since. I did this again first apt remove cups, then apt purge cups. Followed by apt install cups.
– user835745
Nov 8 '16 at 18:39
As I said in my original question, I had already uninstalled and re-installed cups. Cups has not run since. I did this again first apt remove cups, then apt purge cups. Followed by apt install cups.
– user835745
Nov 8 '16 at 18:39
Googling tells me I should have a file named /etc/cups/cupsd.conf I don't have that file
– user835745
Nov 8 '16 at 18:42
Googling tells me I should have a file named /etc/cups/cupsd.conf I don't have that file
– user835745
Nov 8 '16 at 18:42
add a comment |
I think I managed to reproduce this bug.
In my case, problems arose when I used system-config-printer tool to change one setting - preserving the printer jobs.
After that, the cupsd.conf was reduced to 22 bytes, and cupsd won't start. Replacing the faulty copsd.conf solved the starting of cupsd, but syste-config-tool (1.2.11-2ubuntu1) breakes it again when I try to change that setting on my ubunut 18.10 desktop.
On my system, the tool made cupsd.conf.0 file that was functional:
LogLevel warn
PageLogFormat
MaxLogSize 0
Port 631
Listen /run/cups/cups.sock
Browsing On
BrowseLocalProtocols dnssd
DefaultAuthType Basic
WebInterface Yes
<Location />
Order allow,deny
Allow all
</Location>
<Location /admin>
</Location>
<Location /admin/conf>
AuthType Default
Require user @SYSTEM
</Location>
<Location /admin/log>
AuthType Default
Require user @SYSTEM
Order allow,deny
</Location>
<Policy default>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Authenticate-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
# Only the owner or an administrator can cancel a job...
<Limit Cancel-Job>
Order deny,allow
Require user @OWNER @SYSTEM
</Limit>
</Policy>
<Policy authenticated>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
AuthType Default
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
<Policy kerberos>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
AuthType Negotiate
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Negotiate
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Negotiate
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
New contributor
add a comment |
I think I managed to reproduce this bug.
In my case, problems arose when I used system-config-printer tool to change one setting - preserving the printer jobs.
After that, the cupsd.conf was reduced to 22 bytes, and cupsd won't start. Replacing the faulty copsd.conf solved the starting of cupsd, but syste-config-tool (1.2.11-2ubuntu1) breakes it again when I try to change that setting on my ubunut 18.10 desktop.
On my system, the tool made cupsd.conf.0 file that was functional:
LogLevel warn
PageLogFormat
MaxLogSize 0
Port 631
Listen /run/cups/cups.sock
Browsing On
BrowseLocalProtocols dnssd
DefaultAuthType Basic
WebInterface Yes
<Location />
Order allow,deny
Allow all
</Location>
<Location /admin>
</Location>
<Location /admin/conf>
AuthType Default
Require user @SYSTEM
</Location>
<Location /admin/log>
AuthType Default
Require user @SYSTEM
Order allow,deny
</Location>
<Policy default>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Authenticate-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
# Only the owner or an administrator can cancel a job...
<Limit Cancel-Job>
Order deny,allow
Require user @OWNER @SYSTEM
</Limit>
</Policy>
<Policy authenticated>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
AuthType Default
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
<Policy kerberos>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
AuthType Negotiate
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Negotiate
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Negotiate
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
New contributor
add a comment |
I think I managed to reproduce this bug.
In my case, problems arose when I used system-config-printer tool to change one setting - preserving the printer jobs.
After that, the cupsd.conf was reduced to 22 bytes, and cupsd won't start. Replacing the faulty copsd.conf solved the starting of cupsd, but syste-config-tool (1.2.11-2ubuntu1) breakes it again when I try to change that setting on my ubunut 18.10 desktop.
On my system, the tool made cupsd.conf.0 file that was functional:
LogLevel warn
PageLogFormat
MaxLogSize 0
Port 631
Listen /run/cups/cups.sock
Browsing On
BrowseLocalProtocols dnssd
DefaultAuthType Basic
WebInterface Yes
<Location />
Order allow,deny
Allow all
</Location>
<Location /admin>
</Location>
<Location /admin/conf>
AuthType Default
Require user @SYSTEM
</Location>
<Location /admin/log>
AuthType Default
Require user @SYSTEM
Order allow,deny
</Location>
<Policy default>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Authenticate-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
# Only the owner or an administrator can cancel a job...
<Limit Cancel-Job>
Order deny,allow
Require user @OWNER @SYSTEM
</Limit>
</Policy>
<Policy authenticated>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
AuthType Default
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
<Policy kerberos>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
AuthType Negotiate
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Negotiate
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Negotiate
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
New contributor
I think I managed to reproduce this bug.
In my case, problems arose when I used system-config-printer tool to change one setting - preserving the printer jobs.
After that, the cupsd.conf was reduced to 22 bytes, and cupsd won't start. Replacing the faulty copsd.conf solved the starting of cupsd, but syste-config-tool (1.2.11-2ubuntu1) breakes it again when I try to change that setting on my ubunut 18.10 desktop.
On my system, the tool made cupsd.conf.0 file that was functional:
LogLevel warn
PageLogFormat
MaxLogSize 0
Port 631
Listen /run/cups/cups.sock
Browsing On
BrowseLocalProtocols dnssd
DefaultAuthType Basic
WebInterface Yes
<Location />
Order allow,deny
Allow all
</Location>
<Location /admin>
</Location>
<Location /admin/conf>
AuthType Default
Require user @SYSTEM
</Location>
<Location /admin/log>
AuthType Default
Require user @SYSTEM
Order allow,deny
</Location>
<Policy default>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Authenticate-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
# Only the owner or an administrator can cancel a job...
<Limit Cancel-Job>
Order deny,allow
Require user @OWNER @SYSTEM
</Limit>
</Policy>
<Policy authenticated>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
AuthType Default
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
<Policy kerberos>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
AuthType Negotiate
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Negotiate
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Negotiate
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
New contributor
New contributor
answered 12 mins ago
HrmeteohubHrmeteohub
1
1
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f846177%2fcups-wont-start%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown