On 2017-10-11 18:52, Brian Potkin <claremont...@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). $ lpstat -a lj400 accepting requests since Fri 13 Oct 2017 09:49:03 PM EDT [and many others listed] $ lpq lpq: Error - no default destination available. $ PRINTER=lj400 lpq lpq: Error - PRINTER environment variable names non-existent destination "lj400". $ lpq -Plj400 lj400 is ready no entries $ PRINTER=lj400 lp /etc/nsswitch.conf lp: Error - scheduler not responding. $ lpoptions -d lj400 [options displayed] $ lpq lpq: Error - no default destination available. $ PRINTER=xxx lpq lpq: Error - PRINTER environment variable names non-existent destination "xxx". $ lpq -Plj400 lj400 is ready no entries $ PRINTER=lj400 lp /etc/nsswitch.conf lp: Error - scheduler not responding.