Chris Green wrote:
> I have just [re]installed an HP Laserjet Pro M15w printer on my T470
> laptop which runs Debian 12.
>
> The CUPS test page prints succesfully but nothing else seems able to
> print. The CUPS Print Status window shows the job for a few seconds
> but then it flashes the red cr
Hi,
On Fri, Sep 27, 2024 at 03:21:21PM +0200, Ralph Aichinger wrote:
> oh well, the sensationalism around this is probably overdone
> nevertheless.
As far as I understand it, you would need cups-browsed running on an
unfirewalled host in which case an attacker could create a bogus printer
that ex
On Fri, Sep 27, 2024 at 01:16:07PM +, Andy Smith wrote:
> I put "CVE-2024-47176" in to that and the first result was:
>
> https://security-tracker.debian.org/tracker/CVE-2024-47176
Thanks, Andy. Not quite the information i had hoped for (that stuff
not being relevant for Debian ;), but oh
Hi,
On Fri, Sep 27, 2024 at 02:22:10PM +0200, Ralph Aichinger wrote:
> Is there some place tracking CVE 2024-47176 and related ones in Debian?
I put "Debian CVE" in to my favourite search engine and the first result
was:
https://security-tracker.debian.org/tracker/
I put "CVE-2024-47176" in
I want to thank Joe B for the suggestion
to also install the printer-driver-escpr pkg, and David Wright
to whom I want to say that Epson Connect
is the app for Smartphones Android that I have used to print in the
last few days by transferring files from the PC to the Smartphone.
As for Thorsten
Hello,
On all the distros I've been on, the driver I needed was part of the
epson-inkjet-printer-escpr package. install that close everything go
back to cups login add printer once you are there you should be able
to see your printer (hopefully network printer) once done then you
should be able to
On Tue 20 Aug 2024 at 17:27:37 (+0200), sentini...@virgilio.it wrote:
> > Il 20/08/2024 04:53 CEST David Wright ha scritto:
> >
> > What's the output from:
> >
> > $ driverless
> >
> > (This is normally step one in configuring a printer.)
>
> aldo@aldomaggi:~$ driverless
> ipps://EPSON%20ET-2
Thank you for answering!
> Il 20/08/2024 04:53 CEST David Wright ha scritto:
>
> What's the output from:
>
> $ driverless
>
> (This is normally step one in configuring a printer.)
aldo@aldomaggi:~$ driverless
ipps://EPSON%20ET-2810%20Series._ipps._tcp.local/
>
> Cheers,
> David.
On Sun 18 Aug 2024 at 18:44:30 (+0200), sentini...@virgilio.it wrote:
[ … ]
> At the “connection” line it says: Connection:
> ipps://EPSON%20ET-2810%20Series._ipps._tcp.local/
[ … ]
> in the next screen it tells me: "Unable to add printer: cups-driver failed to
> get PPD file" - see error_log for
I don't have access to a Linux desktop at the moment to workout the
exact steps. But since you're already familiar with the CUPS Web
Interface, it's just a matter of changing the "Connection" to
AppSocket/JetDirect.
So select the printer, then the "Administration" button, "Modify
Printer" and
I just had a similar issue yesterday with an HP Office Pro 7740. I ended
up installing using the socket (port 9100) interface.
...
Philippe
--
The trouble with common sense is that it is so uncommon.
(Anonymous)
On 8/18/24 12:44, sentini...@virgilio.it wrote:
New installation of Debian, on
On Mon, Dec 25, 2023 at 09:36:44PM -0500, Stefan Monnier wrote:
I copied the file to another computer in the LAN, ran LaTeX and dvips,
and sent it to the same printer, but the file hung at the same spot.
Any chance you can use `pdflatex` instead of `latex + dvips`?
Have you tried to manually c
On Mon, Dec 25, 2023 at 09:36:44PM -0500, Stefan Monnier wrote:
I copied the file to another computer in the LAN, ran LaTeX and dvips,
and sent it to the same printer, but the file hung at the same spot.
Any chance you can use `pdflatex` instead of `latex + dvips`?
Have you tried to manually c
> I copied the file to another computer in the LAN, ran LaTeX and dvips,
> and sent it to the same printer, but the file hung at the same spot.
Any chance you can use `pdflatex` instead of `latex + dvips`?
Have you tried to manually convert the PS to PDF before sending to
the printer? or to conve
gene heskett wrote:
...
> Thanks.
when someone ignores common sense after frequently
shooting themself in the foot there's not much more
i can do for them.
i suggest a system management approach which involves
snapshots (use git on the whole thing if you have to
or some partition image copie
On 8/25/23 04:49, gene heskett wrote:
On 8/24/23 13:00, gene heskett wrote:
ping
never mind the ping, I found that ff can't print it even using system
dialog, but okular can. So thats another data point.
Greeting all;
bookworm, upto date, cups 2.4.2 installed.
I goto print a doc on a 3d prin
On 8/24/23 13:00, gene heskett wrote:
ping
Greeting all;
bookworm, upto date, cups 2.4.2 installed.
I goto print a doc on a 3d printer control card, and can't print a pdf
from firefox.
So I goto localhost:631, no printers! I had 4 the day before yesterday,
and used 2 of them.
So I goto add
On Sat, 20 May 2023 08:24:39 +0200
john doe wrote:
> >
> > .home.arpa ? I had never heard of it until you mentioned it. You are
> > suggesting that I change every reference to localdomain to
> > .home.arpa? Implementing that change is going to be a major pain in
> > the arse.
>
> My idea was t
On 5/17/23 21:56, Charles Curley wrote:
On Wed, 17 May 2023 19:21:23 +0200
john doe wrote:
A few things, that I spotted while reading this thread and Im' not
sure if you got everything working!
Thank you. No, I don't have everything working.
- MDNS is using .local
- .localdomain should be
On Wed, 17 May 2023 19:21:23 +0200
john doe wrote:
> A few things, that I spotted while reading this thread and Im' not
> sure if you got everything working!
Thank you. No, I don't have everything working.
>
> - MDNS is using .local
> - .localdomain should be moved to .home.arpa (see RFC)! :)
On 5/15/23 16:46, Charles Curley wrote:
On Mon, 15 May 2023 07:31:29 -0600
Charles Curley wrote:
I solved that one. I had closed TCP port 9100. Opening that up on the
server got me running. However, that did not solve the problem for the
other two protocols.
Correction. That didn't solve it.
On Mon 15 May 2023 at 18:29:12 +0100, Brian wrote:
> On Mon 15 May 2023 at 16:33:42 +0100, Brian wrote:
>
> [...]
>
> > Good. The issue is solved, but how do you feel about being adventurous?
> >
> > Assuming you have deleted the three non-working queues,'lpstat -a' and
> > s-c-p should show on
Charles Curley wrote:
> On Mon, 15 May 2023 20:30:38 -0400
> Timothy M Butterworth wrote:
>
> > > I also have an ancient i386 IBM R51 running Bookworm, dragon. On
> > > dragon, using system-config-printer, I can see the printer
> > > automagically discovered. I can open up the queue window for t
On Mon, 15 May 2023 20:30:38 -0400
Timothy M Butterworth wrote:
> > I also have an ancient i386 IBM R51 running Bookworm, dragon. On
> > dragon, using system-config-printer, I can see the printer
> > automagically discovered. I can open up the queue window for the
> > printer, and request a test
On Sun, May 14, 2023 at 1:30 PM Charles Curley <
charlescur...@charlescurley.com> wrote:
> I have an HP HP_LaserJet_MFP_M234sdw_C0FB67_USB_, one of those modern
> "no driver" multifunction printers. It works fine on Bullseye. I have
> the printer hooked up via USB to a server, hawk, and it prints
On 5/15/23 14:32, Charles Curley wrote:
On Mon, 15 May 2023 12:18:56 -0400
gene heskett wrote:
this is interesting Brian, but how do I adapt it to my brother
printers? All I can get by substituting the queue name M234 is
"printer or class does not exist".
Right. M234 is the name assigned pre
On Mon, 15 May 2023 12:18:56 -0400
gene heskett wrote:
> this is interesting Brian, but how do I adapt it to my brother
> printers? All I can get by substituting the queue name M234 is
> "printer or class does not exist".
Right. M234 is the name assigned previously. You get the URI(s) of
availab
On 5/15/23 07:10, Brian wrote:
On Sun 14 May 2023 at 20:57:23 -0600, Charles Curley wrote:
On Sun, 14 May 2023 23:30:25 +0100
Brian wrote:
On Sun 14 May 2023 at 14:04:51 -0600, Charles Curley wrote:
We take it that dragon, hawk and the printer are network connected.
Give what you get f
On Mon 15 May 2023 at 08:24:28 -0600, Charles Curley wrote:
> On Mon, 15 May 2023 12:09:33 +0100
> Brian wrote:
[...]
> Ah, OK. So can I get rid of the three queues and print directly to the
> printer?
Indeed you can! 'lpstat -l -e' should show only the printer on the network
and a working loc
On Mon, 15 May 2023 15:42:51 +0100
Brian wrote:
> On Mon 15 May 2023 at 08:07:12 -0600, Charles Curley wrote:
>
> [...]
> [...]
> >
> > Possibly just legacy habits. I'm not accustomed to this automation.
> >
>
> Possibly. You are not alone in this. The thinking appears to be: "I
> hav
On Mon, 15 May 2023 07:31:29 -0600
Charles Curley wrote:
> I solved that one. I had closed TCP port 9100. Opening that up on the
> server got me running. However, that did not solve the problem for the
> other two protocols.
Correction. That didn't solve it. I realized that port 9100 on hawk is
On Mon 15 May 2023 at 08:07:12 -0600, Charles Curley wrote:
> On Mon, 15 May 2023 14:22:14 +0100
> Brian wrote:
> >
> > Consider: the printer can be discovered via mDNS/DNS-SD by all
> > machines on the network. ideapc does this and hasn't any difficulty
> > printing. So why set up a server when
On Mon, 15 May 2023 12:09:33 +0100
Brian wrote:
> Useful data but an aside first:
>
> The pdl= key lacks image/urf. HP claims AirPrint support for the
> device (URF=V1.4,...). It looks like you have been sold a pup. A
> firmware update?
I will look into that later today.
>
> > root@dragon:~#
On Mon, 15 May 2023 14:22:14 +0100
Brian wrote:
> > Not that I know of.
>
> Blocking port 5353 (mdns) is not unknown.
True. It is open (udp) on hawk (server) and ideapc, where I am running
shorewall (iptables). dragon has firewalld, which simply shows the
service, mdns, as open, but does not
On Sun, 14 May 2023 14:04:51 -0600
Charles Curley wrote:
> I also enabled "port 9100" printing on the printer, and went directly
> to it:
>
> socket://hpm234ethernet.localdomain:9100
>
> The printer spun its wheels, reported an error and stopped without
> printing. Nothing in the event log.
I
On Sun 14 May 2023 at 14:04:51 -0600, Charles Curley wrote:
> On Sun, 14 May 2023 19:48:07 +0200
> john doe wrote:
>
> > On 5/14/23 19:29, Charles Curley wrote:
> > [...]
> >
> > The below, is what I would try:
> >
> > - On the non-working client, Are you restricting outbound traffic at
> >
On Sun 14 May 2023 at 20:57:23 -0600, Charles Curley wrote:
> On Sun, 14 May 2023 23:30:25 +0100
> Brian wrote:
>
> > On Sun 14 May 2023 at 14:04:51 -0600, Charles Curley wrote:
>
>
> >
> > We take it that dragon, hawk and the printer are network connected.
> >
> > Give what you get from dra
On Sun, 14 May 2023 23:30:25 +0100
Brian wrote:
> On Sun 14 May 2023 at 14:04:51 -0600, Charles Curley wrote:
>
> We take it that dragon, hawk and the printer are network connected.
>
> Give what you get from dragon with
>
> avahi-browse -rt _ipp._tcp
> avahi-browse -rt _uscan._tcp
> d
On Sun 14 May 2023 at 14:04:51 -0600, Charles Curley wrote:
> On Sun, 14 May 2023 19:48:07 +0200
> john doe wrote:
>
> > On 5/14/23 19:29, Charles Curley wrote:
> > [...]
> >
> > The below, is what I would try:
> >
> > - On the non-working client, Are you restricting outbound traffic at
> >
On Sun, 14 May 2023 19:48:07 +0200
john doe wrote:
> On 5/14/23 19:29, Charles Curley wrote:
> [...]
>
> The below, is what I would try:
>
> - On the non-working client, Are you restricting outbound traffic at
> all
Not that I know of.
> or for testing purposes can you disable the FW?
I
On 5/14/23 19:29, Charles Curley wrote:
I have an HP HP_LaserJet_MFP_M234sdw_C0FB67_USB_, one of those modern
"no driver" multifunction printers. It works fine on Bullseye. I have
the printer hooked up via USB to a server, hawk, and it prints just
fine.
I have a client, ideapc, which sees the pr
On Sat 8 Apr 2023, at 22:12, gene heskett wrote:
> On 4/8/23 02:40, Gareth Evans wrote:
>> On Sat 8 Apr 2023, at 03:20, gene heskett wrote:
>>> 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?
>>
On 4/8/23 02:40, Gareth Evans wrote:
On Sat 8 Apr 2023, at 03:20, gene heskett wrote:
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 a
On 4/8/23 02:40, Gareth Evans wrote:
On Sat 8 Apr 2023, at 03:20, gene heskett wrote:
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 a
On Sat 8 Apr 2023, at 03:20, gene heskett wrote:
> 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 pri
On Sun 26 Feb 2023 at 17:09:51 +0300, Reco wrote:
> 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 woul
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
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 +
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:
>
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
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
On Fri 24 Feb 2023 at 12:58:15 -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 single-page PDF from
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
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
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 |
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
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/printers/Canon_LBP712C_UFR_II_
> > ipp://Cano
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/
This is a print queue,
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
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
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
On 2/16/23 15:33, Greg Wooledge wrote:
On Thu, Feb 16, 2023 at 06:57:46PM +0200, Teemu Likonen wrote:
Here is my version which I suggest turning into a shell alias, function
or script:
avahi-browse -atrp 2>/dev/null | awk -F\; \
'$1 == "=" { printf "%-23s %-26s %5s %s\n",$7,$8,$9,
On Thu, Feb 16, 2023 at 06:57:46PM +0200, Teemu Likonen wrote:
> Here is my version which I suggest turning into a shell alias, function
> or script:
>
> avahi-browse -atrp 2>/dev/null | awk -F\; \
> '$1 == "=" { printf "%-23s %-26s %5s %s\n",$7,$8,$9,$5 }'
>
> It should print lines l
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
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
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
On Thu 16 Feb 2023 at 10:41:33 -0500, Greg Wooledge wrote:
[...]
> 3) Also suggested: driverless
>Here's what I get this year:
>
>wooledg:~$ driverless
>ipp://Canon%20LBP712Cdn%20(db%3Ac0%3Ad3)._ipp._tcp.local/
>
>That's all. And no, that's not the right printer. That's the on
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...
> >
> >
* 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
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
On 2/16/23 08:41, Greg Wooledge wrote:
It's tax season again, so once again I am putting myself through the
utter hell that is attempting to print my city's Income Tax Forms.
(Yes, this is mandatory. No, they do not accept electronic submissions.
You must use paper and ink. Yes, they require y
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
It's tax season again, so once again I am putting myself through the
utter hell that is attempting to print my city's Income Tax Forms.
(Yes, this is mandatory. No, they do not accept electronic submissions.
You must use paper and ink. Yes, they require you to print your own
forms. No, they wil
On Sun 05 Feb 2023 at 20:52:42 +, Russell L. Harris wrote:
> Fresh installation of Debian 11.6 on Dell Vostro 200 (Intel Core 2).
>
> The Vostro 200 is being added to a home LAN with Debian 11.6 running
> on a nondescript desktop (amd64) and a HP Laserjet P3015 Postscript
> (Ethernet). The a
On 2/5/23 21:52, Russell L. Harris wrote:
Fresh installation of Debian 11.6 on Dell Vostro 200 (Intel Core 2).
The Vostro 200 is being added to a home LAN with Debian 11.6 running
on a nondescript desktop (amd64) and a HP Laserjet P3015 Postscript
(Ethernet). The amd64 machine works perfectly w
On 7/14/22 13:08, Brian wrote:
On Thu 14 Jul 2022 at 11:56:10 -0400, gene heskett wrote:
On 7/14/22 05:19, Brian wrote:
[...]
But now the "add printer" just re-configures the existing one. "Add"
does not make a new profile. I need both profiles to show up in both
firefox's, print dialog, an
On Thu 14 Jul 2022 at 11:56:10 -0400, gene heskett wrote:
> On 7/14/22 05:19, Brian wrote:
> > On Wed 13 Jul 2022 at 21:31:24 -0400, gene heskett wrote:
> >
> > > On 7/13/22 19:27, Brian wrote:
> > > > On Wed 13 Jul 2022 at 16:10:56 -0400, gene heskett wrote:
> > > >
> > > > > On 7/13/22 15:14,
On 7/14/22 05:19, Brian wrote:
On Wed 13 Jul 2022 at 21:31:24 -0400, gene heskett wrote:
On 7/13/22 19:27, Brian wrote:
On Wed 13 Jul 2022 at 16:10:56 -0400, gene heskett wrote:
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
On Wed 13 Jul 2022 at 21:31:24 -0400, gene heskett wrote:
> On 7/13/22 19:27, Brian wrote:
> > On Wed 13 Jul 2022 at 16:10:56 -0400, gene heskett wrote:
> >
> > > On 7/13/22 15:14, Brian wrote:
> > > > On Wed 13 Jul 2022 at 13:21:07 -0400, gene heskett wrote:
> > > >
> > > > [Broken lines mended
On Thu 14 Jul 2022, at 02:08, gene heskett wrote:
> it printed a test page
Good. I'm afraid I don't know of a workaround for tray selection.
This site
https://productz.com/en/brother-mfc-j6920dw/p/LZbAV
suggests the printer concerned is airprint/fax-capable, and given:
> On Wed 13 Jul 2022
On 7/13/22 19:27, Brian wrote:
On Wed 13 Jul 2022 at 16:10:56 -0400, gene heskett wrote:
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.
Yet another part of the compting ex
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 avai
On Wed 13 Jul 2022 at 16:10:56 -0400, gene heskett wrote:
> 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.
Yet another part of the compting experience tou are
> 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 h
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 the drive
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/cupsd.conf
>>
>> to disable automatic queue creation for autodet
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 tha
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? Is that a separa
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 work, preventing me from using the
> > prin
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 at all.
> >
> > So how do I
> 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 the driverless junk? Is that a se
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 the printer at all
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 a separate package that
> is remov
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
that is
On Mon 20 Jun 2022, at 23:50, Gareth Evans wrote:
> On Mon 20 Jun 2022, at 23:31, Gareth Evans wrote:
>> 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:5
On Mon 20 Jun 2022, at 23:31, Gareth Evans wrote:
> 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 pri
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 discovering its
URI. CUPS gets the URI vi
On Mon 20 Jun 2022 at 19:49:18 +0100, Brian wrote:
Please forget about this mai. I pressed the wrong key. Never done that
before!
> 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?
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 mechanisms.
>
> CUPS could run discovery on
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 is an
>>> on-demand or manual queu
1 - 100 of 1046 matches
Mail list logo
