No. Seems to be the option "-l" which causes systemd to shutdown cupsd
and to restart if a print job is available. For applications with pre-
checks for available printers or given printer names (for instance with
java javax.print.PrintServiceLookup) or with CUPS web Interface on
demand this does
I had the same problem in Ubuntu 16.04.1. After some testing I removed
all (3) printers and all cups-related packages and reinstalled them. And
now (without any additonal changes) all works fine. The only difference:
The first time I used a port forwarding to the remote print server like
"ssh -L
SRU fix for Xenial is simple. In the CUPS 2.1.3 used there the upstream
bug (https://github.com/apple/cups/issues/4755) is already fixed but it
seems that the removal of the workaround patch (auto-shutdown-on-idle-
also-with-webinterface-on.patch) got forgotten. So removing this patch
seems to be
Not having "ListenStream=631" in the systemd cups.socket file is
intended. See the answer from Mike Sweet, author of CUPS:
--
First, the reason why we don't include "ListenStream=631" is because that
exposes cupsd to remote attack. And we don't listen on localhost (which has a
similar
in my /etc/cups/client.conf (now /etc/cups/client.conf_bak) are two lines:
ServerName NameoftheremoteCUPSServer
ServerName localhost
The remote CUPS Server is running Version 1.5.3 and my client 2.0.2.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
edited /lib/systemd/system/cups.socket
restarted systemd and cups.
waiting for the bug to come back ...
--
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/1598300
Title:
cups
hi Till,
there is no client.* in /etc/cups
--
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/1598300
Title:
cups hang after a while
Status in cups package in Ubuntu:
What was in your /etc/cups/client.conf (now /etc/cups/client.conf_bak)?
If it pointed to a CUPS on a remote machine, all your CUPS access (from
applications/command line, not web interface) was directed to the remote
machine with a different CUPS setup. Now you are using always the CUPS
on your
I have done some tests and have found a solution. Please try it out.
Edit the file (with sudo):
/lib/systemd/system/cups.socket
adding a line
ListenStream=631
in the "[Socket]" section. The file should look like this then:
--
[Unit]
Description=CUPS Scheduler
[Socket]
Nice to see some progress, but the initial problem description and mine
is different from what has been discovered. The problem is not just the
webinterface, it is cups itself (or the scheduler) which goes inactive
and doesn't come back.
Today I was able to invest more time. On my system there
I tried now the following:
till@till-x1carbon:~/printing/cups/bzr/y$ sudo systemctl stop cups
Warning: Stopping cups.service, but it can still be activated by:
cups.socket
cups.path
till@till-x1carbon:~/printing/cups/bzr/y$ ps auxwww | grep cupsd
till 4265 0.0 0.0 14224 896 pts/19
First, xinetd is not needed. systemd handles running services on-demand
well.
Important to know is that there are two access methods for CUPS:
1. The domain socket file /var/run/cups/cups.sock
2. IP Port 631
CUPS can be configured to use one of these methods or both.
Both methods can be used
I posted an upstream feature request now to improve the web interface
for CUPS running on-demand. See
https://github.com/apple/cups/issues/4874.
** Bug watch added: github.com/apple/cups/issues #4874
https://github.com/apple/cups/issues/4874
--
You received this bug notification because you
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]
A little correction: 'sudo service cups restart' only solves the problem
for a short time, not necessarily till the next reboot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
The same for me:
● cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: ena
Active: inactive (dead) since Di 2016-08-30 08:42:33 CEST; 34min ago
Docs: man:cupsd(8)
Process: 11682 ExecStart=/usr/sbin/cupsd -l (code=exited,
Please follow the instructions of the section "CUPS error_log" on
https://wiki.ubuntu.com/DebuggingPrintingProblems. Thanks.
** Changed in: cups (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I have exactly the same thing on 16.04 LTS with the minimal virtual machine
install. I run the whole thing on ESXi 5.5 something.
Status:
root@printserver:/var/log/cups# service cups status
● cups.service - CUPS Scheduler
Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor
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.
19 matches
Mail list logo
