Discussion:
Bug#868316: cups-bsd: lpr does not print with "DefaultPolicy authenticated" in cupsd.conf
Add Reply
Christoph Pleger
2017-07-14 13:10:03 UTC
Reply
Permalink
Raw Message
Package: cups-bsd
Version: 2.2.1-8

Dear maintainers,

I do not know if it is a problem with the lpr program from cups-bsd or
with the cups daemon itself, but with "DefaultPolicy authenticated" in
cupsd.conf, lpr does not print, but the job remains in the print queue
for a while and then is removed.

Regards
Christoph
Brian Potkin
2017-07-14 16:00:02 UTC
Reply
Permalink
Raw Message
Thank you for your report, Christoph.
I do not know if it is a problem with the lpr program from cups-bsd or with
the cups daemon itself, but with "DefaultPolicy authenticated" in
cupsd.conf, lpr does not print, but the job remains in the print queue for a
while and then is removed.
You could try using lp to print but I cannot see that producing any
different an outcome.

We'll need an error_log; the Printing section of the wiki will guide
you in getting one. Compress it with gzip and send it to #868316.
Also attach your cupsd.conf and give the printer make and model.

Regards,

Brian.
Christoph Pleger
2017-07-17 08:20:01 UTC
Reply
Permalink
Raw Message
Hello,
Post by Brian Potkin
We'll need an error_log; the Printing section of the wiki will guide
you in getting one. Compress it with gzip and send it to #868316.
The log is attached. I stopped the cups daemon, removed the old
error_log, started the cups daemon, tried to print, and after the print
job had been removed from the queue, stopped the daemon. So, the log
contains only these steps.
Post by Brian Potkin
Also attach your cupsd.conf and give the printer make and model.
It is the original cupsd.conf copied from
/usr/share/cups/cupsd.conf.default at package installation, only with an
additional

DefaultPolicy authenticated

entry.

There are several printers, all of them remote printers imported by
cups-browsed - which is also currently broken related to authenticated
policy, see #868283, so that I installed an older version. Of course, I
verified that printing works with this older version of cups-browsed and
"DefaultPolicy default".

Regards
Christoph
Brian Potkin
2017-07-18 16:50:02 UTC
Reply
Permalink
Raw Message
Post by Christoph Pleger
Hello,
Post by Brian Potkin
We'll need an error_log; the Printing section of the wiki will guide
you in getting one. Compress it with gzip and send it to #868316.
The log is attached. I stopped the cups daemon, removed the old error_log,
started the cups daemon, tried to print, and after the print job had been
removed from the queue, stopped the daemon. So, the log contains only these
steps.
D [17/Jul/2017:09:55:22 +0200] [Client 63] 2.0 Send-Document 3
D [17/Jul/2017:09:55:22 +0200] Send-Document ipp://localhost:631/printers/nd50
D [17/Jul/2017:09:55:22 +0200] cupsdIsAuthorized: username=""
D [17/Jul/2017:09:55:22 +0200] [Client 63] Returning HTTP Nicht berechtigt for Send-Document (ipp://localhost:631/printers/nd50) from localhost

The username has an empty value, so sending the document is not
authorised. I have no idea why username is "".
Post by Christoph Pleger
Post by Brian Potkin
Also attach your cupsd.conf and give the printer make and model.
It is the original cupsd.conf copied from /usr/share/cups/cupsd.conf.default
at package installation, only with an additional
DefaultPolicy authenticated
entry.
There are several printers, all of them remote printers imported by
cups-browsed - which is also currently broken related to authenticated
policy, see #868283, so that I installed an older version. Of course, I
verified that printing works with this older version of cups-browsed and
"DefaultPolicy default".
I installed 1.10.0-1 and got printing with "DefaultPolicy default" but
none with "DefaultPolicy authenticated" - as happened to you. Then I
reverted to 1.11.6-3 and got no printing for either directive.

I wonder if this bug and #868283 have the same origin.

Regards,

Brian.

Loading...