Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #257808
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Date | 2023-05-01 19:30 +0200 |
| Message-ID | <GqFvz-5QAt-3@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <GqCxH-5ONn-5@gated-at.bofh.it> <GqDk5-5PjN-9@gated-at.bofh.it> <GqDDr-5Pq0-3@gated-at.bofh.it> <GqDWN-5PwD-3@gated-at.bofh.it> <GqEJc-5Q2l-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 5/1/23 12:30, Brian wrote: > On Mon 01 May 2023 at 11:39:29 -0400, gene heskett wrote: > >> On 5/1/23 11:28, Brian wrote: >>> On Mon 01 May 2023 at 11:02:58 -0400, gene heskett wrote: >>> >>>> On 5/1/23 10:40, Brian wrote: >>> >>> [...] >>> >>>>> Your printing situation appears to be a sane one, so now for a test. Do >>>>> >>>>> lp -d HLL2320D_coyote ANY_FILE_YOU_WANT >>>>> >>>> Is not working, shell appears frozen but eventually returns: >>>> gene@bpi51:~$ lp -d HLL2320D_coyote printer.cfg >>>> lp: The printer or class does not exist. >>> >>> But HLL2320D_coyote does exist. It is seen in the outputs of 'lpstat -l -e' >>> and 'sudo lpinfo -v'. Give >>> >>> lpoptopns -p HLL2320D_coyote >> gene@bpi51:~$ lpoptions -p HLL2320D_coyote >> device-uri=ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups >> printer-info='HLL2320D @ coyote' printer-make-and-model='Brother HL-L2320D >> series' printer-type=25202710 > > The print queue specified by -p is queried for some information about itself. > Its reponse is given and it seems a very reasonable one. > >>> lpoptions -p HLL2320D_coyote -l >> gene@bpi51:~$ lpoptions -p HLL2320D_coyote -l >> lpoptions: Unable to get PPD file for HLL2320D_coyote: The printer or class >> does not exist. > > The -l option asks the queue for the specific options it offers. The response > indicates something wrong with CUPS on bpi51. I haven't any problem when doing > this and getting sensible outputs on my Debian unstable machine. Which isn't quite a 1:1 comparison as that will be bookworm shortly. Or, should I update the bullseyes to unstable? IDK and I'm not even sure how... > Assuming your buster machines (which are working) have similar setups to bpi51, Which is a bullseye machine. And has a totally different content to the /etc/cups directory as shown by my last post, much more complex on the bullseye installs that don't work. > you couls try the two commands (and all the others in this thread) on one of > those. > I'd think I could start by comparing cupsd.conf's, but miss And I can't see the trees for all this forest in the way in both, but missing is a client.conf. I think... But that is probably whats wrong, me thinking. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
repeat of previous question that has gone unanswered several times. gene heskett <gheskett@shentel.net> - 2023-05-01 01:10 +0200
Re: repeat of previous question that has gone unanswered several times. Lee <ler762@gmail.com> - 2023-05-01 02:20 +0200
Re: repeat of previous question that has gone unanswered several times. gene heskett <gheskett@shentel.net> - 2023-05-01 09:40 +0200
Re: repeat of previous question that has gone unanswered several times. Brian <ad44@cityscape.co.uk> - 2023-05-01 15:00 +0200
Re: repeat of previous question that has gone unanswered severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 15:50 +0200
Re: repeat of previous question that has gone unanswered severaltimes. David Wright <deblis@lionunicorn.co.uk> - 2023-05-01 16:10 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 16:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 17:40 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 16:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 17:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 18:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 19:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 19:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-02 01:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 19:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 20:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. debian-user@howorth.org.uk - 2023-05-01 22:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 23:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 01:00 +0200
Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:30 +0200
Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 01:00 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Jeffrey Walton <noloader@gmail.com> - 2023-05-01 16:20 +0200
Re: repeat of previous question that has gone unanswered severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:00 +0200
Re: repeat of previous question that has gone unanswered several times. David Wright <deblis@lionunicorn.co.uk> - 2023-05-01 06:30 +0200
Re: repeat of previous question that has gone unanswered several times. john doe <johndoe65534@mail.com> - 2023-05-01 09:40 +0200
Re: repeat of previous question that has gone unanswered several times. <tomas@tuxteam.de> - 2023-05-01 13:50 +0200
Re: repeat of previous question that has gone unanswered several times. Brian <ad44@cityscape.co.uk> - 2023-05-01 15:00 +0200
Re: repeat of previous question that has gone unanswered several times. zithro <slack@rabbit.lu> - 2023-05-04 21:50 +0200
Re: repeat of previous question that has gone unanswered severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-04 22:00 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-05 16:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-05 17:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-05 19:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-05 22:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-06 01:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-06 03:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Alex King <alex@king.net.nz> - 2023-05-07 01:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. David <curmudgeon@telaman.net.au> - 2023-05-07 02:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Byung-Hee HWANG <soyeomul@doraji.xyz> - 2023-05-07 03:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2023-05-07 13:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-07 17:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-07 18:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 06:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-08 13:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 19:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 00:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 10:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-09 13:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 22:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 14:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 16:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. <tomas@tuxteam.de> - 2023-05-10 16:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 17:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 19:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 20:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 22:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 13:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-11 18:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 22:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. debian-user@howorth.org.uk - 2023-05-10 22:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 13:10 +0200
SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-11 18:10 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 21:20 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 00:00 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-12 00:30 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 01:50 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:40 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 11:20 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 12:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-12 13:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 13:50 +0200
Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 18:20 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 12:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 13:50 +0200
:Re: repeat of previous question thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 18:10 +0200
Re: :Re: repeat of previous question thathasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 23:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-12 20:50 +0200
Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 21:30 +0200
Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-13 13:20 +0200
Re: SOLVED:Re: repeat of previous questionthathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-13 17:10 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:30 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2023-05-07 19:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 07:10 +0200
csiph-web