Re: printing QR-codes on labels with 300dpi label printers with LaTeX

Hi, Max Nikulin wrote: > I admit "dithering" may be incorrect term, [...] > Consider 2 squares having size of 2.5×2.5 pixels. Non-even sizes and fuzzy > lines variants: > █████ > ██████ > ████ ██ >██ ██ >█████ > Second variant might have sense if an

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On 20/03/2024 01:51, Thomas Schmitt wrote: Max Nikulin wrote: When vector graphics, that does not match device resolution, is rasterized, the result is either non-even sizes of similar elements or fuzzy lines due to dithering. Nitpicking: "Dithering" in raster graphics is emulation of color r

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

Hi, Max Nikulin wrote: > When vector graphics, that does not match device resolution, is rasterized, > the result is either non-even sizes of similar elements or fuzzy lines due > to dithering. Nitpicking: "Dithering" in raster graphics is emulation of color resolution at the expense of space re

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On 13/03/2024 12:25, hw wrote: On Mon, 2024-03-11 at 23:45 +0700, Max Nikulin wrote: It seems you expect some number that you can use for any QR code. There is no size that fits for all codes. It's because you said: "I believed that 300dpi is high enough resolution for QR-codes of reasonable s

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On 14/3/24 17:47, jeremy ardley wrote: For reference on a 203 DPI (8 dots per mm) printer, a GS1-128 barcode takes up 12 modules per character. The minimum size of a module is 1 pixel so 1 character is 12 pixels wide or 1.2mm on a 203 dpi printer. Assuming a 40 character barcode at 1 pixel p

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On 14/3/24 06:59, hw wrote: Manufacturers can provide CUPS drivers as well, but the barcode application is usually only windows. In my case I had to write my own CUPS driver as the manufacturer does not provide one. How did you do that? It is simply a C program that gets given some paramete

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On Wed, 2024-03-13 at 03:50 +0800, jeremy ardley wrote: > On 12/3/24 21:21, hw wrote: > > > > Even if they did that, it would be totally useless because it won't be > > able to automatically print labels from databases. > > The manufacturer applications  usually allow you to print a list from a

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On 13/03/2024 02:50, jeremy ardley wrote: Getting back to pixel registration, the latex CUPS route is very unlikely to work well. TeX with MetaFont fonts worked well with low resolution dot matrix printers. Rasterized fonts may be generated for specified resolution. It should be still

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

Florent Rougon wrote: > - printer matrix alignment if printer resolution is low (more > difficult; maybe try with some very small horizontal and veritical > shifts to see if it helps...). Thinking about it more, this is probably hopeless unless printer resolution is *extremely* low. Ty

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

hw wrote: >> That is quite likely: the pst- prefix means this is PSTricks, which is >> an oldish way of doing vector graphics with LaTeX. I tend to avoid >> PSTricks these days as it is generally awkward to use in PDF contexts, >> although there are various workarounds that often allow to do so.

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

; > > > > > > That works for 600dpi laser printers. When you print the QR-code with > > > > a 300dpi label printer you can't reliably scan it, not even when you > > > > make the QR-code 1x1" in size. > > > > > > > > Perhaps t

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On Mon, 2024-03-11 at 11:58 +0100, Florent Rougon wrote: > Hi, > > I haven't read the whole thread (sorry) but thought this might help. > > hw wrote: > > > When I zoom in on QR-codes in a PDF viewer, they don't get blurry. > > Perhaps the pst-barcode package uses vector graphics? > > That is q

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On 12/3/24 21:21, hw wrote: Even if they did that, it would be totally useless because it won't be able to automatically print labels from databases. The manufacturer applications  usually allow you to print a list from a spreadsheet or text file. It is possible to use document generatio

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On Mon, 2024-03-11 at 09:57 +0800, jeremy ardley wrote: > On 11/3/24 07:34, hw wrote: > > Do you think that thermal transfer printers with 203dpi would be > > better suited to print QR codes than the 300dpi multi-mode printers? > > > > I'm not fond of thermal t

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On 11/03/2024 08:06, hw wrote: On Sun, 2024-03-10 at 09:50 +0700, Max Nikulin wrote: On 10/03/2024 04:41, hw wrote: \psbarcode{textblah foo}{height=0.6 width=0.6 eclevel=L}{qrcode} That works for 600dpi laser printers. When you print the QR-code with a 300dpi label printer you can't rel

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

Hi, I haven't read the whole thread (sorry) but thought this might help. hw wrote: > When I zoom in on QR-codes in a PDF viewer, they don't get blurry. > Perhaps the pst-barcode package uses vector graphics? That is quite likely: the pst- prefix means this is PSTricks, which is an oldish way o

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On 11/3/24 07:34, hw wrote: Do you think that thermal transfer printers with 203dpi would be better suited to print QR codes than the 300dpi multi-mode printers? I'm not fond of thermal transfer at all. Usually what is being printed that way fades rather quickly over time and is

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On Sun, 2024-03-10 at 09:50 +0700, Max Nikulin wrote: > On 10/03/2024 04:41, hw wrote: > > \psbarcode{textblah foo}{height=0.6 width=0.6 eclevel=L}{qrcode} > > > > That works for 600dpi laser printers. When you print the QR-code with > > a 300dpi label printer you

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On Sun, 2024-03-10 at 07:56 +0800, jeremy ardley wrote: > On 10/3/24 05:41, hw wrote: > > The QR-codes are sharp and easily scanable when printed in 600dpi. > > With the label printer you can't really tell if they're sharp or not. > > As  mentioned in my previous p

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On Sun, 2024-03-10 at 10:21 +0700, Max Nikulin wrote: > On 10/03/2024 03:48, jeremy ardley wrote: > > > > Standard thermal label printers are 203DPI (8 dots per mm). > > Thanks, this number suits better to my expectation. I just trusted hw > earlier. I should clar

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On 10/3/24 15:39, Max Nikulin wrote: From your earlier message I count approximately 1000px for 5in (125 mm) barcode. If it is 1:1 to ~200dpi then it is incompatible with 300dpi printers, so it may be a reason why your proposal to the post office was rejected. If it is 500 black or white

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

I count approximately 1000px for 5in (125 mm) barcode. If it is 1:1 to ~200dpi then it is incompatible with 300dpi printers, so it may be a reason why your proposal to the post office was rejected. If it is 500 black or white lines and each one occupies 2 printer dots then 300dpi image of the

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On 10/3/24 11:21, Max Nikulin wrote: Is the QR image a raster one? I am unsure concerning its printer dots per QR pixel ratio. Let's take e.g. 4 as a value inconvenient for direct scaling from 300dpi to 203dpi. I expect that upscaling it by 3 and downscaling the result by 4 with disabled sm

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On 10/03/2024 03:48, jeremy ardley wrote: Standard thermal label printers are 203DPI (8 dots per mm). Thanks, this number suits better to my expectation. I just trusted hw earlier. I have asked the postal service to generate labels at 203dpi which will print just fine at 600 dpi and so

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On 10/03/2024 04:41, hw wrote: \psbarcode{textblah foo}{height=0.6 width=0.6 eclevel=L}{qrcode} That works for 600dpi laser printers. When you print the QR-code with a 300dpi label printer you can't reliably scan it, not even when you make the QR-code 1x1" in size. Perhaps th

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On 10/3/24 05:41, hw wrote: The QR-codes are sharp and easily scanable when printed in 600dpi. With the label printer you can't really tell if they're sharp or not. As  mentioned in my previous post, thermal label printers are 203dpi, *not the 300 that the OP quoted.* you can r

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

l influence the result. Also, labels are continuously being fed through the printer while printing without stopping. That makes some smear inevitable. > format of QR codes. It basically goes like this: \psbarcode{textblah foo}{height=0.6 width=0.6 eclevel=L}{qrcode} That works for 600dpi l

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

stability of optics in scanners in respect to labels. This one is printed using a laser printer with resolution at least 600 dpi. Each QR code pixel has still 4x4 printer dots in the case of 300dpi, so when image is properly aligned, printer quality is not an issue. Standard thermal label printers

Re: printing QR-codes on labels with 300dpi label printers with LaTeX

On 09/03/2024 19:08, hw wrote: On Fri, 2024-03-08 at 23:21 +0700, Max Nikulin wrote: On 08/03/2024 12:35, hw wrote: On Thu, 2024-03-07 at 23:15 -0500, Jeffrey Walton wrote: I have a USB thermal printer for the shipping labels, . This printer has

printing QR-codes on labels with 300dpi label printers with LaTeX (was: libbusiness-us-usps-webtools-perl and USPS Ground Advantage shipping)

On Fri, 2024-03-08 at 23:21 +0700, Max Nikulin wrote: > On 08/03/2024 12:35, hw wrote: > > On Thu, 2024-03-07 at 23:15 -0500, Jeffrey Walton wrote: > > > > > > I have a USB thermal printer for the shipping labels, > > > . > > > > This printer has only

More printers in the Brother printer-driver-brlaser package

Greetings, There are drivers for more Brother laser printers in the package printer-driver-brlaser . One doesn't have to put up with Brother's atrocious install script to set up the DCP-1610W. The driver package from the Debian repository doesn't produce the extraneous squi

Printers disappear

I used /usr/bin/system-config-printer to detect and set up my printers. I want to set up one of the printers to do do both simplex and duplex printing, so I duplicate it, and change the original settings that the "find printer" process discovered from simplex to duplex. After a few

Re: cups not sharing printers with other bullseye machines

ressed to cups from my local 192.168/xx.yy network? >>> >>> The problem is: other buster machines on this local network can see and >>> use the two brother printers just as if the printer was local to that >>> buster machine. >>> >>> But no bullse

Re: cups not sharing printers with other bullseye machines

n see and use the two brother printers just as if the printer was local to that buster machine. But no bullseye, debian or armbian can see anything at localhost:631/printers except the search screen when there are no printers. These printers are marked as shared in this bullseye machines /etc/cups

Re: cups not sharing printers with other bullseye machines

n see and use the two brother printers just as if the printer was local to that buster machine. But no bullseye, debian or armbian can see anything at localhost:631/printers except the search screen when there are no printers. These printers are marked as shared in this bullseye machines /etc/cups

Re: cups not sharing printers with other bullseye machines

> use the two brother printers just as if the printer was local to that > buster machine. > > But no bullseye, debian or armbian can see anything at > localhost:631/printers except the search screen when there are no printers. > > These printers are marked as shared

cups not sharing printers with other bullseye machines

Greetings all; Where do I turn on cups debugging so I'll see every bit of traffic addressed to cups from my local 192.168/xx.yy network? The problem is: other buster machines on this local network can see and use the two brother printers just as if the printer was local to that b

Re: can't see shared printers from clients o local network

On 3/30/23 04:47, Jeremy Ardley wrote: On 30/3/23 16:32, gene heskett wrote: Greetings all; hosts based local 192.158.xx.yy network. cups at localhost:631 on any buster machine sees my printers just fine, and the buster machines can print to them. Those machines running bullseye aren&#

Re: can't see shared printers from clients o local network

On 30/3/23 16:32, gene heskett wrote: Greetings all; hosts based local 192.158.xx.yy network. cups at localhost:631 on any buster machine sees my printers just fine, and the buster machines can print to them. Those machines running bullseye aren't allowed. can't see my printers

Re: CUPS - how to match autodetected printers to physical ones

Canon LBP712Cdn (db:c0:d3) > + eno1 IPv4 HP LaserJet P3010 Series [0FCDD7] > + eno1 IPv4 hp LaserJet 4250 [621E13] He did not want to use these printers, but they would be shown in the print dialog of Evince (say), as would be the non-adverised printer if it had been set up correct

Re: CUPS - how to match autodetected printers to physical ones

Hi. On Sat, Feb 25, 2023 at 11:26:21PM +, Brian wrote: > > It's interesting how you bring up DHCP, yet do not mention DHCP option 9 > > (aka "option lpr-servers" in ISC lingo). > > A proper implementation of DHCP options would make DNS-SD (and other > > assorted kludges) completely red

Re: CUPS - how to match autodetected printers to physical ones

On Sat 25 Feb 2023 at 22:22:55 +0300, Reco wrote: > On Sat, Feb 25, 2023 at 06:30:28PM +, Brian wrote: > > On Sat 25 Feb 2023 at 17:44:15 +0300, Reco wrote: > > > > > Hi. > > > > > > On Fri, Feb 24, 2023 at 12:58:15PM -0500, Greg Wooledge wrote: > > > > On Fri, Feb 17, 2023 at 05:35:11PM +

Re: CUPS - how to match autodetected printers to physical ones

On Sat, Feb 25, 2023 at 06:30:28PM +, Brian wrote: > On Sat 25 Feb 2023 at 17:44:15 +0300, Reco wrote: > > > Hi. > > > > On Fri, Feb 24, 2023 at 12:58:15PM -0500, Greg Wooledge wrote: > > > On Fri, Feb 17, 2023 at 05:35:11PM +0300, Reco wrote: > > > > Try this next time you're on site: >

Re: CUPS - how to match autodetected printers to physical ones

On Sat 25 Feb 2023 at 17:44:15 +0300, Reco wrote: > Hi. > > On Fri, Feb 24, 2023 at 12:58:15PM -0500, Greg Wooledge wrote: > > On Fri, Feb 17, 2023 at 05:35:11PM +0300, Reco wrote: > > > Try this next time you're on site: > > > > > > lpadmin -p D14841 -E -v ipp://10.76.172.100/ipp/print -m

Re: CUPS - how to match autodetected printers to physical ones

Hi. On Fri, Feb 24, 2023 at 12:58:15PM -0500, Greg Wooledge wrote: > On Fri, Feb 17, 2023 at 05:35:11PM +0300, Reco wrote: > > Try this next time you're on site: > > > > lpadmin -p D14841 -E -v ipp://10.76.172.100/ipp/print -m everywhere > > This worked. I printed two copies of the sing

Re: CUPS - how to match autodetected printers to physical ones

wo copies of the single-page PDF from Chrome > without any further problems. Good. As I have previous indicated, this works because the vendor has not used ipp/canon as the resource, which it is at liberty to do so. A previous off-target comment was > My burning hatred of printers and this

Re: CUPS - how to match autodetected printers to physical ones

On Fri, Feb 17, 2023 at 05:35:11PM +0300, Reco wrote: > Try this next time you're on site: > > lpadmin -p D14841 -E -v ipp://10.76.172.100/ipp/print -m everywhere This worked. I printed two copies of the single-page PDF from Chrome without any further problems. I've gotta say, though, this opti

Re: CUPS - how to match autodetected printers to physical ones

On 16/02/2023 22:41, Greg Wooledge wrote: 2) Also suggested: avahi-browse -rt _ipp._tcp This year, the output of that command no longer contains my printer's IP address. Last year, it did. I have no idea why this has changed. Avahi was mentioned in the ipv6 thread, so I decided to re

Re: CUPS - how to match autodetected printers to physical ones

On Fri 17 Feb 2023 at 09:05:39 -0500, Greg Wooledge wrote: > On Fri, Feb 17, 2023 at 11:18:32AM +, Brian wrote: [...] > > avahi-browse -rt _ipp._tcp > > avahi-browse -rt _uscan._tcp > > > > (I would find that data useful for my records). > > wooledg:~$ avahi-browse -rt _ipp._tcp 2>&1 |

Re: CUPS - how to match autodetected printers to physical ones

Hi. On Thu, Feb 16, 2023 at 10:41:33AM -0500, Greg Wooledge wrote: > So the printer WORKS. It is ON THE NETWORK. I can print TEXT to it > using port 9100. > > What I CANNOT do is find it in CUPS. Or avahi-browse, or driverless, or > any of these other commands that are so allegedly won

Re: CUPS - how to match autodetected printers to physical ones

On Fri, Feb 17, 2023 at 11:18:32AM +, Brian wrote: > On Thu 16 Feb 2023 at 15:32:47 -0500, Greg Wooledge wrote: > > > wooledg:~$ cat /etc/debian_version > > 11.6 > > wooledg:~$ lpstat -l -e > > Canon_LBP712C_UFR_II_ permanent > > ipp://localhost/pri

Re: CUPS - how to match autodetected printers to physical ones

On Thu 16 Feb 2023 at 15:32:47 -0500, Greg Wooledge wrote: > wooledg:~$ cat /etc/debian_version > 11.6 > wooledg:~$ lpstat -l -e > Canon_LBP712C_UFR_II_ permanent > ipp://localhost/printers/Canon_LBP712C_UFR_II_ > ipp://Canon%20LBP712Cdn%20(db%3Ac0%3Ad3)._ipp._tcp.local/ Thi

Re: CUPS - how to match autodetected printers to physical ones

On Thu, Feb 16, 2023 at 03:51:47PM -0500, gene heskett wrote: > I hate to ask the obvious, but is the net cable plugged into that printer? See below. On Thu, Feb 16, 2023 at 10:41:33AM -0500, Greg Wooledge wrote: > 4) Also mentioned: port 9100. >For grins, I did "telnet 10.76.172.100 9100" an

Re: CUPS - how to match autodetected printers to physical ones

On 2/16/23 16:09, Bob McGowan wrote: On 2/16/23 12:01 PM, Brian wrote: On Thu 16 Feb 2023 at 11:27:25 -0800, Bob McGowan wrote: On 2/16/23 11:14 AM, Brian wrote: On Thu 16 Feb 2023 at 11:52:21 -0500, Stefan Monnier wrote: [1]to...@tuxteam.de [2023-02-16 16:53:02] wrote: Just for kicks

Re: CUPS - how to match autodetected printers to physical ones

On 2/16/23 12:01 PM, Brian wrote: On Thu 16 Feb 2023 at 11:27:25 -0800, Bob McGowan wrote: On 2/16/23 11:14 AM, Brian wrote: On Thu 16 Feb 2023 at 11:52:21 -0500, Stefan Monnier wrote: [1]to...@tuxteam.de [2023-02-16 16:53:02] wrote: Just for kicks: have you tried sending a PS (or *gas

Re: CUPS - how to match autodetected printers to physical ones

t's another Canon LBP712Cdn somewhere else on the 10th floor, or at least something claiming to be a Canon LBP712Cdn. I still have no idea what the db:c0:d3 means. Your machine has bullseye, we suppose? Give what you gat for lpstat -l -e wooledg:~$ cat /etc/debian_version 11.6 wooledg

Re: CUPS - how to match autodetected printers to physical ones

ot; suffix. The printer with that suffix in CUPS is the black hole where whatever I send doesn't get printed by my printer. I assume it's another Canon LBP712Cdn somewhere else on the 10th floor, or at least something claiming to be a Canon LBP712Cdn. I still have no idea what the db:c0:

Re: CUPS - how to match autodetected printers to physical ones

On Thu 16 Feb 2023 at 11:27:25 -0800, Bob McGowan wrote: >On 2/16/23 11:14 AM, Brian wrote: > > On Thu 16 Feb 2023 at 11:52:21 -0500, Stefan Monnier wrote: > > > [1]to...@tuxteam.de [2023-02-16 16:53:02] wrote: > > Just for kicks: have you tried sending a PS (or *gasp* PDF) file > down tha

Re: CUPS - how to match autodetected printers to physical ones

On 2/16/23 11:14 AM, Brian wrote: On Thu 16 Feb 2023 at 11:52:21 -0500, Stefan Monnier wrote: to...@tuxteam.de [2023-02-16 16:53:02] wrote: Just for kicks: have you tried sending a PS (or *gasp* PDF) file down that alley (e.g. with soc

Re: CUPS - how to match autodetected printers to physical ones

On Thu 16 Feb 2023 at 11:52:21 -0500, Stefan Monnier wrote: > to...@tuxteam.de [2023-02-16 16:53:02] wrote: > > Just for kicks: have you tried sending a PS (or *gasp* PDF) file > > down that alley (e.g. with socat)? > > > > For That One Form in the Year this might be just sufficient... > > > > Hin

Re: CUPS - how to match autodetected printers to physical ones

s, but it should not be needed and involves guessing.(Please try to avoid unhelpful, judgemental adjectives). [...] > My burning hatred of printers and this printing system remains unquenched. Calm down! Understanding a situation (like the operation of a shell script) requires being able to focus. -- Brian.

Re: CUPS - how to match autodetected printers to physical ones

On Thu, Feb 16, 2023 at 11:52:21AM -0500, Stefan Monnier wrote: > to...@tuxteam.de [2023-02-16 16:53:02] wrote: > > Just for kicks: have you tried sending a PS (or *gasp* PDF) file > > down that alley (e.g. with socat)? > > > > For That One Form in the Year this might be just sufficient... > > > >

Re: CUPS - how to match autodetected printers to physical ones

* 2023-02-16 10:41:33-0500, Greg Wooledge wrote: > 1) Someone suggested: avahi-discover -r _print-caps._tcp >When I tried it last year, it simply hung with no visible output >until Ctrl-C'ed. Here is my version which I suggest turning into a shell alias, function or script: avahi-bro

Re: CUPS - how to match autodetected printers to physical ones

to...@tuxteam.de [2023-02-16 16:53:02] wrote: > Just for kicks: have you tried sending a PS (or *gasp* PDF) file > down that alley (e.g. with socat)? > > For That One Form in the Year this might be just sufficient... > > Hint: start with a small one :) I don't think "a small one" can be small enou

Re: CUPS - how to match autodetected printers to physical ones

paper attached to the printer (I took a picture of it with a cell phone, and carried the phone back to my desk so I can type it all out): D#: D14841 P#: IP: 10.76.172.100 Queue \\SPS\S010NEURD14841M Model # Canon LBP712Cdn Serial # NGDA008248 Bldg: S Flr: 10 Zone: Main Room: 007 Epic ID Notes B9754 My

Re: CUPS - how to match autodetected printers to physical ones

On Thu, Feb 16, 2023 at 10:41:33AM -0500, Greg Wooledge wrote: [...] > 4) Also mentioned: port 9100. >For grins, I did "telnet 10.76.172.100 9100" and after that connected >I typed "HELLO WORLD", then pressed Enter, then Ctrl-] q Enter to >close the telnet session. > >That actual

Re: CUPS - how to match autodetected printers to physical ones

phone, and carried the phone back to my desk so I can type it all out): D#: D14841 P#: IP: 10.76.172.100 Queue \\SPS\S010NEURD14841M Model # Canon LBP712Cdn Serial # NGDA008248 Bldg: S Flr: 10 Zone: Main Room: 007 Epic ID Notes B9754 My burning hatred of printers and this printing system remains unquenched.

Re: CUPS and available-printers-list management (was Re: non installed printer can not be removed)

ring into the >>>>> picture. >>>> >>>> "...once the URIis known"? What mechaism does that? Incidentally, a >>>> URI is required to query a printer for its attributes. >>> >>> Any of a number of mechanisms. >>> >>

Re: CUPS and available-printers-list management (was Re: non installed printer can not be removed)

sm does that? Incidentally, a >>> URI is required to query a printer for its attributes. >> >> Any of a number of mechanisms. >> >> CUPS could run discovery once, then either A: present the discovered URI >> with a prompt for whether to add it to its local list

Re: CUPS and available-printers-list management (was Re: non installed printer can not be removed)

of mechanisms. > > CUPS could run discovery once, then either A: present the discovered URI > with a prompt for whether to add it to its local list of known printers > or B: add it to that list automatically, and then in either case not run > discovery again until something asks it to.

Re: CUPS and available-printers-list management (was Re: non installed printer can not be removed)

known"? What mechaism does that? Incidentally, a > > > URI is required to query a printer for its attributes. > > > > Any of a number of mechanisms. > > > > CUPS could run discovery once, then either A: present the discovered URI > > with a prompt for wh

Re: CUPS and available-printers-list management (was Re: non installed printer can not be removed)

sms. > > CUPS could run discovery once, then either A: present the discovered URI > with a prompt for whether to add it to its local list of known printers > or B: add it to that list automatically, and then in either case not run > discovery again until something asks it to. > &g

Re: CUPS and available-printers-list management (was Re: non installed printer can not be removed)

. > > "...once the URIis known"? What mechaism does that? Incidentally, a > URI is required to query a printer for its attributes. Any of a number of mechanisms. CUPS could run discovery once, then either A: present the discovered URI with a prompt for whether to add it to its

Re: CUPS and available-printers-list management (was Re: non installed printer can not be removed)

say what is meant by "delete". > >>> CUPS essentially *discover* printers. It is why it exists. Is > >>> that not wanted? > >> > >> I understand the reason for CUPS' existence to be, not > >> *discovering printers*, but *facilitating the

CUPS and available-printers-list management (was Re: non installed printer can not be removed)

On 2022-06-20 at 08:59, Brian wrote: > On Sun 19 Jun 2022 at 18:01:36 -0400, The Wanderer wrote: > >> On 2022-06-19 at 15:47, Brian wrote: >>> You (or the OP) would have to say what is meant by "delete". >>> CUPS essentially *discover* printers. It

Re: CUPS - how to match autodetected printers to physical ones

On Mon 11 Apr 2022, at 19:23, Brian wrote: > On Mon 11 Apr 2022 at 13:55:03 -0400, Greg Wooledge wrote: > >> On Mon, Apr 11, 2022 at 06:47:59PM +0100, Brian wrote: >> > BTW. I am interested in how using /usr/lib/cups/backend/snmp went. >> > Its drawback is that no

Re: CUPS - how to match autodetected printers to physical ones

On Mon 11 Apr 2022 at 13:55:03 -0400, Greg Wooledge wrote: > On Mon, Apr 11, 2022 at 06:47:59PM +0100, Brian wrote: > > BTW. I am interested in how using /usr/lib/cups/backend/snmp went. > > Its drawback is that not all printers provide an snmp service. > > wooledg:~$ /usr/

Re: CUPS - how to match autodetected printers to physical ones

On Mon, Apr 11, 2022 at 06:47:59PM +0100, Brian wrote: > BTW. I am interested in how using /usr/lib/cups/backend/snmp went. > Its drawback is that not all printers provide an snmp service. wooledg:~$ /usr/lib/cups/backend/snmp network socket://10.76.172.120 "HP LaserJet 4250" &

Re: CUPS - how to match autodetected printers to physical ones

ird method. It is too involved to explain how to reverse what is in the implicitclass URI just for resolving. avahi-browse seems the way to go for your purpose. BTW. I am interested in how using /usr/lib/cups/backend/snmp went. Its drawback is that not all printers provide an snmp service. -- Brian.

Re: CUPS - how to match autodetected printers to physical ones

On Mon, Apr 11, 2022 at 05:47:07PM +0100, Brian wrote: > What does > >avahi-browse -rt _ipp._tcp | grep -B3 port > > give for this device? = eno1 IPv4 Canon LBP351dn (f9:7a:4a) Internet Printer local hostname = [dhcp-10-76-172-100.local] address = [10.76.172.

Re: CUPS - how to match autodetected printers to physical ones

On Mon 11 Apr 2022 at 11:53:38 -0400, Greg Wooledge wrote: > On Mon, Apr 11, 2022 at 03:40:12PM +0100, Brian wrote: > > A third way forward: > > > > "implicitclass://Canon_LBP351dn_f9_7a_4a_/" is the URI for this printer. > > Canon_LBP351dn_f9_7a_4a_ is the printer's Service Name. > > > > ava

Re: CUPS - how to match autodetected printers to physical ones

On Mon, Apr 11, 2022 at 03:40:12PM +0100, Brian wrote: > A third way forward: > > "implicitclass://Canon_LBP351dn_f9_7a_4a_/" is the URI for this printer. > Canon_LBP351dn_f9_7a_4a_ is the printer's Service Name. > > avahi-resolve -n Canon_LBP351dn_f9_7a_4a_.local > > should give the IP addre

Re: CUPS - how to match autodetected printers to physical ones

e to find ANY way to determine the IP > > > > addresses of the autodetected printers that were presented to me. > > > > > > If I go to http://localhost:631/printers/ > > > > I should say I got to that URL from the CUPs interface at > > http://localh

Re: CUPS - how to match autodetected printers to physical ones

, an rpi4, > > does not expose the printers address, only: > > pi@rpi4:~ $ sudo /usr/lib/cups/backend/snmp > > network lpd://BRN30055C8A2DC8/BINARY_P1 "Brother MFC-J6920DW" > > "Brother > > MFC-J6920DW" "MFG:Brother;CMD:HBP,BRPJL,URF;MDL:MFC- &

Re: CUPS - how to match autodetected printers to physical ones

On Sun 10 Apr 2022 at 21:29:30 +0200, to...@tuxteam.de wrote: > On Sun, Apr 10, 2022 at 08:19:52PM +0100, Brian wrote: > > [...] > > > > forbidden of trying to do network scans, but the sysadmin wants to > > > know. I can't blame him (I'm on speaking terms with him ;-) > > > > Not forbidden? >

Re: CUPS - how to match autodetected printers to physical ones

On Sun, Apr 10, 2022 at 08:19:52PM +0100, Brian wrote: [...] > > forbidden of trying to do network scans, but the sysadmin wants to > > know. I can't blame him (I'm on speaking terms with him ;-) > > Not forbidden? > > I know a corporate network or two which would get you disconnected > if

Re: CUPS - how to match autodetected printers to physical ones

> > > [...] > > > > > > > Many printers provide an snmp (Simple Network Management Protocol) > > > > service on port 9100. Check with > > > > > > > > nmap 10.76.172.100 > > > > > > I know a corporate network or two

Re: CUPS - how to match autodetected printers to physical ones

rily, if not exclusively, by its IP >> address.) > > Of corse the IP address is needed, but not by the user. The user is > better served by having the queue name matching the printer. That depends on what information the user is going to be able to access about the printer. I have

Re: CUPS - how to match autodetected printers to physical ones

On Sun, Apr 10, 2022 at 06:47:36PM +0100, Brian wrote: > On Sun 10 Apr 2022 at 15:40:28 +0200, to...@tuxteam.de wrote: > > > On Sun, Apr 10, 2022 at 01:40:29PM +0100, Brian wrote: > > > > [...] > > > > > Many printers provide an snmp (Simple Network Man

Re: CUPS - how to match autodetected printers to physical ones

On Sun 10 Apr 2022 at 08:52:09 -0400, The Wanderer wrote: > On 2022-04-10 at 08:38, Brian wrote: [...] > > The CUPS web interface is not designed to show the IP address but to > > display the URI. > > This, I think, is exactly the detail that's being complained of. If CUPS > knows the IP addr

Re: CUPS - how to match autodetected printers to physical ones

On Sun 10 Apr 2022 at 15:40:28 +0200, to...@tuxteam.de wrote: > On Sun, Apr 10, 2022 at 01:40:29PM +0100, Brian wrote: > > [...] > > > Many printers provide an snmp (Simple Network Management Protocol) > > service on port 9100. Check with > > > > nmap 1

Re: CUPS - how to match autodetected printers to physical ones

aring, cups > > > does > > > its own advertising. All printers here are attached to this machine, > > > marked as shareable and I can put stuff on their output trays from > > > any > > > machine including the rpi4 on my local network. > > > > Indeed

Re: CUPS - how to match autodetected printers to physical ones

On Sun 10 Apr 2022 at 10:05:09 -0400, The Wanderer wrote: > On 2022-04-10 at 09:54, Brian wrote: > > > The snmp backend is not installed in the location I gave but has > > to be moved there. Do either > > > > mv /usr/lib/cups/backend-available/snmp /usr/lib/cups/backend/snmp > > > > or > > >

Re: CUPS - how to match autodetected printers to physical ones

On 2022-04-10 at 09:54, Brian wrote: > The snmp backend is not installed in the location I gave but has > to be moved there. Do either > > mv /usr/lib/cups/backend-available/snmp /usr/lib/cups/backend/snmp > > or > > dpkg-reconfigure cups I've never taken specific action in either of these

Re: CUPS - how to match autodetected printers to physical ones

On Sun 10 Apr 2022 at 09:19:43 -0400, gene heskett wrote: > On Sunday, 10 April 2022 08:40:29 EDT Brian wrote: > > /usr/lib/cups/backend/snmp > The only machine I have here that has that file installed, an rpi4, does > not expose the printers address, only: > pi@rpi4:~ $ s

Re: CUPS - how to match autodetected printers to physical ones

On Sun, Apr 10, 2022 at 01:40:29PM +0100, Brian wrote: [...] > Many printers provide an snmp (Simple Network Management Protocol) > service on port 9100. Check with > > nmap 10.76.172.100 I know a corporate network or two which would get you disconnected if you do that :) Then y

Re: CUPS - how to match autodetected printers to physical ones

On Sun 10 Apr 2022 at 08:10:17 -0400, gene heskett wrote: > On Sunday, 10 April 2022 07:17:42 EDT The Wanderer wrote: > > On 2022-04-10 at 07:08, gene heskett wrote: > > > On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote: > > >> I just don't install it. > > > > > > And how do you acco

Re: CUPS - how to match autodetected printers to physical ones

On Sunday, 10 April 2022 08:54:07 EDT Brian wrote: > On Sun 10 Apr 2022 at 05:46:35 -0400, gene heskett wrote: > > [...] > > > This, FWIW, has nothing to do with cups and printer sharing, cups > > does > > its own advertising. All printers here are attached

Re: CUPS - how to match autodetected printers to physical ones

On Sunday, 10 April 2022 08:40:29 EDT Brian wrote: > /usr/lib/cups/backend/snmp The only machine I have here that has that file installed, an rpi4, does not expose the printers address, only: pi@rpi4:~ $ sudo /usr/lib/cups/backend/snmp network lpd://BRN30055C8A2DC8/BINARY_P1 "Bro

Re: CUPS - how to match autodetected printers to physical ones

On Sun 10 Apr 2022 at 05:46:35 -0400, gene heskett wrote: [...] > This, FWIW, has nothing to do with cups and printer sharing, cups does > its own advertising. All printers here are attached to this machine, > marked as shareable and I can put stuff on their output trays from any

  1   2   3   4   5   6   7   8   >