rote:
> > > >
> > > > [Broken lines mended to give a readable original post.]
> > > >
> > > Blame that in tbird.
> > Yet another part of the compting experience tou are unable to
> > control?
> > > > > I give up, the driverles
this is the third case we've seen of what seems to be a
fax+driverless printing bug in cups.
As well as
$ lpadmin [...] everywhere
"IPP Eveywhere" printers/queues added via cups web interface (localhost:631)
also seem to work.
I have reported the problem upstream after help f
experience tou are unable to
control?
I give up, the driverless printer cups installs automaticaly cannot be
deleted and has taken over from the brother drivers that work,
preventing me from using the printer at all.
So how do I disable the driverless junk? Is that a separate package
On 7/13/22 18:25, Gareth Evans wrote:
On 13 Jul 2022, at 22:04, gene heskett wrote:
On 7/13/22 15:15, Gareth Evans wrote:
[...]
Out of interest, which model printer(s) has the issue?
Brother MFC-J6920DW A huge tabloid capable printer/scanner
# lpinfo -v
first off, none of that stuff is
of the compting experience tou are unable to
control?
> > > I give up, the driverless printer cups installs automaticaly cannot be
> > > deleted and has taken over from the brother drivers that work,
> > > preventing me from using the printer at all.
> > >
> &g
> On 13 Jul 2022, at 22:04, gene heskett wrote:
> On 7/13/22 15:15, Gareth Evans wrote:
>> [...]
>> Out of interest, which model printer(s) has the issue?
> Brother MFC-J6920DW A huge tabloid capable printer/scanner
>> # lpinfo -v
> first off, none of that stuff is available to the user unless
On 7/13/22 15:15, Gareth Evans wrote:
On 13 Jul 2022, at 18:21, gene heskett wrote:
I give up, the driverless printer cups installs automaticaly cannot be deleted
and has
taken over from the brother drivers that work, preventing me from using the
printer at all.
So how do I disable
On Wed 13 Jul 2022, at 20:36, Brian wrote:
> On Wed 13 Jul 2022 at 20:12:28 +0100, Gareth Evans wrote:
[...]
>>
>> Hi Gene,
>>
>> Out of interest, which model printer(s) has the issue?
>>
>> There are options in
>>
>> /etc/cups/cu
On 7/13/22 15:14, Brian wrote:
On Wed 13 Jul 2022 at 13:21:07 -0400, gene heskett wrote:
[Broken lines mended to give a readable original post.]
Blame that in tbird.
I give up, the driverless printer cups installs automaticaly cannot be
deleted and has taken over from the brother drivers
On 7/13/22 13:59, John Conover wrote:
gene heskett writes:
I give up, the driverless printer cups installs automaticaly cannot be
deleted and has
taken over from the brother drivers that work, preventing me from using
the printer at all.
So how do I disable the driverless junk
On Wed 13 Jul 2022 at 20:12:28 +0100, Gareth Evans wrote:
>
> > On 13 Jul 2022, at 18:21, gene heskett wrote:
> > I give up, the driverless printer cups installs automaticaly cannot be
> > deleted and has
> > taken over from the brother drivers that wor
On Wed 13 Jul 2022 at 10:56:15 -0700, John Conover wrote:
> gene heskett writes:
> > I give up, the driverless printer cups installs automaticaly cannot be
> > deleted and has
> > taken over from the brother drivers that work, preventing me from using
> > the printer
> On 13 Jul 2022, at 18:21, gene heskett wrote:
> I give up, the driverless printer cups installs automaticaly cannot be
> deleted and has
> taken over from the brother drivers that work, preventing me from using the
> printer at all.
>
> So how do I disabl
On Wed 13 Jul 2022 at 13:21:07 -0400, gene heskett wrote:
[Broken lines mended to give a readable original post.]
> I give up, the driverless printer cups installs automaticaly cannot be
> deleted and has taken over from the brother drivers that work,
> preventing me from using th
gene heskett writes:
> I give up, the driverless printer cups installs automaticaly cannot be
> deleted and has
> taken over from the brother drivers that work, preventing me from using
> the printer at all.
>
> So how do I disable the driverless junk? Is that
On 2022-07-13 18:21, gene heskett wrote:
I give up, the driverless printer cups installs automaticaly cannot be
deleted and has
taken over from the brother drivers that work, preventing me from
using the printer at all.
So how do I disable the driverless junk? Is that a separate package
I give up, the driverless printer cups installs automaticaly cannot be
deleted and has
taken over from the brother drivers that work, preventing me from using
the printer at all.
So how do I disable the driverless junk? Is that a separate package that
is removable?
cups doesn't even offer
After troubleshooting assistance from the Debian Printing team, I was advised
to report my non-printing driverless printer issue upstream, which I have done.
https://github.com/OpenPrinting/cups-filters/issues/472
Given that driverless printing works in CUPS 2.4 (on Ubuntu 22.04
wrote:
>>>>
>>>>> On 2022-06-20 at 08:59, Brian wrote:
>>>
>>>>>> The ability to print to an IPP printer involves discovering its
>>>>>> URI. CUPS gets the URI via avahi-daemon whether it is an
>>>>>> o
rote:
>>
>>>>> The ability to print to an IPP printer involves discovering its
>>>>> URI. CUPS gets the URI via avahi-daemon whether it is an
>>>>> on-demand or manual queue.
>>>>
>>>> But that discovery doesn't have to be done
On Mon 20 Jun 2022, at 17:34, The Wanderer wrote:
> On 2022-06-20 at 12:01, Brian wrote:
>
>> On Mon 20 Jun 2022 at 09:28:30 -0400, The Wanderer wrote:
>>
>>> On 2022-06-20 at 08:59, Brian wrote:
>
>>>> The ability to print to an IPP printer involves d
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 pr
On Mon 20 Jun 2022 at 12:34:19 -0400, The Wanderer wrote:
> On 2022-06-20 at 12:01, Brian wrote:
>
> > "...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 mechani
On 2022-06-20 at 12:01, Brian wrote:
> On Mon 20 Jun 2022 at 09:28:30 -0400, The Wanderer wrote:
>
>> On 2022-06-20 at 08:59, Brian wrote:
>>> The ability to print to an IPP printer involves discovering its
>>> URI. CUPS gets the URI via avahi-daemon whether it
On Mon 20 Jun 2022 at 09:28:30 -0400, The Wanderer wrote:
> 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
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
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
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/
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" &
a) Internet Printer
>local
>hostname = [dhcp-10-76-172-100.local]
>address = [10.76.172.100]
>port = [631]
>
> And for completeness:
>
> wooledg:~$ avahi-resolve -n dhcp-10-76-172-100.local
> dhcp-10-76-172-100.local 10.76.172.1
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 =
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.
> >
> >
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
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:/
On Sunday, 10 April 2022 09:54:34 EDT Brian wrote:
> 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
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?
>
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
On Sun 10 Apr 2022 at 20:39:15 +0200, to...@tuxteam.de wrote:
> 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
On 2022-04-10 at 14:25, Brian wrote:
> 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.
>
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 Management Protocol)
> > > service on port
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. I
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 10.76.172.100
>
> I know a corporate
On Sun 10 Apr 2022 at 09:31:59 -0400, gene heskett wrote:
> 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 sh
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/s
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 s
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
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 you've got to
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
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 attach
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
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
On 2022-04-10 at 08:38, Brian wrote:
> On Sat 09 Apr 2022 at 20:21:12 -0400, The Wanderer wrote:
>
>> On 2022-04-09 at 07:56, Brian wrote:
>>> It is straightforward, I don't know about obvious to all users.
>>>
>>> avahi-browse -rt _ipp._tcp
>>
On Sunday, 10 April 2022 08:02:32 EDT to...@tuxteam.de wrote:
> On Sun, Apr 10, 2022 at 07:46:37AM -0400, gene heskett wrote:
> > On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
> > > AVAHI_DAEMON_DETECT_LOCAL=0 into some /etc/default/avahi-daemon.
> >
> > Checking all my machines,
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:/
18:44, Brian wrote:
>
>
>
> >> What Greg was asking about, as far as I can tell, is a way to get
> >> CUPS to tell him that network-location information - so that he, as
> >> someone external to the printing system, could then apply that
> >>
On 2022-04-10 at 08:10, 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:
>>> And how do you accomplish that? Its automatically installed
>>> AFAIK. And once installed, apt will not remove it without
>>> destroying
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 accomplish that? Its automatically installed AFAIK.
> > And once
On Sun, Apr 10, 2022 at 07:46:37AM -0400, gene heskett wrote:
> On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
>
> > AVAHI_DAEMON_DETECT_LOCAL=0 into some /etc/default/avahi-daemon.
>
> Checking all my machines, all but one was set to 1, fixed the others and
> redid the initramfs
On Sun, Apr 10, 2022 at 07:17:42AM -0400, 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 accomplish that? Its automatically installed AFAIK.
> > And once
On Sun, Apr 10, 2022 at 07:08:36AM -0400, gene heskett wrote:
> On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
[...]
> > be putting AVAHI_DAEMON_DETECT_LOCAL=0 into some
> > /etc/default/avahi-daemon.
>
> Then whyintarnation does it not say that in what serves as a man page?
On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
> AVAHI_DAEMON_DETECT_LOCAL=0 into some /etc/default/avahi-daemon.
Checking all my machines, all but one was set to 1, fixed the others and
redid the initramfs as it said in 2 of the 5, in that file.
Thank you for that Tomas, now
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 accomplish that? Its automatically installed AFAIK.
> And once installed, apt will not remove it without destroying the
> install. rm or
On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
> On Sun, Apr 10, 2022 at 05:46:35AM -0400, gene heskett wrote:
>
> [...]
>
> > Then why, after a decade and change of bitching about it because it
> > insists on putting a 169.254.xx,yy address in ones routing table that
> > only
On Sun, Apr 10, 2022 at 05:46:35AM -0400, gene heskett wrote:
[...]
> Then why, after a decade and change of bitching about it because it
> insists on putting a 169.254.xx,yy address in ones routing table that
> only removing avahi fixes, has it not been fixed?
This would be an IPv4
then send jobs to that
> > printer via that computer, which is de-facto a print server for that
> > printer.
> >
> > Do you know whether CUPS is capable of interacting with printers
> > which
> > are shared in that way? (This is a tangent
er not directly to the network, but locally to a
> particular computer, and then configure that computer to advertise the
> printer over the network. Other computers can then send jobs to that
> printer via that computer, which is de-facto a print server for that
> printer.
>
> Do
* 2022-04-10 03:59:25+0100, mick crane wrote:
> On 2022-04-10 01:21, The Wanderer wrote:
>>> avahi-browse -rt _ipp._tcp
>>
>> Does that get the information from CUPS?
>
> With printer connected via other PC (CUPS print server) there is no
> output from &qu
On 2022-04-10 01:21, The Wanderer wrote:
avahi-browse -rt _ipp._tcp
Does that get the information from CUPS?
With printer connected via other PC (CUPS print server) there is no
output from "avahi-browse -rt _ipp._tcp"
mick
--
Key ID4BFEBB31
I do not reply to every point you make.
I don't strongly mind that, no. A few of them were probably rephrasings
of the same thing in different ways.
>> On 2022-04-08 at 18:44, Brian wrote:
>> What Greg was asking about, as far as I can tell, is a way to get
>> CUPS to tell
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:/
an't recall all of the information that
was on the "card" (folded sheet of paper actually). There was
something that looked like a Windows pathname, but it did not match
any of the names presented by CUPS, and I don't remember exactly what
it said.
an IP address. Printing to it doesn't. The wrong path was taken.
That's, strictly speaking, right; in the OP's case, it'd been
helpful to finding the printed rag, though.
> > In the bus's case, perhaps there is a big sign on the parking lot
> > "NEUF-BRISACH". There, that's your I
On Fri 08 Apr 2022 at 19:57:53 -0500, David Wright wrote:
> On Fri 08 Apr 2022 at 23:44:29 (+0100), Brian wrote:
> > On Fri 08 Apr 2022 at 16:20:54 -0400, The Wanderer wrote:
>
> > > What I understood Greg as asking about is how to get CUPS to *tell* you
> > > what
g system has, or must have, any knowledge of the printer's
> location.
>
> Even if the printing system doesn't have any knowledge of the printer's
> physical location, it must still have some knowledge of the printer's
> *network* location, in the form of an IP address
parking lot
> "NEUF-BRISACH". There, that's your IP address.
>
> Back to the printers, I'm horrified at the idea that CUPS doesn't
> tell you the IP address it thinks the printer is at. It's what
> I call "authoritarian software", where the software thinks it's
>
and click on my printer it
> > > > shows amongst other information:
> > > >
> > > > Connection: socket://192.168.2.3:9100
> > >
> > > OK. That's the destination.
> > > >
> > > > In case it got that IP address because
IP address.
Back to the printers, I'm horrified at the idea that CUPS doesn't
tell you the IP address it thinks the printer is at. It's what
I call "authoritarian software", where the software thinks it's
smarter than me. Don't get me wrong, I like comfort like the next
guy, but I don't like
On 2022-04-08 17:10, Greg Wooledge wrote:
If you don't want to read the background information, the question is:
How is one *supposed* to figure out which autodetected printer is the
correct one, apart from trial and error?
I think you'd set up a printer on your machine with
On Fri 08 Apr 2022 at 23:44:29 (+0100), Brian wrote:
> On Fri 08 Apr 2022 at 16:20:54 -0400, The Wanderer wrote:
> > What I understood Greg as asking about is how to get CUPS to *tell* you
> > what the IP address it knows about for a given printer object is. That
&
em has, or must have, any knowledge of the printer's
location.
Even if the printing system doesn't have any knowledge of the printer's
physical location, it must still have some knowledge of the printer's
*network* location, in the form of an IP address (or other routing
information, such as in t
inter's IP address before I even touched CUPS. It was
prominently displayed on the device itself. It was the one thing I
didn't have to guess at during the entire adventure.(*)
In all of my experience working with printers BEFORE the CUPS/Avahi
thing came along, knowing the IP address of t
gt; > > Connection: socket://192.168.2.3:9100
> >
> > OK. That's the destination.
> > >
> > > In case it got that IP address because I configured it that way, I just
> > > tried it on another computer that didn't previously have CUPS on until
> > >
it. You're
> >> just screwed, and must resort to trial and error to figure out
> >> where the printers are. Even though CUPS can magically contact the
> >> printers, it will refuse to tell you how it does that, because of
> >> some kind of policy decision.
> >
On Fri, Apr 08, 2022 at 08:52:26PM +0100, Brian wrote:
> You didn't like my bus analogy, did you?
I don't think it's a very good analogy for this situation.
> What makes you think that knowing an IP address tells you where
> any machine of any description is located?
Because the device is (was)
atever the server/printer is advertising.
>>
>> So... if your corporate network is not set up in the way that
>> Brian expects, there is simply nothing you can do about it. You're
>> just screwed, and must resort to trial and error to figure out
>> where the printers are.
case it got that IP address because I configured it that way, I just
> > tried it on another computer that didn't previously have CUPS on until
> > I just installed it and it shows the same for an auto discovered
> > printer.
>
> Do you find that surprising? The destination ha
On Fri, Apr 08, 2022 at 08:24:00PM +0100, Brian wrote:
> avahi-browse -rt _ipp._tcp
>
> is better.
That one actually works. It completes in under 1 second, and it
includes IP addresses in its output.
Out of curiosity, I tried omitting the -r option, to try to figure out
what "resolve" means
is simply nothing you can do about it. You're just
> screwed, and must resort to trial and error to figure out where
> the printers are. Even though CUPS can magically contact the printers,
> it will refuse to tell you how it does that, because of some kind of
> policy decision.
You didn
On Fri 08 Apr 2022 at 15:30:13 (-0400), Greg Wooledge wrote:
> On Fri, Apr 08, 2022 at 08:28:31PM +0200, didier gaumet wrote:
> > CLI:
> >
> > # avahi-browse -r _print-caps._tcp
> > (from the avahi-utils package)
>
> I tried this with and without the -r (which according to the man page
> asks
is simply nothing you can do about it. You're just
> screwed, and must resort to trial and error to figure out where
> the printers are. Even though CUPS can magically contact the printers,
> it will refuse to tell you how it does that, because of some kind of
> policy decision.
It's an od
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://localhost:631/ then clicking the 'Admininitation' tab at the top
followed by the 'Manage Printers' button on the page that showed.
Here is what I have
On Fri, Apr 08, 2022 at 08:28:31PM +0200, didier gaumet wrote:
> CLI:
>
> # avahi-browse -r _print-caps._tcp
> (from the avahi-utils package)
I tried this with and without the -r (which according to the man page
asks to "resolve services", but it doesn't say what kind of resolution
it's doing).
On Fri 08 Apr 2022 at 20:08:22 (+0100), Brian wrote:
> On Fri 08 Apr 2022 at 12:10:37 -0400, Greg Wooledge wrote:
> > How is one *supposed* to figure out which autodetected printer is the
> > correct one, apart from trial and error?
>
> Fancy an analogy?
>
> My local bus intercange has display
On Fri 08 Apr 2022 at 20:28:31 +0200, didier gaumet wrote:
> Hello Greg,
>
> Perhaps, try:
>
> GUI:
>
> avahi-discover from the avahi-discover package presents a network tree:
> you can find the IP adresses of the printers
>
> CLI:
>
> # avahi-browse -r _print-caps._tcp
> (from the
the printers are. Even though CUPS can magically contact the printers,
it will refuse to tell you how it does that, because of some kind of
policy decision.
ocalhost:631/printers/ and click on my printer it
> shows amongst other information:
>
> Connection: socket://192.168.2.3:9100
OK. That's the destination.
>
> In case it got that IP address because I configured it that way, I just
> tried it on another computer that didn't
On Fri 08 Apr 2022 at 12:10:37 -0400, Greg Wooledge wrote:
[Misconceptions snipped. It would take too long to comment on and refute
every single one of them, interesting though they may be.]
> After all this, I have two final comments:
>
> 1) To whomever received two surprise printer test
Hello Greg,
Perhaps, try:
GUI:
avahi-discover from the avahi-discover package presents a network tree:
you can find the IP adresses of the printers
CLI:
# avahi-browse -r _print-caps._tcp
(from the avahi-utils package)
In my case it's sufficient to detect my network printer but I do not
detected 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://localhost:631/ then clicking the 'Admininitation' tab at the top
> followed by the 'Manage Printers' button on the
host:631/printers/
I should say I got to that URL from the CUPs interface at
http://localhost:631/ then clicking the 'Admininitation' tab at the top
followed by the 'Manage Printers' button on the page that showed.
--
Tixy
101 - 200 of 7728 matches
Mail list logo
