On 2023-05-11 18:24:39 -0400, Greg Wooledge wrote:
> On Thu, May 11, 2023 at 11:58:56PM +0200, Vincent Lefevre wrote:
> > On 2023-05-11 12:08:01 -0400, gene heskett wrote:
> > > Aha Got it, geany evince okular etc can now print from bpi54! Removing
> > > the Listen localhost:631 directive from
On Thu, May 11, 2023 at 11:58:56PM +0200, Vincent Lefevre wrote:
> On 2023-05-11 12:08:01 -0400, gene heskett wrote:
> > Aha Got it, geany evince okular etc can now print from bpi54! Removing
> > the Listen localhost:631 directive from /etc/cups/cupsd.conf and inserting a
> >
> > Listen
On 2023-05-11 12:08:01 -0400, gene heskett wrote:
> Aha Got it, geany evince okular etc can now print from bpi54! Removing
> the Listen localhost:631 directive from /etc/cups/cupsd.conf and inserting a
>
> Listen 192.168.xx.yy:631
>
> made the localhost:631/printers on this machine show up
On Thu 11 May 2023 at 12:08:01 -0400, gene heskett wrote:
> On 5/11/23 07:07, Brian wrote:
> > On Wed 10 May 2023 at 16:02:43 -0400, gene heskett wrote:
> >
> > > On 5/10/23 14:22, Brian wrote:
> > > > On Wed 10 May 2023 at 13:18:07 -0400, gene heskett wrote:
> > > >
> > > > > On 5/10/23 11:29,
On 5/11/23 07:09, Brian wrote:
On Wed 10 May 2023 at 15:51:53 -0400, gene heskett wrote:
On 5/10/23 14:22, Brian wrote:
[...]
After appreciating that bpi51 has libnss-mdns installed, you might discard any
assumption that nsswitch.conf on bpi54 has the same contents.
I don't believe any
On 5/11/23 07:07, Brian wrote:
On Wed 10 May 2023 at 16:02:43 -0400, gene heskett wrote:
On 5/10/23 14:22, Brian wrote:
On Wed 10 May 2023 at 13:18:07 -0400, gene heskett wrote:
On 5/10/23 11:29, Brian wrote:
On Wed 10 May 2023 at 10:04:47 -0400, gene heskett wrote:
On 5/10/23 08:17,
gene heskett wrote:
> On 5/10/23 14:22, Brian wrote:
> > A link would be ever so useful.
>
> send browser to cups.org, click help, in right pane, click "printer
> sharing", scroll down about a screenfull to Automatic using IPP
So the answer to Brian's question is
On 5/10/23 14:22, Brian wrote:
On Wed 10 May 2023 at 13:18:07 -0400, gene heskett wrote:
On 5/10/23 11:29, Brian wrote:
On Wed 10 May 2023 at 10:04:47 -0400, gene heskett wrote:
On 5/10/23 08:17, Brian wrote:
[...]
Is /etc/cups/client,conf really, really needed?
That is the first
On 5/10/23 14:22, Brian wrote:
On Wed 10 May 2023 at 13:18:07 -0400, gene heskett wrote:
On 5/10/23 11:29, Brian wrote:
On Wed 10 May 2023 at 10:04:47 -0400, gene heskett wrote:
On 5/10/23 08:17, Brian wrote:
[...]
Is /etc/cups/client,conf really, really needed?
That is the first
On Wed 10 May 2023 at 13:18:07 -0400, gene heskett wrote:
> On 5/10/23 11:29, Brian wrote:
> > On Wed 10 May 2023 at 10:04:47 -0400, gene heskett wrote:
> >
> > > On 5/10/23 08:17, Brian wrote:
>
> > [...]
> > Is /etc/cups/client,conf really, really needed?
> >
> That is the first thing cups
On 5/10/23 11:29, Brian wrote:
On Wed 10 May 2023 at 10:04:47 -0400, gene heskett wrote:
On 5/10/23 08:17, Brian wrote:
[...]
Your nsswitch.conf line implies libnss-mymacines and libnss-mymhostname are
used.
They have man pages to help you decide what parts they play on bpi54.
They were
On Wed 10 May 2023 at 10:04:47 -0400, gene heskett wrote:
> On 5/10/23 08:17, Brian wrote:
[...]
> > Your nsswitch.conf line implies libnss-mymacines and libnss-mymhostname are
> > used.
> > They have man pages to help you decide what parts they play on bpi54.
>
> They were not installed, and
On Wed, May 10, 2023 at 10:04:47AM -0400, gene heskett wrote:
> On 5/10/23 08:17, Brian wrote:
[...]
> > Your nsswitch.conf line implies libnss-mymacines and libnss-mymhostname are
> > used.
> > They have man pages to help you decide what parts they play on bpi54.
>
> They were not installed,
On 5/10/23 08:17, Brian wrote:
On Tue 09 May 2023 at 16:49:22 -0400, gene heskett wrote:
On 5/9/23 07:12, Greg Wooledge wrote:
On Tue, May 09, 2023 at 04:06:14AM -0400, gene heskett wrote:
I think you have said resolv.conf Search directive doesn't work but
nsswitch.conf was mentioned and
On Tue 09 May 2023 at 16:49:22 -0400, gene heskett wrote:
> On 5/9/23 07:12, Greg Wooledge wrote:
> > On Tue, May 09, 2023 at 04:06:14AM -0400, gene heskett wrote:
> > > I think you have said resolv.conf Search directive doesn't work but
> > > nsswitch.conf was mentioned and there is a diff
On 5/9/23 07:12, Greg Wooledge wrote:
On Tue, May 09, 2023 at 04:06:14AM -0400, gene heskett wrote:
I think you have said resolv.conf Search directive doesn't work but
nsswitch.conf was mentioned and there is a diff between this machine and one
of the arms. So what do I put in nsswitch.conf to
On Tue, May 09, 2023 at 04:06:14AM -0400, gene heskett wrote:
> I think you have said resolv.conf Search directive doesn't work but
> nsswitch.conf was mentioned and there is a diff between this machine and one
> of the arms. So what do I put in nsswitch.conf to make cups search the hosts
> file
On 5/8/23 07:49, Brian wrote:
On Mon 08 May 2023 at 00:23:43 -0400, gene heskett wrote:
Brian, I found the secret sauce. Armed with the knowledge that Mike had
moved, I found his new site, and found the answer in 5 minutes under the
"printer sharing" link. Something is broken when using a
On 5/8/23 16:57, gene heskett wrote:
On 5/8/23 07:49, Brian wrote:
On Mon 08 May 2023 at 00:23:43 -0400, gene heskett wrote:
On 5/7/23 12:48, Brian wrote:
[...]
Please give 'lpstat -t' for bpi51 (bullseye) and a buster machine.
gene@bpi51:~$ lpstat -t
scheduler is running
system default
On 5/8/23 07:49, Brian wrote:
On Mon 08 May 2023 at 00:23:43 -0400, gene heskett wrote:
On 5/7/23 12:48, Brian wrote:
[...]
Please give 'lpstat -t' for bpi51 (bullseye) and a buster machine.
gene@bpi51:~$ lpstat -t
scheduler is running
system default destination: PDF
device for
On Mon 08 May 2023 at 00:23:43 -0400, gene heskett wrote:
> On 5/7/23 12:48, Brian wrote:
[...]
> > Please give 'lpstat -t' for bpi51 (bullseye) and a buster machine.
> gene@bpi51:~$ lpstat -t
> scheduler is running
> system default destination: PDF
> device for HLL2320D-RAW:
On 5/7/23 13:34, Eduardo M KALINOWSKI wrote:
On 07/05/2023 12:26, gene heskett wrote:
There is a light at the end of this dark tunnel, IF you are willing to
change the brand name on the printer. But in your case you've already
done that. So now do a search for brotherusa, go there and
On 5/7/23 12:48, Brian wrote:
On Sun 07 May 2023 at 11:26:05 -0400, gene heskett wrote:
On 5/6/23 19:29, Alex King wrote:
Printing on Linux is poor. CUPS is poor. It doesn't work for some (a
lot?) of people.
I have a Brother HL-L2300D printer. It is connected to my (Debian
bullseye)
On 07/05/2023 12:26, gene heskett wrote:
There is a light at the end of this dark tunnel, IF you are willing to
change the brand name on the printer. But in your case you've already
done that. So now do a search for brotherusa, go there and download
their driver installer, unpack it, run it
On Sun 07 May 2023 at 11:26:05 -0400, gene heskett wrote:
> On 5/6/23 19:29, Alex King wrote:
> > Printing on Linux is poor. CUPS is poor. It doesn't work for some (a
> > lot?) of people.
> >
> > I have a Brother HL-L2300D printer. It is connected to my (Debian
> > bullseye) workstation by
On 5/6/23 19:29, Alex King wrote:
Printing on Linux is poor. CUPS is poor. It doesn't work for some (a
lot?) of people.
I have a Brother HL-L2300D printer. It is connected to my (Debian
bullseye) workstation by USB. I have CUPS installed.
My printer prints sometime. Other times, it
On 06/05/2023 20:02, Alex King wrote:
Implying the user is at fault (which Brian isn't necessarily doing
here,) or acting surprised when someone has trouble printing, is like
gaslighting. Maybe it works OK for you, but please understand that is
not the general case.
Take not of this, it'll
On Sat May 6 21:11:09 2023 Alex King wrote:
> Printing on Linux is poor. CUPS is poor. It doesn't work for some (a
> lot?) of people.
>
> I have a Brother HL-L2300D printer. It is connected to my (Debian
> bullseye) workstation by USB. I have CUPS installed.
>
> My printer prints sometime.
Alex King writes:
> Printing on Linux is poor. CUPS is poor. It doesn't work for some (a lot?)
> of people.
>
> I have a Brother HL-L2300D printer. It is connected to my (Debian bullseye)
> workstation by USB. I have CUPS installed.
> (...)
Hellow Alex!
In South Korea, most people does
On Sun, 2023-05-07 at 11:02 +1200, Alex King wrote:
> Printing on Linux is poor. CUPS is poor. It doesn't work for some
> (a
> lot?) of people.
I bought an Epson WF-C5290 18 months ago, connected it up, installed
the Linux driver provided on the Epson site, and it has been as solid
as a rock.
Printing on Linux is poor. CUPS is poor. It doesn't work for some (a
lot?) of people.
I have a Brother HL-L2300D printer. It is connected to my (Debian
bullseye) workstation by USB. I have CUPS installed.
My printer prints sometime. Other times, it spins up (makes a noise
like it is
On 5/5/23 18:51, Brian wrote:
On Fri 05 May 2023 at 16:32:36 -0400, gene heskett wrote:
On 5/5/23 13:45, Brian wrote:
[...]
* An output from 'lpoptions -p HLL2320D_coyote -l' that indicates a broken
system.
this is bad?
gene@coyote:~$ lpoptions -p HLL2320D_coyote -l
On 5/5/23 13:45, Brian wrote:
On Fri 05 May 2023 at 11:40:21 -0400, gene heskett wrote:
On 5/5/23 10:08, Brian wrote:
On Thu 04 May 2023 at 15:57:49 -0400, gene heskett wrote:
On 5/4/23 15:43, zithro wrote:
On 01 May 2023 14:53, Brian wrote:
[...]
Second question: is that possible to
On Fri 05 May 2023 at 11:40:21 -0400, gene heskett wrote:
> On 5/5/23 10:08, Brian wrote:
> > On Thu 04 May 2023 at 15:57:49 -0400, gene heskett wrote:
> >
> > > On 5/4/23 15:43, zithro wrote:
> > > > On 01 May 2023 14:53, Brian wrote:
> >
> > [...]
> >
> > > > Second question: is that
On 5/5/23 10:08, Brian wrote:
On Thu 04 May 2023 at 15:57:49 -0400, gene heskett wrote:
On 5/4/23 15:43, zithro wrote:
On 01 May 2023 14:53, Brian wrote:
[...]
Second question: is that possible to use CUPS/printing without avahi ?
Absolutely, up to bullseye for both buster and bullseye,
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
On 5/1/23 17:22, Brian wrote:
On Mon 01 May 2023 at 20:59:50 +0100, debian-u...@howorth.org.uk wrote:
gene heskett wrote:
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...
On 5/1/23 14:31, Brian wrote:
On Mon 01 May 2023 at 13:22:47 -0400, gene heskett wrote:
On 5/1/23 12:30, Brian wrote:
[...]
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
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
gene heskett wrote:
> 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.
Your directory listings showed that both had a ppd
On Mon 01 May 2023 at 13:22:47 -0400, gene heskett wrote:
> On 5/1/23 12:30, Brian wrote:
[...]
> > 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
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
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
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
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
> >
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
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
>
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:
>
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
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
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
51 matches
Mail list logo
