Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #258188
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: SOLVED:Re: repeat of previous question thathasgoneunansweredseveraltimes. |
| Date | 2023-05-12 21:30 +0200 |
| Message-ID | <GuGCJ-8qus-1@gated-at.bofh.it> (permalink) |
| References | (6 earlier) <GuocN-8ePR-1@gated-at.bofh.it> <GupVf-8fT9-1@gated-at.bofh.it> <Gux6p-8kH1-9@gated-at.bofh.it> <Guyca-8ljm-9@gated-at.bofh.it> <GuG01-8pVi-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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/>
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web