Bug#877888: marked as done (cups-bsd: lpq and lp ignore the PRINTER environment variable)
Your message dated Sun, 15 Oct 2017 12:33:58 +0100
with message-id <15102017121908.9a484caa8c5b@desktop.copernicus.org.uk>
and subject line Re: Bug#877888: cups-bsd: lpq and lp ignore the PRINTER environment variable
has caused the Debian Bug report #877888,
regarding cups-bsd: lpq and lp ignore the PRINTER environment variable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
877888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877888
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cups-bsd
Version: 2.2.4-7
Severity: normal
File: /usr/bin/lpq
lpq and lp are no longer paying attention to the PRINTER environment
variable. (The cups(1) manpage says that PRINTER is used except for
setuid binaries. But lpq and lp are not setuid.)
Here is a commented log with lpq:
$ lpq
lj400 is ready /* my default destination */
no entries
$ PRINTER=mh371 printenv PRINTER
mh371 /* to show that the environment variable inherits */
$ PRINTER=mh371 lpq
lj400 is ready /* but lpq ignores it */
no entries
$ lpq -Pmh371
mh371 is ready /* to show that mh371 is a known destination */
no entries
And for lp:
$ PRINTER=mh371 lp /usr/share/hplip/data/ps/testpage.ps.gz
request id is lj400-2890 (1 file(s))
It went to the default destination despite the environment setting.
Here is my /etc/cups/lpoptions:
Default lj400 fitplot=true PageSize=Letter sides=two-sided-long-edge
Dest lj400/gs fitplot=true PageSize=Letter pdftops-renderer=gs sides=two-sided-long-edge
Dest mh235 fitplot=true PageSize=Letter sides=two-sided-long-edge
Dest mh271 fitplot=true PageSize=Letter sides=two-sided-long-edge
Dest mh271/duplex fitplot=true PageSize=Letter sides=two-sided-long-edge
Dest mh271/saver fitplot=true number-up=2 PageSize=Letter sides=two-sided-long-edge
Dest mh371 PageSize=Letter sides=two-sided-long-edge
Dest mitx duplex=duplexnotumble
Dest psc outputorder=reverse PageSize=Letter PrintoutMode=High
-Sanjoy
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages cups-bsd depends on:
ii cups-client 2.2.4-7
ii cups-common 2.2.4-7
ii debconf 1.5.63
ii libc6 2.24-17
ii libcups2 2.2.4-7
cups-bsd recommends no packages.
Versions of packages cups-bsd suggests:
ii cups 2.2.4-7
ii update-inetd 4.44
-- debconf information:
cups-bsd/setuplpd: false
--
--- End Message ---
--- Begin Message ---
On Fri 13 Oct 2017 at 22:29:14 -0400, Sanjoy Mahajan wrote:
> On 2017-10-11 18:52, Brian Potkin <claremont102@gmail.com> wrote:
>
> > When it came to unstable (only /etc/cups/lpoptions existing) I obtained
> > the same as you did.
> >
> > It would be good if you would test some of my observations and report
> > before the bug is forwarded upstream.
>
> Brian,
>
> I've reproduced your results. Below is the log. The only difference
> from yours is that my usual printer is called lj400 instead of pcl. All
> tests were run as a regular user starting from no /etc/cups/lpoptions or
> ~/.cups/lpoptions (restarting cups after moving /etc/cups/lpoptions to
> /etc/cups/lpoptions.bak, just in case).
Thanks for doing that. As it happens, cups 2.2.5 is now in unstable so I
re-tested. None of the issues we both observed appear to be present in
this version. I have not looked closely to find the cause of the fix but
it is a good note on which to close this report.
Cheers,
Brian.
--- End Message ---
Reply to: