Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #257755 > unrolled thread
| Started by | gene heskett <gheskett@shentel.net> |
|---|---|
| First post | 2023-05-01 01:10 +0200 |
| Last post | 2023-05-08 07:10 +0200 |
| Articles | 9 on this page of 89 — 15 participants |
Back to article view | Back to linux.debian.user
repeat of previous question that has gone unanswered several times. gene heskett <gheskett@shentel.net> - 2023-05-01 01:10 +0200
Re: repeat of previous question that has gone unanswered several times. Lee <ler762@gmail.com> - 2023-05-01 02:20 +0200
Re: repeat of previous question that has gone unanswered several times. gene heskett <gheskett@shentel.net> - 2023-05-01 09:40 +0200
Re: repeat of previous question that has gone unanswered several times. Brian <ad44@cityscape.co.uk> - 2023-05-01 15:00 +0200
Re: repeat of previous question that has gone unanswered severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 15:50 +0200
Re: repeat of previous question that has gone unanswered severaltimes. David Wright <deblis@lionunicorn.co.uk> - 2023-05-01 16:10 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 16:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 17:40 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 16:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 17:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 18:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 19:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 19:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-02 01:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 19:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 20:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. debian-user@howorth.org.uk - 2023-05-01 22:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-01 23:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 01:00 +0200
Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 00:30 +0200
Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-02 01:00 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Jeffrey Walton <noloader@gmail.com> - 2023-05-01 16:20 +0200
Re: repeat of previous question that has gone unanswered severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-01 17:00 +0200
Re: repeat of previous question that has gone unanswered several times. David Wright <deblis@lionunicorn.co.uk> - 2023-05-01 06:30 +0200
Re: repeat of previous question that has gone unanswered several times. john doe <johndoe65534@mail.com> - 2023-05-01 09:40 +0200
Re: repeat of previous question that has gone unanswered several times. <tomas@tuxteam.de> - 2023-05-01 13:50 +0200
Re: repeat of previous question that has gone unanswered several times. Brian <ad44@cityscape.co.uk> - 2023-05-01 15:00 +0200
Re: repeat of previous question that has gone unanswered several times. zithro <slack@rabbit.lu> - 2023-05-04 21:50 +0200
Re: repeat of previous question that has gone unanswered severaltimes. gene heskett <gheskett@shentel.net> - 2023-05-04 22:00 +0200
Re: repeat of previous question that has gone unanswered severaltimes. Brian <ad44@cityscape.co.uk> - 2023-05-05 16:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-05 17:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-05 19:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-05 22:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-06 01:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-06 03:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Alex King <alex@king.net.nz> - 2023-05-07 01:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. David <curmudgeon@telaman.net.au> - 2023-05-07 02:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Byung-Hee HWANG <soyeomul@doraji.xyz> - 2023-05-07 03:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2023-05-07 13:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-07 17:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-07 18:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 06:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-08 13:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 19:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 00:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 10:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-09 13:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-09 22:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 14:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 16:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. <tomas@tuxteam.de> - 2023-05-10 16:50 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 17:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 19:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-10 20:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 22:00 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 13:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-11 18:30 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-10 22:10 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. debian-user@howorth.org.uk - 2023-05-10 22:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 13:10 +0200
SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-11 18:10 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-11 21:20 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 00:00 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-12 00:30 +0200
Re: SOLVED:Re: repeat of previous question that has gone unansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 01:50 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:40 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 11:20 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 12:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Greg Wooledge <greg@wooledge.org> - 2023-05-12 13:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 13:50 +0200
Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 18:20 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 12:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 13:50 +0200
:Re: repeat of previous question thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 18:10 +0200
Re: :Re: repeat of previous question thathasgoneunansweredseveraltimes. Vincent Lefevre <vincent@vinc17.net> - 2023-05-12 23:30 +0200
Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-12 20:50 +0200
Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 21:30 +0200
Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. Brian <ad44@cityscape.co.uk> - 2023-05-13 13:20 +0200
Re: SOLVED:Re: repeat of previous questionthathasgoneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-13 17:10 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:30 +0200
Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-12 03:20 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> - 2023-05-07 19:40 +0200
Re: repeat of previous question that has gone unansweredseveraltimes. gene heskett <gheskett@shentel.net> - 2023-05-08 07:10 +0200
Page 5 of 5 — ← Prev page 1 2 3 4 [5]
| From | Vincent Lefevre <vincent@vinc17.net> |
|---|---|
| Date | 2023-05-12 23:30 +0200 |
| Subject | Re: :Re: repeat of previous question thathasgoneunansweredseveraltimes. |
| Message-ID | <GuIuR-8rO4-5@gated-at.bofh.it> |
| In reply to | #258183 |
On 2023-05-12 12:08:33 -0400, gene heskett wrote: > On 5/12/23 07:41, Vincent Lefevre wrote: > > On 2023-05-12 06:23:56 -0400, gene heskett wrote: > > > I'm confused. There is not anything wrong with this machine as a Server. > > > ALL of this muttering and bitching has been because bookworm clients did NOT > > > work. buster clients work great. > > > > > > How many times do I have to say it is/was a CLIENT problem that only exists > > > for BOOKWORM clients. The elephant in the room that most have ignored. > > > > But you said that the problem was "solved" by modifying a setting > > corresponding to the Listen directives (in /etc/cups/cupsd.conf). > > These directives concern the *server* only. > > > Oh, then how does one tell the CLIENT to even use the SERVER? I'm not sure what you mean by "use". In the past, I had the following lines in the /etc/cups/client.conf file of the machine at my lab: ServerName liqqs.lip.ens-lyon.fr:443 Encryption Required ValidateCerts Yes The first line is to tell which server to use, and the other lines for security. This way of doing means that everything is configured on the server. This has been deprecated at my lab, and now, the printers need to be configured directly on the client side. In case you want something like that, AFAIK, there are 2 solutions: Manual: something like lpadmin -p <name> -v <URI> [ -E ] -m everywhere -L <location> Automatic with the cups-browsed package: Description: OpenPrinting CUPS Filters - cups-browsed This package provides cups-browsed, a daemon which browses the Bonjour broadcasts of shared remote CUPS printers and makes the printers available locally, replacing the CUPS broadcasting/browsing which was dropped in CUPS 1.6.x. This way the old behavior of having the remote printers available automatically is now re-implemented with Bonjour. (However, it appears that because of that, on my laptop, I now have dozens of ghost printers, and this is annoying.) > It is 100% a "cannot assign requested address error" on the bpi51 as logged > in/var/log/cups/error_log: > > E [12/May/2023:10:32:20 -0500] Unable to open listen socket for address > 192.168.71.3:631 - Cannot assign requested address. > E [12/May/2023:10:34:45 -0500] Unable to open listen socket for address > [v1.::1]:631 - Cannot assign requested address. I suppose that this is because you already have a server that is already running and listening on these ports. Or you started the server too soon after the old one terminated. > Where its getting the ipv6 addy is a mystery ::1 is the IPv6 loopback. Perhaps listening on it is the default (this makes sense), and perhaps even if it isn't setup (as this is unusual). -- Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-12 20:50 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question that hasgoneunansweredseveraltimes. |
| Message-ID | <GuG01-8pVi-3@gated-at.bofh.it> |
| In reply to | #258159 |
On Fri 12 May 2023 at 06:23:56 -0400, gene heskett wrote: [...] > I'm confused. There is not anything wrong with this machine as a Server. > ALL of this muttering and bitching has been because bookworm clients did NOT > work. buster clients work great. "work(s)" is such vague term. I guess working and non-working are references to > All of my bullseye machines are locked out, printer screen at > localhost:631 is empty, and no printers can be found and added > How many times do I have to say it is/was a CLIENT problem that only exists > for BOOKWORM clients. The elephant in the room that most have ignored. THe issue has been fully dealt with. In short: No local printers leads to an empty localhost:631 and 'lpstat -t'. THere isn't any issue whatsoever. You seem very reluctant to incorporate this basic fact into your thinking. THe room is empty. May we have 'lpstat -t' from a buster machine that is not bpi54? -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-12 21:30 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. |
| Message-ID | <GuGCJ-8qus-1@gated-at.bofh.it> |
| In reply to | #258187 |
On 5/12/23 14:45, Brian wrote: > On Fri 12 May 2023 at 06:23:56 -0400, gene heskett wrote: > > [...] > >> I'm confused. There is not anything wrong with this machine as a Server. >> ALL of this muttering and bitching has been because bookworm clients did NOT >> work. buster clients work great. > > "work(s)" is such vague term. I guess working and non-working are references > to > > > All of my bullseye machines are locked out, printer screen at > > localhost:631 is empty, and no printers can be found and added > >> How many times do I have to say it is/was a CLIENT problem that only exists >> for BOOKWORM clients. The elephant in the room that most have ignored. > > THe issue has been fully dealt with. In short: > > No local printers leads to an empty localhost:631 and 'lpstat -t'. > > THere isn't any issue whatsoever. You seem very reluctant to incorporate this > basic fact into your thinking. THe room is empty. > > May we have 'lpstat -t' from a buster machine that is not bpi54? This is buster, running a milling machine in the garage gene@GO704:~$ lpstat -t scheduler is running no system default destination device for Brother_HL_L2320D_series_coyote: implicitclass://Brother_HL_L2320D_series_coyote/ device for Brother_MFC_J6920DW: ipp://BRN30055C8A2DC8.local:631/ipp/print device for Brother_MFC_J6920DW_coyote: implicitclass://Brother_MFC_J6920DW_coyote/ device for HLL2320D_coyote: implicitclass://HLL2320D_coyote/ device for MFCJ6920DW_tray_2_coyote: ///dev/null Brother_HL_L2320D_series_coyote accepting requests since Fri 12 May 2023 12:00:02 AM EDT Brother_MFC_J6920DW accepting requests since Fri 12 May 2023 12:00:02 AM EDT Brother_MFC_J6920DW_coyote accepting requests since Fri 12 May 2023 12:00:02 AM EDT HLL2320D_coyote accepting requests since Fri 12 May 2023 12:00:02 AM EDT MFCJ6920DW_tray_2_coyote not accepting requests since Wed 03 May 2023 12:00:02 AM EDT - reason unknown printer Brother_HL_L2320D_series_coyote is idle. enabled since Fri 12 May 2023 12:00:02 AM EDT printer Brother_MFC_J6920DW is idle. enabled since Fri 12 May 2023 12:00:02 AM EDT printer Brother_MFC_J6920DW_coyote is idle. enabled since Fri 12 May 2023 12:00:02 AM EDT printer HLL2320D_coyote is idle. enabled since Fri 12 May 2023 12:00:02 AM EDT printer MFCJ6920DW_tray_2_coyote disabled since Wed 03 May 2023 12:00:02 AM EDT - reason unknown this is another gantry style machine: gene@sixty40:~$ lpstat -t scheduler is running no system default destination device for Brother_HL_L2320D_series_coyote: ///dev/null device for Brother_MFC_J6920DW: ipp://BRN30055C8A2DC8.local:631/ipp/print device for Brother_MFC_J6920DW_coyote: ///dev/null Brother_HL_L2320D_series_coyote not accepting requests since Sun 23 Apr 2023 12:00:03 AM EDT - reason unknown Brother_MFC_J6920DW accepting requests since Fri 12 May 2023 12:00:14 AM EDT Brother_MFC_J6920DW_coyote not accepting requests since Thu 20 Apr 2023 12:00:03 AM EDT - reason unknown printer Brother_HL_L2320D_series_coyote disabled since Sun 23 Apr 2023 12:00:03 AM EDT - reason unknown printer Brother_MFC_J6920DW is idle. enabled since Fri 12 May 2023 12:00:14 AM EDT printer Brother_MFC_J6920DW_coyote disabled since Thu 20 Apr 2023 12:00:03 AM EDT - reason unknown and this is an rpi4b running a 1500 lb lathe: pi@rpi4:~ $ lpstat -t scheduler is running no system default destination device for Brother_HL-L2320D_series: usb://Brother/HL-L2320D%20series?serial=U63877H0N346913 device for Brother_MFC-J6920DW_photo: usb://Brother/MFC-J6920DW?serial=BROG5F229909 device for MFCJ6920DW: usb://Brother/MFC-J6920DW?serial=BROG5F229909 Brother_HL-L2320D_series accepting requests since Tue 09 May 2023 05:23:01 PM EDT Brother_MFC-J6920DW_photo accepting requests since Thu 30 Mar 2023 09:16:43 AM EDT MFCJ6920DW accepting requests since Sun 26 Mar 2023 03:30:13 PM EDT printer Brother_HL-L2320D_series is idle. enabled since Tue 09 May 2023 05:23:01 PM EDT printer Brother_MFC-J6920DW_photo is idle. enabled since Thu 30 Mar 2023 09:16:43 AM EDT printer MFCJ6920DW is idle. enabled since Sun 26 Mar 2023 03:30:13 PM EDT there is a 2nd smaller lathe in a shed in the upper rear corner of the place that has been kept uptodate but is in the middle of a hardware update for linuxcnc, and its a suprise: gene@TLM:~$ lpstat -t scheduler is not running no system default destination lpstat: Bad file descriptor lpstat: Bad file descriptor lpstat: Bad file descriptor lpstat: Bad file descriptor lpstat: Bad file descriptor but cups is not installed, its missing from .etc/init.d, rebooting didn't change. machine updates and cups and friends installed: gene@TLM:~$ lpstat -t scheduler is running no system default destination device for Brother_HL_L2320D_series_coyote: implicitclass://Brother_HL_L2320D_series_coyote/ device for Brother_MFC_J6920DW: ipp://BRN30055C8A2DC8.local:631/ipp/print device for Brother_MFC_J6920DW_coyote: implicitclass://Brother_MFC_J6920DW_coyote/ device for HLL2320D_coyote: implicitclass://HLL2320D_coyote/ device for MFCJ6920DW_tray_2_coyote: implicitclass://MFCJ6920DW_tray_2_coyote/ Brother_HL_L2320D_series_coyote accepting requests since Fri 12 May 2023 03:21:26 PM EDT Brother_MFC_J6920DW accepting requests since Fri 12 May 2023 03:20:24 PM EDT Brother_MFC_J6920DW_coyote accepting requests since Fri 12 May 2023 03:21:26 PM EDT HLL2320D_coyote accepting requests since Fri 12 May 2023 03:21:26 PM EDT MFCJ6920DW_tray_2_coyote accepting requests since Fri 12 May 2023 03:21:26 PM EDT printer Brother_HL_L2320D_series_coyote is idle. enabled since Fri 12 May 2023 03:21:26 PM EDT printer Brother_MFC_J6920DW is idle. enabled since Fri 12 May 2023 03:20:24 PM EDT printer Brother_MFC_J6920DW_coyote is idle. enabled since Fri 12 May 2023 03:21:26 PM EDT printer HLL2320D_coyote is idle. enabled since Fri 12 May 2023 03:21:26 PM EDT printer MFCJ6920DW_tray_2_coyote is idle. enabled since Fri 12 May 2023 03:21:26 PM EDT all those running uptodate buster. opening and re-closing both paper trays on the 6920 fixed that error Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2023-05-13 13:20 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. |
| Message-ID | <GuVs5-8BBJ-3@gated-at.bofh.it> |
| In reply to | #258188 |
On Fri 12 May 2023 at 15:27:21 -0400, gene heskett wrote: > On 5/12/23 14:45, Brian wrote: > > On Fri 12 May 2023 at 06:23:56 -0400, gene heskett wrote: > > > > [...] > > > > > I'm confused. There is not anything wrong with this machine as a Server. > > > ALL of this muttering and bitching has been because bookworm clients did NOT > > > work. buster clients work great. > > > > "work(s)" is such vague term. I guess working and non-working are references > > to > > > > > All of my bullseye machines are locked out, printer screen at > > > localhost:631 is empty, and no printers can be found and added > > > > > How many times do I have to say it is/was a CLIENT problem that only exists > > > for BOOKWORM clients. The elephant in the room that most have ignored. > > > > THe issue has been fully dealt with. In short: > > > > No local printers leads to an empty localhost:631 and 'lpstat -t'. > > > > THere isn't any issue whatsoever. You seem very reluctant to incorporate this > > basic fact into your thinking. THe room is empty. > > > > May we have 'lpstat -t' from a buster machine that is not bpi54? > > This is buster, running a milling machine in the garage [Informative info from a number of machines snupped.] All the displayed queues are local and have either been set up manually (ipp://...) or autmatically by cups-browsed (implicitclass://...). A manual setup on a bullseye machine would involve the raw or everywhere model. A client.conf is an is an alternative. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-13 17:10 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous questionthathasgoneunansweredseveraltimes. |
| Message-ID | <GuZ2F-8DN3-5@gated-at.bofh.it> |
| In reply to | #258221 |
On 5/13/23 07:18, Brian wrote: > On Fri 12 May 2023 at 15:27:21 -0400, gene heskett wrote: > >> On 5/12/23 14:45, Brian wrote: >>> On Fri 12 May 2023 at 06:23:56 -0400, gene heskett wrote: >>> >>> [...] >>> >>>> I'm confused. There is not anything wrong with this machine as a Server. >>>> ALL of this muttering and bitching has been because bookworm clients did NOT >>>> work. buster clients work great. >>> >>> "work(s)" is such vague term. I guess working and non-working are references >>> to >>> >>> > All of my bullseye machines are locked out, printer screen at >>> > localhost:631 is empty, and no printers can be found and added >>> >>>> How many times do I have to say it is/was a CLIENT problem that only exists >>>> for BOOKWORM clients. The elephant in the room that most have ignored. >>> >>> THe issue has been fully dealt with. In short: >>> >>> No local printers leads to an empty localhost:631 and 'lpstat -t'. >>> >>> THere isn't any issue whatsoever. You seem very reluctant to incorporate this >>> basic fact into your thinking. THe room is empty. >>> >>> May we have 'lpstat -t' from a buster machine that is not bpi54? >> >> This is buster, running a milling machine in the garage > > [Informative info from a number of machines snupped.] > > All the displayed queues are local and have either been set up manually (ipp://...) > or autmatically by cups-browsed (implicitclass://...). A manual setup on a > bullseye machine would involve the raw or everywhere model. A client.conf is an > is an alternative. > But it doesn't seem to work in armbian bullseye, who uses debian repo's for everything not involved with booting. Most armbian stuff is u-boot. I now have different results between bpi54, which works, and bpi51, which does not. The two are I believe configured identically in /etc/cups. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-12 03:30 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. |
| Message-ID | <GupLz-8fQ2-1@gated-at.bofh.it> |
| In reply to | #258142 |
On 5/11/23 18:25, 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 /etc/cups/cupsd.conf and inserting a >>> >>> Listen 192.168.xx.yy:631 >>> >>> made the localhost:631/printers on this machine show up in FF on bpi54, all >>> 5 choices from this machine. >> >> Any explanation? > > Seems obvious enough to me. CUPS on bpi54 was only listening to > loopback (localhost), but Gene wanted to print through it remotely. > So he had to make it listen to the network instead. Close, I wanted to be able to print from the bpi from any app on the bpi that had a print this option. Now I can. > > My questions would be: > > 1) Can you put *both* Listen lines in, to keep loopback working? No, that kills the cups ability to query the network even with the Server named in client.conf. It even logs it as a failure, on the bpi5 but doesn't say why. > 2) Failing that, can you use 0.0.0.0 as the Listen address, to listen on > all interfaces? That's the normal convention. Untried, so can't say. And I've not read far enough to see that as an example. Thanks Greg. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-12 03:20 +0200 |
| Subject | Re: SOLVED:Re: repeat of previous question that has goneunansweredseveraltimes. |
| Message-ID | <GupBT-8fN8-1@gated-at.bofh.it> |
| In reply to | #258141 |
On 5/11/23 17:59, 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 192.168.xx.yy:631 >> >> made the localhost:631/printers on this machine show up in FF on bpi54, all >> 5 choices from this machine. > > Any explanation? > My best guess is the Server directive in client.conf was rejected because there was already a couple "Listen" directives pointing at itself. Remove the main one and the client.conf was able to take over. Or the substition of a "Listen ipv4-address-of-server:631" is also a possibility. Whatever, the point now is that it Just Works. A lot of hacking on C-89 has taken place since the last C book was published by K&R, so I am not the C guru I was in the 1990's. I'm now 88 yo and some of me has gone to the dogs too. Take that as an admission that my diagnosis might be wrong, but I've been chasing electrons to make then do useful work since about 1948 when I quit school and went to work fixing them new fangled things called tv's. Take care & stay well, Vincent. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [next] | [standalone]
| From | Eduardo M KALINOWSKI <eduardo@kalinowski.com.br> |
|---|---|
| Date | 2023-05-07 19:40 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <GsQwx-7hvz-15@gated-at.bofh.it> |
| In reply to | #258032 |
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 sudo if needed. It will ask > you for the model # of your printer, enter it EXACTLY, the script will, > if you've net access, goto brothers site, download the exact driver your > printer needs, install it, integrating with cups perfectly but you will > probably need to disable cups-browsed as it will make the default driver > the everywhere driver, crippling 95% of the printers abilities. And > from the machine the printer is plugged into, and assuming browsed is > stopped so you can use the brother driver, it Just Works. Please stop spreading misinformation. I have a Brother MFC-L2740DW (which I believe is the exact model you have, or if not very similar) and it works perfectly with the "driverless" approach, both with the cups ppd generator (everywhere) and the cups-filters pps generator (driverless). The first one leads to slow printing for some reason, and I had to select "high" quality to get standard quality; the second one is as fast as the proprietary driver. Auto discovery with cups-browsed also works. There might be some specialized options only available in the proprietary driver, but everything needed for general use (tray selection, duplex, etc) is available in the driverless driver. The proprietary driver is fine and works well, if it suits you, feel free to use it. Just be aware that it's only available for i386, not amd64, so in a desktop pc you'll need to add the i386 architecture. On a Raspberry Pi or other arm computer you won't be able to run the proprietary driver. But please don't say it's the only option because you've been unable to use the other ones. -- Ban the bomb. Save the world for conventional warfare. Eduardo M KALINOWSKI eduardo@kalinowski.com.br
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2023-05-08 07:10 +0200 |
| Subject | Re: repeat of previous question that has gone unansweredseveraltimes. |
| Message-ID | <Gt1ih-7ozo-1@gated-at.bofh.it> |
| In reply to | #258036 |
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 download >> their driver installer, unpack it, run it sudo if needed. It will ask >> you for the model # of your printer, enter it EXACTLY, the script >> will, if you've net access, goto brothers site, download the exact >> driver your printer needs, install it, integrating with cups perfectly >> but you will probably need to disable cups-browsed as it will make the >> default driver the everywhere driver, crippling 95% of the printers >> abilities. And from the machine the printer is plugged into, and >> assuming browsed is stopped so you can use the brother driver, it Just >> Works. > > Please stop spreading misinformation. I have a Brother MFC-L2740DW > (which I believe is the exact model you have, or if not very similar) I doubt it, does your handle tabloid sized paper (11x17"), including the scanner in its lid with an adf? Does it have 2 paper drawers? > and it works perfectly with the "driverless" approach, both with the > cups ppd generator (everywhere) and the cups-filters pps generator > (driverless). The first one leads to slow printing for some reason, and > I had to select "high" quality to get standard quality; the second one > is as fast as the proprietary driver. Auto discovery with cups-browsed > also works. There might be some specialized options only available in > the proprietary driver, but everything needed for general use (tray > selection, duplex, etc) is available in the driverless driver. You just showed that it doesn't Just Work, which is exactly why I run the brother drivers, which run just fine on a 6 core i5. Every feature this printer has, I can adjust from the cups menu's. The driverless setup can run this inkjet, w/o duplex because its w/o tray selection, printing everything on paper from the top smaller tray normally loaded with 50 cents a sheet glossy photo paper. > The proprietary driver is fine and works well, if it suits you, feel > free to use it. Just be aware that it's only available for i386, not > amd64, so in a desktop pc you'll need to add the i386 architecture. On a > Raspberry Pi or other arm computer you won't be able to run the > proprietary driver. An arm computer has no need to run their driver, and yes, the rpi4b running 1500 lbs worth of 80 yo Sheldon lathe, but running buster sees 7 shared printers from this machine right now. And they are all usable from that keyboard. If their driver ever had an i386 limitation its news to me. > But please don't say it's the only option because you've been unable to > use the other ones. This printer also has a cat5 feed, with an address in my local 192,168,xx, block, so even if its not plugged into a given machine, but the printer and the scanner should still be available at it ipv4 address. That should be found by cups running anywhere on the property, it is not discovered. But I'm mistaken, I now recall unplugging the cat 5 cable about 2 years ago. USB is faster at data transfer. By about 5x. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/>
[toc] | [prev] | [standalone]
Page 5 of 5 — ← Prev page 1 2 3 4 [5]
Back to top | Article view | linux.debian.user
csiph-web