Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #257755 > unrolled thread
| Started by | gene heskett <gheskett@shentel.net> |
|---|---|
| First post | 2023-05-01 01:10 +0200 |
| Last post | 2023-05-08 07:10 +0200 |
| Articles | 20 on this page of 89 — 15 participants |
Back to article view | Back to linux.debian.user
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
Page 1 of 5 [1] 2 3 4 5 Next page →
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-01 01:10 +0200 |
| Subject | repeat of previous question that has gone unanswered several times. |
| Message-ID | <Gqol3-5FqD-1@gated-at.bofh.it> |
Greetings all; I have a mixed home network, some buster, some bullseye, all up to date a/o yesterday. I have 2 printers shared on this bullseye main box, available as 5 or 6 printers, each configured in cups to do a specific job. Good printers, both running on brother's own linux drivers for that printer. All my buster machines can use both of these printers just as if they were plugged into that machine, but a machine shop full of sawdust and metal shavings is not a good printer environment, even if there was room for them, which there isn't. All of my bullseye machines are locked out, printer screen at localhost:631 is empty, and no printers can be found and added. But open a shell, and type "lpstat -t" and it gets the full list of available printers on that same bullseye machine whose cups output is empty. Why? Thank you for any insight. 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/>
[toc] | [next] | [standalone]
| From | Lee <ler762@gmail.com> |
|---|---|
| Date | 2023-05-01 02:20 +0200 |
| Message-ID | <GqpqN-5G2p-5@gated-at.bofh.it> |
| In reply to | #257755 |
On 4/30/23, gene heskett <gheskett@shentel.net> wrote: > Greetings all; > > I have a mixed home network, some buster, some bullseye, all up to date > a/o yesterday. > > I have 2 printers shared on this bullseye main box, available as 5 or 6 > printers, each configured in cups to do a specific job. Good printers, > both running on brother's own linux drivers for that printer. > > All my buster machines can use both of these printers just as if they > were plugged into that machine, but a machine shop full of sawdust and > metal shavings is not a good printer environment, even if there was room > for them, which there isn't. > > All of my bullseye machines are locked out, printer screen at > localhost:631 is empty, and no printers can be found and added. > > But open a shell, and type "lpstat -t" and it gets the full list of > available printers on that same bullseye machine whose cups output is > empty. > > Why? Take a look at https://wiki.debian.org/CUPSQuickPrintQueues The quick ref is to install avahi-utils and run avahi-browse -rt _ipp._tcp | grep URF If you get a line matching URF the printer supports the AirPrint service. Install cups and see if it works (which is all that I needed to do to get the printer working). If no, what does avahi-browse -rt _ipp._tcp and systemctl status avahi-daemon show you? Regards, Lee
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-01 09:40 +0200 |
| Subject | Re: repeat of previous question that has gone unanswered several times. |
| Message-ID | <GqwiB-5Kit-1@gated-at.bofh.it> |
| In reply to | #257757 |
On 4/30/23 20:19, Lee wrote:
> On 4/30/23, gene heskett <gheskett@shentel.net> wrote:
>> Greetings all;
>>
>> I have a mixed home network, some buster, some bullseye, all up to date
>> a/o yesterday.
>>
>> I have 2 printers shared on this bullseye main box, available as 5 or 6
>> printers, each configured in cups to do a specific job. Good printers,
>> both running on brother's own linux drivers for that printer.
>>
>> All my buster machines can use both of these printers just as if they
>> were plugged into that machine, but a machine shop full of sawdust and
>> metal shavings is not a good printer environment, even if there was room
>> for them, which there isn't.
>>
>> All of my bullseye machines are locked out, printer screen at
>> localhost:631 is empty, and no printers can be found and added.
>>
>> But open a shell, and type "lpstat -t" and it gets the full list of
>> available printers on that same bullseye machine whose cups output is
>> empty.
>>
>> Why?
>
> Take a look at
> https://wiki.debian.org/CUPSQuickPrintQueues
>
> The quick ref is to install avahi-utils and run
> avahi-browse -rt _ipp._tcp | grep URF
>
had to install it, pulled in 7 other pkgs: then:
gene@bpi51:~$ avahi-browse -rt _ipp._tcp | grep URF
txt = ["printer-type=0x80300E" "printer-state=3" "Color=T" "TLS=1.2"
"UUID=831942b6-acfd-3e55-7013-00336f687aa2" "URF=DM3"
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf"
"product=(MFC-J6920DW)" "priority=0" "note=letss see if this works"
"adminurl=https://coyote.local.:631/printers/Brother_MFC-J6920DW_photo"
"ty=Brother MFC-J6920DW CUPS" "rp=printers/Brother_MFC-J6920DW_photo"
"qtotal=1" "txtvers=1"]
txt = ["printer-type=0x80300E" "printer-state=3" "Color=T" "TLS=1.2"
"UUID=58daf55b-1dc3-31b0-7442-4a936bde800c" "URF=DM3"
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf"
"product=(MFC-J6920DW)" "priority=0" "note=coyote.den duplex bottom
tray" "adminurl=https://coyote.local.:631/printers/MFCJ6920DW"
"ty=Brother MFC-J6920DW CUPS" "rp=printers/MFCJ6920DW" "qtotal=1"
"txtvers=1"]
txt = ["printer-type=0x809016" "printer-state=3" "Duplex=T"
"TLS=1.2" "UUID=36139eb5-df51-332f-4f80-ebf162ecc0ae" "URF=DM3"
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf"
"product=(Brother HL-L2320D series)" "priority=0"
"adminurl=https://coyote.local.:631/printers/HLL2320D" "ty=Brother
HL-L2320D for CUPS" "rp=printers/HLL2320D" "qtotal=1" "txtvers=1"]
txt = ["printer-type=0x809016" "printer-state=3" "Duplex=T"
"TLS=1.2" "UUID=391b5af9-9bac-3249-65f0-795f553651fe" "URF=DM3"
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf"
"product=(Brother HL-L2320D series)" "priority=0" "note=floor in den"
"adminurl=https://coyote.local.:631/printers/Brother_HL-L2320D_series"
"ty=Brother HL-L2320D for CUPS" "rp=printers/Brother_HL-L2320D_series"
"qtotal=1" "txtvers=1"]
> If you get a line matching URF the printer supports the AirPrint
> service. Install cups and see if it works (which is all that I needed
> to do to get the printer working). If no, what does
>
cups already installed as part of armbian
> avahi-browse -rt _ipp._tcp
gene@bpi51:~$ avahi-browse -rt _ipp._tcp
+ eth0 IPv4 Brother HL-L2320D series @ coyote Internet
Printer local
+ eth0 IPv4 Brother MFC-J6920DW @ coyote Internet
Printer local
+ eth0 IPv4 HLL2320D @ coyote Internet
Printer local
+ eth0 IPv4 MFCJ6920DW _tray_2 @ coyote Internet
Printer local
= eth0 IPv4 Brother HL-L2320D series @ coyote Internet
Printer local
hostname = [coyote.local]
address = [192.168.71.3]
port = [631]
txt = ["printer-type=0x809016" "printer-state=3" "Duplex=T"
"TLS=1.2" "UUID=391b5af9-9bac-3249-65f0-795f553651fe" "URF=DM3"
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf"
"product=(Brother HL-L2320D series)" "priority=0" "note=floor in den"
"adminurl=https://coyote.local.:631/printers/Brother_HL-L2320D_series"
"ty=Brother HL-L2320D for CUPS" "rp=printers/Brother_HL-L2320D_series"
"qtotal=1" "txtvers=1"]
= eth0 IPv4 Brother MFC-J6920DW @ coyote Internet
Printer local
hostname = [coyote.local]
address = [192.168.71.3]
port = [631]
txt = ["printer-type=0x80300E" "printer-state=3" "Color=T" "TLS=1.2"
"UUID=831942b6-acfd-3e55-7013-00336f687aa2" "URF=DM3"
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf"
"product=(MFC-J6920DW)" "priority=0" "note=letss see if this works"
"adminurl=https://coyote.local.:631/printers/Brother_MFC-J6920DW_photo"
"ty=Brother MFC-J6920DW CUPS" "rp=printers/Brother_MFC-J6920DW_photo"
"qtotal=1" "txtvers=1"]
= eth0 IPv4 HLL2320D @ coyote Internet
Printer local
hostname = [coyote.local]
address = [192.168.71.3]
port = [631]
txt = ["printer-type=0x809016" "printer-state=3" "Duplex=T"
"TLS=1.2" "UUID=36139eb5-df51-332f-4f80-ebf162ecc0ae" "URF=DM3"
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf"
"product=(Brother HL-L2320D series)" "priority=0"
"adminurl=https://coyote.local.:631/printers/HLL2320D" "ty=Brother
HL-L2320D for CUPS" "rp=printers/HLL2320D" "qtotal=1" "txtvers=1"]
= eth0 IPv4 MFCJ6920DW _tray_2 @ coyote Internet
Printer local
hostname = [coyote.local]
address = [192.168.71.3]
port = [631]
txt = ["printer-type=0x80300E" "printer-state=3" "Color=T" "TLS=1.2"
"UUID=58daf55b-1dc3-31b0-7442-4a936bde800c" "URF=DM3"
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf"
"product=(MFC-J6920DW)" "priority=0" "note=coyote.den duplex bottom
tray" "adminurl=https://coyote.local.:631/printers/MFCJ
>
> and
>
> systemctl status avahi-daemon
>
> show you?
>
gene@bpi51:~$ systemctl status avahi-daemon
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled;
vendor preset: enabled)
Active: active (running) since Mon 2023-05-01 02:13:38 -05; 11min ago
TriggeredBy: ● avahi-daemon.socket
Main PID: 5081 (avahi-daemon)
Status: "avahi-daemon 0.8 starting up."
Tasks: 2 (limit: 4207)
Memory: 788.0K
CPU: 166ms
CGroup: /system.slice/avahi-daemon.service
├─5081 avahi-daemon: running [bpi51.local]
└─5083 avahi-daemon: chroot helper
May 01 02:13:38 bpi51 avahi-daemon[5081]: No service file found in
/etc/avahi/services.
May 01 02:13:38 bpi51 avahi-daemon[5081]: *** WARNING: Detected another
IPv4 mDNS stack running on this host. This makes mDNS unreliable and is
thus not>
May 01 02:13:38 bpi51 avahi-daemon[5081]: Joining mDNS multicast group
on interface eth0.IPv4 with address 192.168.71.9.
May 01 02:13:38 bpi51 avahi-daemon[5081]: New relevant interface
eth0.IPv4 for mDNS.
May 01 02:13:38 bpi51 avahi-daemon[5081]: Joining mDNS multicast group
on interface lo.IPv4 with address 127.0.0.1.
May 01 02:13:38 bpi51 avahi-daemon[5081]: New relevant interface lo.IPv4
for mDNS.
May 01 02:13:38 bpi51 avahi-daemon[5081]: Network interface enumeration
completed.
May 01 02:13:38 bpi51 avahi-daemon[5081]: Registering new address record
for 192.168.71.9 on eth0.IPv4.
May 01 02:13:38 bpi51 avahi-daemon[5081]: Registering new address record
for 127.0.0.1 on lo.IPv4.
May 01 02:13:39 bpi51 avahi-daemon[5081]: Server startup complete. Host
name is bpi51.local. Local service cookie is 4247089512.
Went to machine, ff already running for octoprint tab opened to
localhost:631, no printers for a printer search.
So cups still cannot see the shares but only for a bullseye install,
buster installs work just fine.
??
Thanks Lee.
> Regards,
> Lee
> .
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/>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-01 15:00 +0200 |
| Subject | Re: repeat of previous question that has gone unanswered several times. |
| Message-ID | <GqBii-5NSo-7@gated-at.bofh.it> |
| In reply to | #257768 |
On Mon 01 May 2023 at 03:29:28 -0400, gene heskett wrote: > > avahi-browse -rt _ipp._tcp > gene@bpi51:~$ avahi-browse -rt _ipp._tcp > + eth0 IPv4 Brother HL-L2320D series @ coyote Internet Printer > local > + eth0 IPv4 Brother MFC-J6920DW @ coyote Internet Printer > local > + eth0 IPv4 HLL2320D @ coyote Internet Printer > local > + eth0 IPv4 MFCJ6920DW _tray_2 @ coyote Internet Printer > local You have exactly four (not five or six) print queues manually set up on the CUPS server coyote (192.168.71.3). It is assumed that when sat at coyote it is possible to print to any of Brother HL-L2320D series, Brother MFC-J6920DW, HLL2320D and MFCJ6920DW _tray_2. Im particular - can you print to HLL2320D from the server? [...] > = eth0 IPv4 HLL2320D @ coyote Internet Printer > local > hostname = [coyote.local] > address = [192.168.71.3] > port = [631] > txt = ["printer-type=0x809016" "printer-state=3" "Duplex=T" "TLS=1.2" > "UUID=36139eb5-df51-332f-4f80-ebf162ecc0ae" "URF=DM3" "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf" > "product=(Brother HL-L2320D series)" "priority=0" > "adminurl=https://coyote.local.:631/printers/HLL2320D" "ty=Brother HL-L2320D > for CUPS" "rp=printers/HLL2320D" "qtotal=1" "txtvers=1"] As well as three other printers, the host bpi51 sees the shared HLL2320D @ coyote queue via mDNS/DNS-SD. All is well and good up to now. Let's have lpstat -l -e lpstat -a lpinfo -v from bpi51. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-01 15:50 +0200 |
| Subject | Re: repeat of previous question that has gone unanswered severaltimes. |
| Message-ID | <GqC4F-5OnQ-3@gated-at.bofh.it> |
| In reply to | #257783 |
On 5/1/23 08:56, Brian wrote: > On Mon 01 May 2023 at 03:29:28 -0400, gene heskett wrote: > >>> avahi-browse -rt _ipp._tcp >> gene@bpi51:~$ avahi-browse -rt _ipp._tcp >> + eth0 IPv4 Brother HL-L2320D series @ coyote Internet Printer >> local >> + eth0 IPv4 Brother MFC-J6920DW @ coyote Internet Printer >> local >> + eth0 IPv4 HLL2320D @ coyote Internet Printer >> local >> + eth0 IPv4 MFCJ6920DW _tray_2 @ coyote Internet Printer >> local > > You have exactly four (not five or six) print queues manually set up on > the CUPS server coyote (192.168.71.3). It is assumed that when sat at > coyote it is possible to print to any of Brother HL-L2320D series, Brother > MFC-J6920DW, HLL2320D and MFCJ6920DW _tray_2. Im particular - can you > print to HLL2320D from the server? > Yes, and from any buster machine on my local network. > [...] > >> = eth0 IPv4 HLL2320D @ coyote Internet Printer >> local >> hostname = [coyote.local] >> address = [192.168.71.3] >> port = [631] >> txt = ["printer-type=0x809016" "printer-state=3" "Duplex=T" "TLS=1.2" >> "UUID=36139eb5-df51-332f-4f80-ebf162ecc0ae" "URF=DM3" "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/pwg-raster,image/urf" >> "product=(Brother HL-L2320D series)" "priority=0" >> "adminurl=https://coyote.local.:631/printers/HLL2320D" "ty=Brother HL-L2320D >> for CUPS" "rp=printers/HLL2320D" "qtotal=1" "txtvers=1"] > > As well as three other printers, the host bpi51 sees the shared HLL2320D @ coyote > queue via mDNS/DNS-SD. All is well and good up to now. Let's have > > lpstat -l -e gene@bpi51:~$ lpstat -l -e Brother_HL_L2320D_series_coyote network none ipps://Brother%20HL-L2320D%20series%20%40%20coyote._ipps._tcp.local/cups Brother_MFC_J6920DW_coyote network none ipps://Brother%20MFC-J6920DW%20%40%20coyote._ipps._tcp.local/cups HLL2320D_coyote network none ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups MFCJ6920DW_tray_2_coyote network none ipps://MFCJ6920DW%20_tray_2%20%40%20coyote._ipps._tcp.local/cups PDF permanent ipp://localhost/printers/PDF cups-pdf:/ > lpstat -a gene@bpi51:~$ lpstat -a PDF accepting requests since Fri 02 Dec 2022 11:13:10 PM -05 > lpinfo -v gene@bpi51:~$ lpinfo -v -bash: lpinfo: command not found gene@bpi51:~$ sudo apt install lpinfo Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package lpinfo > > from bpi51. > Thank you Brian Take care and stay well. 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/>
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2023-05-01 16:10 +0200 |
| Subject | Re: repeat of previous question that has gone unanswered severaltimes. |
| Message-ID | <GqCo1-5OK3-11@gated-at.bofh.it> |
| In reply to | #257786 |
On Mon 01 May 2023 at 09:39:51 (-0400), gene heskett wrote: > > lpinfo -v > gene@bpi51:~$ lpinfo -v > -bash: lpinfo: command not found > gene@bpi51:~$ sudo apt install lpinfo > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > E: Unable to locate package lpinfo You need root: # lpinfo -v network beh network lpd file cups-brf:/ network socket network ipps network https network ipp network http file cups-pdf:/ network dnssd://Brother%20HL-L2390DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-90324b75e771 network ipp://Brother%20HL-L2390DW._ipp._tcp.local/ network lpd://BRW90324B75E771/BINARY_P1 # Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-01 16:40 +0200 |
| Subject | Re: repeat of previous question that has gone unanswered severaltimes. |
| Message-ID | <GqCR3-5OU3-1@gated-at.bofh.it> |
| In reply to | #257787 |
On Mon 01 May 2023 at 09:07:53 -0500, David Wright wrote: > On Mon 01 May 2023 at 09:39:51 (-0400), gene heskett wrote: > > > lpinfo -v > > gene@bpi51:~$ lpinfo -v > > -bash: lpinfo: command not found > > gene@bpi51:~$ sudo apt install lpinfo > > Reading package lists... Done > > Building dependency tree... Done > > Reading state information... Done > > E: Unable to locate package lpinfo > > You need root: > > # lpinfo -v > network beh > network lpd > file cups-brf:/ > network socket > network ipps > network https > network ipp > network http > file cups-pdf:/ > network dnssd://Brother%20HL-L2390DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-90324b75e771 > network ipp://Brother%20HL-L2390DW._ipp._tcp.local/ > network lpd://BRW90324B75E771/BINARY_P1 Indeed you do. I forgot that root privilege is required because the USB bus is probed. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-01 17:00 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqDap-5P0Y-11@gated-at.bofh.it> |
| In reply to | #257787 |
On 5/1/23 10:08, David Wright wrote: > On Mon 01 May 2023 at 09:39:51 (-0400), gene heskett wrote: >>> lpinfo -v >> gene@bpi51:~$ lpinfo -v >> -bash: lpinfo: command not found >> gene@bpi51:~$ sudo apt install lpinfo >> Reading package lists... Done >> Building dependency tree... Done >> Reading state information... Done >> E: Unable to locate package lpinfo > > You need root: > > # lpinfo -v > network beh > network lpd > file cups-brf:/ > network socket > network ipps > network https > network ipp > network http > file cups-pdf:/ > network dnssd://Brother%20HL-L2390DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-90324b75e771 > network ipp://Brother%20HL-L2390DW._ipp._tcp.local/ > network lpd://BRW90324B75E771/BINARY_P1 > # > > Cheers, > David. > > . Ah so gene@bpi51:~$ sudo lpinfo -v [sudo] password for gene: Sorry, try again. [sudo] password for gene: network beh network socket network http network ipps network lpd network https network ipp file cups-brf:/ file cups-pdf:/ network dnssd://Brother%20HL-L2320D%20series%20%40%20coyote._ipp._tcp.local/cups?uuid=391b5af9-9bac-3249-65f0-795f553651fe network dnssd://Brother%20MFC-J6920DW%20%40%20coyote._ipp._tcp.local/cups?uuid=831942b6-acfd-3e55-7013-00336f687aa2 network dnssd://HLL2320D%20%40%20coyote._ipp._tcp.local/cups?uuid=36139eb5-df51-332f-4f80-ebf162ecc0ae network dnssd://MFCJ6920DW%20_tray_2%20%40%20coyote._ipp._tcp.local/cups?uuid=58daf55b-1dc3-31b0-7442-4a936bde800c Thats better, but does it show "why" 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/>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-01 17:40 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqDN7-5Pta-1@gated-at.bofh.it> |
| In reply to | #257795 |
On Mon 01 May 2023 at 10:56:00 -0400, gene heskett wrote: > On 5/1/23 10:08, David Wright wrote: > > On Mon 01 May 2023 at 09:39:51 (-0400), gene heskett wrote: > > > > lpinfo -v > > > gene@bpi51:~$ lpinfo -v > > > -bash: lpinfo: command not found > > > gene@bpi51:~$ sudo apt install lpinfo > > > Reading package lists... Done > > > Building dependency tree... Done > > > Reading state information... Done > > > E: Unable to locate package lpinfo > > > > You need root: > > > > # lpinfo -v > > network beh > > network lpd > > file cups-brf:/ > > network socket > > network ipps > > network https > > network ipp > > network http > > file cups-pdf:/ > > network dnssd://Brother%20HL-L2390DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-90324b75e771 > > network ipp://Brother%20HL-L2390DW._ipp._tcp.local/ > > network lpd://BRW90324B75E771/BINARY_P1 > > # > > > > Cheers, > > David. > > > > . > Ah so > gene@bpi51:~$ sudo lpinfo -v > [sudo] password for gene: > Sorry, try again. > [sudo] password for gene: > network beh > network socket > network http > network ipps > network lpd > network https > network ipp > file cups-brf:/ > file cups-pdf:/ > network dnssd://Brother%20HL-L2320D%20series%20%40%20coyote._ipp._tcp.local/cups?uuid=391b5af9-9bac-3249-65f0-795f553651fe > network dnssd://Brother%20MFC-J6920DW%20%40%20coyote._ipp._tcp.local/cups?uuid=831942b6-acfd-3e55-7013-00336f687aa2 > network dnssd://HLL2320D%20%40%20coyote._ipp._tcp.local/cups?uuid=36139eb5-df51-332f-4f80-ebf162ecc0ae > network dnssd://MFCJ6920DW%20_tray_2%20%40%20coyote._ipp._tcp.local/cups?uuid=58daf55b-1dc3-31b0-7442-4a936bde800c > > Thats better, but does it show "why" THe network is probed and the dnssd backend of CUPS find the same four printers as 'lpsta -l -e' does. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-01 16:20 +0200 |
| Subject | Re: repeat of previous question that has gone unanswered severaltimes. |
| Message-ID | <GqCxH-5ONn-5@gated-at.bofh.it> |
| In reply to | #257786 |
On Mon 01 May 2023 at 09:39:51 -0400, gene heskett wrote: > gene@bpi51:~$ lpstat -l -e > Brother_HL_L2320D_series_coyote network none > ipps://Brother%20HL-L2320D%20series%20%40%20coyote._ipps._tcp.local/cups > > Brother_MFC_J6920DW_coyote network none > ipps://Brother%20MFC-J6920DW%20%40%20coyote._ipps._tcp.local/cups > > HLL2320D_coyote network none > ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups > > MFCJ6920DW_tray_2_coyote network none > ipps://MFCJ6920DW%20_tray_2%20%40%20coyote._ipps._tcp.local/cups There you are! CUPS sees all four print queues shared by coyote. At this stage we are golden. Note that all four are designated as "network". > PDF permanent ipp://localhost/printers/PDF cups-pdf:/ This is a manual queue (permanent) set up locally on bpi51. It isn't of any further interest. > gene@bpi51:~$ lpstat -a > PDF accepting requests since Fri 02 Dec 2022 11:13:10 PM -05 You may care to take note that 'lpstat -a' and 'lpstat -t' only show local printers (permanent) and not those that are on the network. That also goes for the Printers section at localhost:631. Local printers can also be auto-setup by cups-browsed. You do not have it installed/running. Thar's OK; there isn't any obligation (or for that matter, any need) to use it. Having mentioned it, we will now completely put it out of our minds. > gene@bpi51:~$ lpinfo -v > -bash: lpinfo: command not found sudo lpinfo -v Your printing situation appears to be a sane one, so now for a test. Do lp -d HLL2320D_coyote ANY_FILE_YOU_WANT -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-01 17:10 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqDk5-5PjN-9@gated-at.bofh.it> |
| In reply to | #257788 |
On 5/1/23 10:40, Brian wrote: > On Mon 01 May 2023 at 09:39:51 -0400, gene heskett wrote: > >> gene@bpi51:~$ lpstat -l -e >> Brother_HL_L2320D_series_coyote network none >> ipps://Brother%20HL-L2320D%20series%20%40%20coyote._ipps._tcp.local/cups >> >> Brother_MFC_J6920DW_coyote network none >> ipps://Brother%20MFC-J6920DW%20%40%20coyote._ipps._tcp.local/cups >> >> HLL2320D_coyote network none >> ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups >> >> MFCJ6920DW_tray_2_coyote network none >> ipps://MFCJ6920DW%20_tray_2%20%40%20coyote._ipps._tcp.local/cups > > There you are! CUPS sees all four print queues shared by coyote. At this > stage we are golden. Note that all four are designated as "network". > >> PDF permanent ipp://localhost/printers/PDF cups-pdf:/ > > This is a manual queue (permanent) set up locally on bpi51. It isn't of any > further interest. > >> gene@bpi51:~$ lpstat -a >> PDF accepting requests since Fri 02 Dec 2022 11:13:10 PM -05 > > You may care to take note that 'lpstat -a' and 'lpstat -t' only show local > printers (permanent) and not those that are on the network. That also goes > for the Printers section at localhost:631. > > Local printers can also be auto-setup by cups-browsed. You do not have it > installed/running. Thar's OK; there isn't any obligation (or for that matter, > any need) to use it. Having mentioned it, we will now completely put it out > of our minds. > >> gene@bpi51:~$ lpinfo -v >> -bash: lpinfo: command not found > > sudo lpinfo -v > > 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. 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/>
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-01 17:20 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqDtL-5PmX-3@gated-at.bofh.it> |
| In reply to | #257797 |
On 5/1/23 11:03, gene heskett wrote: > On 5/1/23 10:40, Brian wrote: >> On Mon 01 May 2023 at 09:39:51 -0400, gene heskett wrote: >> >>> gene@bpi51:~$ lpstat -l -e >>> Brother_HL_L2320D_series_coyote network none >>> ipps://Brother%20HL-L2320D%20series%20%40%20coyote._ipps._tcp.local/cups >>> >>> Brother_MFC_J6920DW_coyote network none >>> ipps://Brother%20MFC-J6920DW%20%40%20coyote._ipps._tcp.local/cups >>> >>> HLL2320D_coyote network none >>> ipps://HLL2320D%20%40%20coyote._ipps._tcp.local/cups >>> >>> MFCJ6920DW_tray_2_coyote network none >>> ipps://MFCJ6920DW%20_tray_2%20%40%20coyote._ipps._tcp.local/cups >> >> There you are! CUPS sees all four print queues shared by coyote. At this >> stage we are golden. Note that all four are designated as "network". >> >>> PDF permanent ipp://localhost/printers/PDF cups-pdf:/ >> >> This is a manual queue (permanent) set up locally on bpi51. It isn't >> of any >> further interest. >> >>> gene@bpi51:~$ lpstat -a >>> PDF accepting requests since Fri 02 Dec 2022 11:13:10 PM -05 >> >> You may care to take note that 'lpstat -a' and 'lpstat -t' only show >> local >> printers (permanent) and not those that are on the network. That also >> goes >> for the Printers section at localhost:631. >> >> Local printers can also be auto-setup by cups-browsed. You do not have it >> installed/running. Thar's OK; there isn't any obligation (or for that >> matter, >> any need) to use it. Having mentioned it, we will now completely put >> it out >> of our minds. >>> gene@bpi51:~$ lpinfo -v >>> -bash: lpinfo: command not found >> >> sudo lpinfo -v >> >> 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. > > repeat same error if s sudo is put in front of it. > Cheers, Gene Heskett. 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/>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-01 17:30 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqDDr-5Pq0-3@gated-at.bofh.it> |
| In reply to | #257797 |
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 lpoptions -p HLL2320D_coyote -l -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-01 17:50 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqDWN-5PwD-3@gated-at.bofh.it> |
| In reply to | #257799 |
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 > 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. > 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/>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-01 18:40 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqEJc-5Q2l-13@gated-at.bofh.it> |
| In reply to | #257801 |
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. Assuming your buster machines (which are working) have similar setups to bpi51, you couls try the two commands (and all the others in this thread) on one of those. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-01 19:10 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqFcd-5Qrw-7@gated-at.bofh.it> |
| In reply to | #257805 |
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. > > Assuming your buster machines (which are working) have similar setups to bpi51, > you couls try the two commands (and all the others in this thread) on one of > those. > one of those machines reports this for the -l option: gene@sixty40:~$ lpoptions -p HLL2320D_coyote -l PageSize/Media Size: Custom.WIDTHxHEIGHT *Letter Legal Executive FanFoldGermanLegal A4 A5 A6 Env10 EnvMonarch EnvDL EnvC5 ISOB5 B5 ISOB6 B6 4x6 Postcard DoublePostcardRotated EnvYou4 195x270mm 184x260mm 197x273mm CUSTOM1 CUSTOM2 CUSTOM3 BrMediaType/MediaType: *PLAIN THIN THICK THICKERPAPER2 BOND ENV ENVTHICK ENVTHIN RECYCLED InputSlot/InputSlot: MANUAL *TRAY1 Duplex/Duplex: DuplexTumble *DuplexNoTumble None Resolution/Resolution: 300dpi *600dpi 2400x600dpi TonerSaveMode/Toner Save: *OFF ON Sleep/Sleep Time [Min.]: *PrinterDefault 2minutes 10minutes 30minutes the diff between a working buster from an ls -l /etc/cups showing: gene@GO704:~/linuxcnc/src$ ls -l /etc/cups total 64 -rw-r--r-- 1 root root 27303 Apr 10 2019 cups-browsed.conf -rw-r--r-- 1 root root 6402 Feb 26 15:05 cupsd.conf -rw-r--r-- 1 root root 2923 May 23 2022 cups-files.conf drwxr-xr-x 2 root lp 4096 May 1 00:00 ppd -rw------- 1 root lp 1882 May 1 00:00 printers.conf -rw------- 1 root lp 111 May 1 00:00 printers.conf.O drwx------ 2 root lp 4096 May 23 2022 ssl -rw-r----- 1 root lp 387 May 1 00:00 subscriptions.conf -rw-r----- 1 root lp 93 May 1 00:00 subscriptions.conf.O which works fine, And a non-working bullseye: gene@bpi51:~$ ls -l /etc/cups/ total 100 -rw------- 1 root lp 111 Dec 2 23:13 classes.conf -rw-r--r-- 1 root root 30436 Mar 14 2022 cups-browsed.conf -rw-r--r-- 1 root root 6456 Oct 15 2022 cupsd.conf -rw-r--r-- 1 root root 3047 May 23 2022 cups-files.conf -rw-r--r-- 1 root root 10982 Jan 2 2021 cups-pdf.conf drwxr-xr-x 2 root root 4096 May 23 2022 interfaces drwxr-xr-x 2 root lp 4096 Dec 2 23:13 ppd -rw------- 1 root lp 529 May 1 10:37 printers.conf -rw------- 1 root lp 529 May 1 10:36 printers.conf.O -rw-r--r-- 1 root root 240 Oct 15 2022 raw.convs -rw-r--r-- 1 root root 211 Oct 15 2022 raw.types -rw-r--r-- 1 root root 142 May 23 2022 snmp.conf drwx------ 2 root lp 4096 May 23 2022 ssl -rw-r----- 1 root lp 524 May 1 00:00 subscriptions.conf -rw-r----- 1 root lp 234 May 1 00:00 subscriptions.conf.O So call me puzzled. I've been called worse.;o)> 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/>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-01 19:40 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqFFf-5QDR-3@gated-at.bofh.it> |
| In reply to | #257806 |
On Mon 01 May 2023 at 13:03:50 -0400, gene heskett wrote: > On 5/1/23 12:30, Brian wrote: > > > > Assuming your buster machines (which are working) have similar setups to bpi51, > > you couls try the two commands (and all the others in this thread) on one of > > those. > > > one of those machines reports this for the -l option: > > gene@sixty40:~$ lpoptions -p HLL2320D_coyote -l > PageSize/Media Size: Custom.WIDTHxHEIGHT *Letter Legal Executive > FanFoldGermanLegal A4 A5 A6 Env10 EnvMonarch EnvDL EnvC5 ISOB5 B5 ISOB6 B6 > 4x6 Postcard DoublePostcardRotated EnvYou4 195x270mm 184x260mm 197x273mm > CUSTOM1 CUSTOM2 CUSTOM3 > BrMediaType/MediaType: *PLAIN THIN THICK THICKERPAPER2 BOND ENV ENVTHICK > ENVTHIN RECYCLED > InputSlot/InputSlot: MANUAL *TRAY1 > Duplex/Duplex: DuplexTumble *DuplexNoTumble None > Resolution/Resolution: 300dpi *600dpi 2400x600dpi > TonerSaveMode/Toner Save: *OFF ON > Sleep/Sleep Time [Min.]: *PrinterDefault 2minutes 10minutes 30minutes Looks reasonable. A similar command on the server should give a similar output. The reason 'lp -d HLL2320D_coyote printer.cfg' failed is because CUPS is unable to query the HLL2320D_coyote printer for its attributes. Printing from anything else, such as Firefox, will also fail. CUPS on the bullseye machine appears to be broken. [...] A possible way forward is to execute sudo lpadmin -p HLL2320D-RAW -v ipp://192.168.71.3:631/printers/HLL2320D -E -m raw and try lp -d HLL2320D-RAW printer.cfg -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-02 00:00 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqJIR-5SZa-1@gated-at.bofh.it> |
| In reply to | #257809 |
On 5/1/23 13:34, Brian wrote: > On Mon 01 May 2023 at 13:03:50 -0400, gene heskett wrote: > >> On 5/1/23 12:30, Brian wrote: >>> >>> Assuming your buster machines (which are working) have similar setups to bpi51, >>> you couls try the two commands (and all the others in this thread) on one of >>> those. >>> >> one of those machines reports this for the -l option: >> >> gene@sixty40:~$ lpoptions -p HLL2320D_coyote -l >> PageSize/Media Size: Custom.WIDTHxHEIGHT *Letter Legal Executive >> FanFoldGermanLegal A4 A5 A6 Env10 EnvMonarch EnvDL EnvC5 ISOB5 B5 ISOB6 B6 >> 4x6 Postcard DoublePostcardRotated EnvYou4 195x270mm 184x260mm 197x273mm >> CUSTOM1 CUSTOM2 CUSTOM3 >> BrMediaType/MediaType: *PLAIN THIN THICK THICKERPAPER2 BOND ENV ENVTHICK >> ENVTHIN RECYCLED >> InputSlot/InputSlot: MANUAL *TRAY1 >> Duplex/Duplex: DuplexTumble *DuplexNoTumble None >> Resolution/Resolution: 300dpi *600dpi 2400x600dpi >> TonerSaveMode/Toner Save: *OFF ON >> Sleep/Sleep Time [Min.]: *PrinterDefault 2minutes 10minutes 30minutes > > Looks reasonable. A similar command on the server should give a similar output. > > The reason 'lp -d HLL2320D_coyote printer.cfg' failed is because CUPS is unable > to query the HLL2320D_coyote printer for its attributes. Printing from anything > else, such as Firefox, will also fail. CUPS on the bullseye machine appears to > be broken. > > [...] > > A possible way forward is to execute > > sudo lpadmin -p HLL2320D-RAW -v ipp://192.168.71.3:631/printers/HLL2320D -E -m raw which gets me this warning: gene@bpi51:~$ sudo lpadmin -p HLL2320D-RAW -v ipp://192.168.71.3:631/printers/HLL2320D -E -m raw [sudo] password for gene: lpadmin: Raw queues are deprecated and will stop working in a future version of CUPS. lpadmin: Use the 'everywhere' model for shared printers. And I wouldn't use the everywhere option ever as it cripples the printer down to the lowest common performing option list, losing among other things, the duplex ability. So it MUST use the Brother driver. > > and try > then I ran this w/o the sudo: > lp -d HLL2320D-RAW printer.cfg And got this: gene@bpi51:~$ lp -d HLL2320D-RAW printer.cfg request id is HLL2320D-RAW-1 (1 file(s)) printing the file in portrait mode, full duplex, but the file is wider and I would normally put it in landscape mode to reduce the auto-word-wrapping confusion. Does -o landscape still work with the raw option? Yes, provided the -olandscape is after the -d argument. That file is a 3d printer description for klipper, 5 pages in landscape mode. And is the first and 2nd time I've been able to print it. Thank you very much. Can we continue, making a shell script to do this again with all variations available for the -o options of lp? Take care & stay well Brian. > 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/>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-02 01:10 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqKOB-5TRk-1@gated-at.bofh.it> |
| In reply to | #257822 |
On Mon 01 May 2023 at 17:53:08 -0400, gene heskett wrote: > On 5/1/23 13:34, Brian wrote: [...] > > A possible way forward is to execute > > > > sudo lpadmin -p HLL2320D-RAW -v ipp://192.168.71.3:631/printers/HLL2320D -E -m raw > which gets me this warning: > gene@bpi51:~$ sudo lpadmin -p HLL2320D-RAW -v > ipp://192.168.71.3:631/printers/HLL2320D -E -m raw > [sudo] password for gene: > lpadmin: Raw queues are deprecated and will stop working in a future version > of CUPS. A standard warning that is clear enough. > lpadmin: Use the 'everywhere' model for shared printers. > > And I wouldn't use the everywhere option ever as it cripples the printer > down to the lowest common performing option list, losing among other things, > the duplex ability. So it MUST use the Brother driver. Your demand is granted. -m raw uses the Brother driver on coyote. > > > > and try > > > then I ran this w/o the sudo: > > lp -d HLL2320D-RAW printer.cfg > And got this: > gene@bpi51:~$ lp -d HLL2320D-RAW printer.cfg > request id is HLL2320D-RAW-1 (1 file(s)) That's OK. > printing the file in portrait mode, full duplex, but the file is wider and I > would normally put it in landscape mode to reduce the auto-word-wrapping > confusion. Does -o landscape still work with the raw option? > > Yes, provided the -olandscape is after the -d argument. That file is a 3d > printer description for klipper, 5 pages in landscape mode. And is the > first and 2nd time I've been able to print it. Thank you very much. > Can we continue, making a shell script to do this again with all variations > available for the -o options of lp? See the lpadmin manual for how to set up different queues with differnent options on bpi51. Glad you are now printing, but you really need to fix the CUPS installation. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-01 19:30 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GqFvz-5QAt-3@gated-at.bofh.it> |
| In reply to | #257805 |
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/>
[toc] | [prev] | [next] | [standalone]
Page 1 of 5 [1] 2 3 4 5 Next page →
Back to top | Article view | linux.debian.user
csiph-web