Bug#1008175: #1008175
Brian:
PRINT_QUEUE_NAME is the actual name of the queue as given in Okular or
by 'lpstat -a'.
Sorry! Was out at a pub with a friend before responding! Should have
waited! ;^)
driverless
ipps://HP%20LaserJet%20Pro%20M148fdw%20(6CA573)._ipps._tcp.local/
As root:
lpadmin -p testq -v
"ipps://HP%20LaserJet%20Pro%20M148fdw%20(6CA573)._ipps._tcp.local/" -E
-m everywhere
as regular user:
lp -d testq -o sides=two-sided-long-edge lipsum.txt.pdf
Still printed single-sided
The printer was originally setup by the Debian netinst.
Thanks!
Rick
On 2022-03-27 17:01, Brian Potkin wrote:
On Sun 27 Mar 2022 at 15:13:30 -0500, r...@scotsgeek.com wrote:
Brian:
avahi-browse -rt _ipp._tcp
+ enp2s0 IPv6 HP LaserJet Pro M148fdw (6CA573) Internet
Printer
local
+ enp2s0 IPv4 HP LaserJet Pro M148fdw (6CA573) Internet
Printer
local
= enp2s0 IPv6 HP LaserJet Pro M148fdw (6CA573) Internet
Printer
local
hostname = [NPI6CA573.local]
address = [192.168.1.207]
port = [631]
txt = ["mopria-certified=1.3" "mac=f8:b4:6a:6c:a5:73" "usb_MDL=HP
LaserJet Pro M148f-M149f" "usb_MFG=HP" "TLS=1.2" "PaperMax=legal-A4"
"kind=document,envelope,photo"
"UUID=564e4733-5931-3235-3934-f8b46a6ca573"
"Fax=T" "Scan=T" "Duplex=T" "Color=F" "note=unitedStates"
"adminurl=http://NPI6CA573.local./hp/device/info_config_AirPrint.html?tab=Networking=AirPrintStatus;
The text record advertises that the printer is capable of automatic
duplex ("Duplex=T").
[Snipped text]
driverless
ipps://HP%20LaserJet%20Pro%20M148fdw%20(6CA573)._ipps._tcp.local/
ipp://... is a URI for the printer. We will try setting up and printing
to a new print queue. Do
lpadmin -p testq -v "URI" -E -m everywhere
Subdtitute URI with what is above. Test with
lp -d testq -o sides=two-sided-long-edge test.pdf
lpoptions -p PRINT_QUEUE_NAME -l
lpoptions: Unable to get PPD file for PRINT_QUEUE_NAME: No such file
or
directory
PRINT_QUEUE_NAME is the actual name of the queue as given in Okular or
by 'lpstat -a'.
Cheers,
Brian.
Bug#1008175: #1008175
On Sun 27 Mar 2022 at 15:13:30 -0500, r...@scotsgeek.com wrote:
> Brian:
>
> avahi-browse -rt _ipp._tcp
> + enp2s0 IPv6 HP LaserJet Pro M148fdw (6CA573) Internet Printer
> local
> + enp2s0 IPv4 HP LaserJet Pro M148fdw (6CA573) Internet Printer
> local
> = enp2s0 IPv6 HP LaserJet Pro M148fdw (6CA573) Internet Printer
> local
>hostname = [NPI6CA573.local]
>address = [192.168.1.207]
>port = [631]
>txt = ["mopria-certified=1.3" "mac=f8:b4:6a:6c:a5:73" "usb_MDL=HP
> LaserJet Pro M148f-M149f" "usb_MFG=HP" "TLS=1.2" "PaperMax=legal-A4"
> "kind=document,envelope,photo" "UUID=564e4733-5931-3235-3934-f8b46a6ca573"
> "Fax=T" "Scan=T" "Duplex=T" "Color=F" "note=unitedStates"
> "adminurl=http://NPI6CA573.local./hp/device/info_config_AirPrint.html?tab=Networking=AirPrintStatus;
The text record advertises that the printer is capable of automatic
duplex ("Duplex=T").
[Snipped text]
> driverless
> ipps://HP%20LaserJet%20Pro%20M148fdw%20(6CA573)._ipps._tcp.local/
ipp://... is a URI for the printer. We will try setting up and printing
to a new print queue. Do
lpadmin -p testq -v "URI" -E -m everywhere
Subdtitute URI with what is above. Test with
lp -d testq -o sides=two-sided-long-edge test.pdf
> lpoptions -p PRINT_QUEUE_NAME -l
> lpoptions: Unable to get PPD file for PRINT_QUEUE_NAME: No such file or
> directory
PRINT_QUEUE_NAME is the actual name of the queue as given in Okular or
by 'lpstat -a'.
Cheers,
Brian.
Bug#1008175: #1008175
Brian: avahi-browse -rt _ipp._tcp + enp2s0 IPv6 HP LaserJet Pro M148fdw (6CA573) Internet Printer local + enp2s0 IPv4 HP LaserJet Pro M148fdw (6CA573) Internet Printer local = enp2s0 IPv6 HP LaserJet Pro M148fdw (6CA573) Internet Printer local hostname = [NPI6CA573.local] address = [192.168.1.207] port = [631] txt = ["mopria-certified=1.3" "mac=f8:b4:6a:6c:a5:73" "usb_MDL=HP LaserJet Pro M148f-M149f" "usb_MFG=HP" "TLS=1.2" "PaperMax=legal-A4" "kind=document,envelope,photo" "UUID=564e4733-5931-3235-3934-f8b46a6ca573" "Fax=T" "Scan=T" "Duplex=T" "Color=F" "note=unitedStates" "adminurl=http://NPI6CA573.local./hp/device/info_config_AirPrint.html?tab=Networking=AirPrintStatus; "priority=10" "product=(HP LaserJet Pro M148f-M149f)" "ty=HP LaserJet Pro M148f-M149f" "URF=V1.4,CP99,W8,OB10,PQ3-4-5,DM1,IS1,MT1-3-5,RS600" "rfo=ipp/faxout" "rp=ipp/print" "pdl=image/urf,application/PCLm,application/octet-stream,application/pdf,application/postscript,application/vnd.hp-PCL,application/vnd.hp-PCLXL,image/jpeg" "qtotal=1" "txtvers=1"] = enp2s0 IPv4 HP LaserJet Pro M148fdw (6CA573) Internet Printer local hostname = [NPI6CA573.local] address = [192.168.1.207] port = [631] txt = ["mopria-certified=1.3" "mac=f8:b4:6a:6c:a5:73" "usb_MDL=HP LaserJet Pro M148f-M149f" "usb_MFG=HP" "TLS=1.2" "PaperMax=legal-A4" "kind=document,envelope,photo" "UUID=564e4733-5931-3235-3934-f8b46a6ca573" "Fax=T" "Scan=T" "Duplex=T" "Color=F" "note=unitedStates" "adminurl=http://NPI6CA573.local./hp/device/info_config_AirPrint.html?tab=Networking=AirPrintStatus; "priority=10" "product=(HP LaserJet Pro M148f-M149f)" "ty=HP LaserJet Pro M148f-M149f" "URF=V1.4,CP99,W8,OB10,PQ3-4-5,DM1,IS1,MT1-3-5,RS600" "rfo=ipp/faxout" "rp=ipp/print" "pdl=image/urf,application/PCLm,application/octet-stream,application/pdf,application/postscript,application/vnd.hp-PCL,application/vnd.hp-PCLXL,image/jpeg" "qtotal=1" "txtvers=1"] driverless ipps://HP%20LaserJet%20Pro%20M148fdw%20(6CA573)._ipps._tcp.local/ lpoptions -p PRINT_QUEUE_NAME -l lpoptions: Unable to get PPD file for PRINT_QUEUE_NAME: No such file or directory Thanks! Rick On 2022-03-27 12:49, Brian Potkin wrote: On Sun 27 Mar 2022 at 10:25:37 -0500, r...@scotsgeek.com wrote: The printer is"HP LaserJet Plus Pro M148fdw", connected by ethernet. I first created a .txt file, then converted it to a .ps file, then converted to a .pdf file. I then ran the following commands: lpr -o sides=two-sided-long-edge lipsum.txt.ps lp -o sides=two-sided-long-edge lipsum.txt.ps lpr -o sides=two-sided-long-edge lipsum.txt.pdf lp -o sides=two-sided-long-edge lipsum.txt.pdf All printed one-sided. Thanks for doing that. Then, as root, I ran the command cupsctl --debug-logging Then as regular user, I ran: lp -o sides=two-sided-long-edge lipsum.txt.pdf After many seconds, error reported: lp: Error - scheduler not responding. No output to the printer. Pass on this for the moment. My understanding is that there is no difference in what lp and lpr do. I then ran: lpr -o sides=two-sided-long-edge lipsum.txt.pdf It printed one-sided. This used to work correctly, then a few months ago, it stopped working. I had hoped it would have been corrected, but now I am reporting it. Please let me know if I can help in any other way. The error_log shows that two-sided-long-edge is sent to the printing system. See argv[5]. It should then be sent on to the printer. The printer supports two-sided-long-edge. But we have [Job 238] Unable to do two-sided printing, setting sides to \'one-sided\'. Now, where is that coming from and why? Investigating. Rick, you can help with more information. Please give what you get for avahi-browse -rt _ipp._tcp driverless lpoptions -p PRINT_QUEUE_NAME -l avahi-browse is in the avahi-utils package. Cheers, Brian.
Bug#1008175: #1008175
The log message "Unable to do two-sided printing" comes from the "ipp"
CUPS backend, part of CUPS. It seems that the backend does not find the
"sides" attribute in the printer's IPP attributes.
See the code here:
--
if (ipp_status == IPP_STATUS_OK_IGNORED_OR_SUBSTITUTED ||
ipp_status == IPP_STATUS
_OK_CONFLICTING)
{
/*
* One or more options are not supported...
*/
if (ippFindAttribute(response, "sides", IPP_TAG_ZERO))
{
/*
* The sides value is not supported, revert to one-sided as
needed...
*/
const char *sides = cupsGetOption("sides", num_options, options);
if (!sides || !strncmp(sides, "two-sided-", 10))
{
fputs("DEBUG: Unable to do two-sided printing, setting sides
to 'one-sided'.\n", stderr);
num_options = cupsAddOption("sides", "one-sided",
num_options, );
}
}
--
Bug#1008175: #1008175
On Sun 27 Mar 2022 at 10:25:37 -0500, r...@scotsgeek.com wrote: > The printer is"HP LaserJet Plus Pro M148fdw", connected by ethernet. > > I first created a .txt file, then converted it to a .ps file, then converted > to a .pdf file. I then ran the following commands: > lpr -o sides=two-sided-long-edge lipsum.txt.ps > lp -o sides=two-sided-long-edge lipsum.txt.ps > lpr -o sides=two-sided-long-edge lipsum.txt.pdf > lp -o sides=two-sided-long-edge lipsum.txt.pdf > > All printed one-sided. Thanks for doing that. > Then, as root, I ran the command > cupsctl --debug-logging > > Then as regular user, I ran: > lp -o sides=two-sided-long-edge lipsum.txt.pdf > > After many seconds, error reported: > lp: Error - scheduler not responding. > > No output to the printer. Pass on this for the moment. My understanding is that there is no difference in what lp and lpr do. > I then ran: > lpr -o sides=two-sided-long-edge lipsum.txt.pdf > > It printed one-sided. > > This used to work correctly, then a few months ago, it stopped working. I > had hoped it would have been corrected, but now I am reporting it. > > Please let me know if I can help in any other way. The error_log shows that two-sided-long-edge is sent to the printing system. See argv[5]. It should then be sent on to the printer. The printer supports two-sided-long-edge. But we have [Job 238] Unable to do two-sided printing, setting sides to \'one-sided\'. Now, where is that coming from and why? Investigating. Rick, you can help with more information. Please give what you get for avahi-browse -rt _ipp._tcp driverless lpoptions -p PRINT_QUEUE_NAME -l avahi-browse is in the avahi-utils package. Cheers, Brian.
Bug#1008175: #1008175
The printer is"HP LaserJet Plus Pro M148fdw", connected by ethernet. I first created a .txt file, then converted it to a .ps file, then converted to a .pdf file. I then ran the following commands: lpr -o sides=two-sided-long-edge lipsum.txt.ps lp -o sides=two-sided-long-edge lipsum.txt.ps lpr -o sides=two-sided-long-edge lipsum.txt.pdf lp -o sides=two-sided-long-edge lipsum.txt.pdf All printed one-sided. Then, as root, I ran the command cupsctl --debug-logging Then as regular user, I ran: lp -o sides=two-sided-long-edge lipsum.txt.pdf After many seconds, error reported: lp: Error - scheduler not responding. No output to the printer. I then ran: lpr -o sides=two-sided-long-edge lipsum.txt.pdf It printed one-sided. This used to work correctly, then a few months ago, it stopped working. I had hoped it would have been corrected, but now I am reporting it. Please let me know if I can help in any other way. Thank you! Rick On 2022-03-27 08:08, Brian Potkin wrote: tags 1008175 moreinfo thanks On Wed 23 Mar 2022 at 13:01:18 -0400, Rick Stanley wrote: Now neither option works correctly executing from the command line. "lpr -o sides=two-sided-long-edge test.pdf" "lpr -o sides=one-sided test.pdf" And same for lp. Thank you for your report, Rick. What is the printer make and model? The situation is that neither command gives double-sided printing? Printing from Okular works correctly as expected. There is a slight difference between your lp command and what Okular does. Okular sends a PostScript file to the ptinter. Not that I can see why that should make any difference, but printing from Evince or Firefox sens a PDF. You could try that. Anyway, let's have a log. Enable debug logging with cupsctl --debug-logging Empty error_log with >/var/log/cups/error_log Print and send error_log as an attachment after compressing it. Regards, Brian. error.7z Description: application/7z-compressed
Processed: Re: Bug#1008175: #1008175
Processing commands for cont...@bugs.debian.org: > tags 1008175 moreinfo Bug #1008175 [cups-bsd] cups-bsd: lp & lpr options sides=one-sided and sides=two-sided-long-edge are reversed. one-sided prints duplex (Two-sided) and vice-versa Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1008175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1008175: #1008175
tags 1008175 moreinfo thanks On Wed 23 Mar 2022 at 13:01:18 -0400, Rick Stanley wrote: > Now neither option works correctly executing from the command line. > "lpr -o sides=two-sided-long-edge test.pdf" > "lpr -o sides=one-sided test.pdf" > > And same for lp. Thank you for your report, Rick. What is the printer make and model? The situation is that neither command gives double-sided printing? > Printing from Okular works correctly as expected. There is a slight difference between your lp command and what Okular does. Okular sends a PostScript file to the ptinter. Not that I can see why that should make any difference, but printing from Evince or Firefox sens a PDF. You could try that. Anyway, let's have a log. Enable debug logging with cupsctl --debug-logging Empty error_log with >/var/log/cups/error_log Print and send error_log as an attachment after compressing it. Regards, Brian.
Bug#1008175: #1008175
Now neither option works correctly executing from the command line. "lpr -o sides=two-sided-long-edge test.pdf" "lpr -o sides=one-sided test.pdf" And same for lp. Printing from Okular works correctly as expected.
