Re: debian-to-windows message transfer

2024-11-15 Thread Timothy M Butterworth
On Fri, Nov 15, 2024 at 11:31 PM Russell L. Harris wrote: > Debian machines are on the 192.168.1.xxx network. I keep a W10 > machine on the 192.168.2.x network, primarily to access the chewy.com > web site which, since about June, serves my Debian machines a blank > white page. I get to the Ch

Re: Black screen.

2024-11-15 Thread Timothy M Butterworth
On Fri, Nov 15, 2024 at 9:49 PM milton César Disegna de Souza Leite < milton...@yahoo.com> wrote: > > On 15 Nov 2024, at 02:44, Timothy M Butterworth < > timothy.m.butterwo...@gmail.com> wrote: > > > > On Thu, Nov 14, 2024 at 11:52 PM milton César Disegna de Souza Leite < > milton...@yahoo.com> wr

Re: debian-to-windows message transfer

2024-11-15 Thread Russell L. Harris
On Fri, Nov 15, 2024 at 11:42:24PM -0500, Greg Wooledge wrote: Most importantly, though, I'd try to figure out why your browser on Debian is having problems. If you create a brand new user account, and run the browser with no add-ons, does it also have problems with this web site? Maybe it's so

debian-to-windows message transfer

2024-11-15 Thread Russell L. Harris
Debian machines are on the 192.168.1.xxx network. I keep a W10 machine on the 192.168.2.x network, primarily to access the chewy.com web site which, since about June, serves my Debian machines a blank white page. Only one of the Debian machines is set up for mail. Now and then a mail message co

Re: debian-to-windows message transfer

2024-11-15 Thread Greg Wooledge
On Sat, Nov 16, 2024 at 04:28:59 +, Russell L. Harris wrote: > Debian machines are on the 192.168.1.xxx network. I keep a W10 > machine on the 192.168.2.x network, primarily to access the chewy.com > web site which, since about June, serves my Debian machines a blank > white page. chewy.com l

Re: Black screen.

2024-11-15 Thread milton César Disegna de Souza Leite
> On 15 Nov 2024, at 02:44, Timothy M Butterworth > wrote: > > > > On Thu, Nov 14, 2024 at 11:52 PM milton César Disegna de Souza Leite > mailto:milton...@yahoo.com>> wrote: >> >> >> Hello, >> >> I recently installed Debian 12.8 on a laptop with an ONKYO motherboard with >> an i5 M450 pr

Re: utelnetd

2024-11-15 Thread Stefan Monnier
>> SSHD is packaged and available on Debian. > Timothy, for a console on localhost do you use ssh exclusively? Never > xterm or similar? You authenticate every connection to localhost? Hmm...`xterm` is unrelated: you'd run `telnet` or `ssh` *inside* `xterm`, no *instead of* `xterm`. > Naively,

Bump: systemd version 256.7-2 on Debian testing disabled UTMP support

2024-11-15 Thread Farblos
Hi Luca, everybody, any comment from your side on below mail or a general pointer on "the future of Debian and utmp"? Thanks Jens On 2024-11-06 21:18, Jens Schmidt wrote: > [I hope this is the right way to address this question - apologies > if not or if I have overlooked an existing discussio

Re: Modern HP MFD printers and Debian

2024-11-15 Thread gene heskett
On 11/15/24 10:50, Tom Browder wrote: On Fri, Nov 15, 2024 at 08:36 Tom Browder > wrote: … So far I cannot get scanning or copying to use the ADF in two-sided mode. Sorry, I lied about two-sided copying: I can do that, but menu is not easy to use. -Tom

Re: utelnetd

2024-11-15 Thread Andy Smith
Hi, On Fri, Nov 15, 2024 at 11:11:49AM -0700, pe...@easthope.ca wrote: > Exactly what I meant with "Naively, I wouldn't expect TLS to be > necessary for localhost. This utelnetd is also not necessary for localhost. And if telnet was actually a requirement, I'm fairly confident that the telnetd t

Re: utelnetd

2024-11-15 Thread Timothy M Butterworth
On Fri, Nov 15, 2024 at 2:27 PM wrote: > From: Stefan Monnier > Date: Fri, 15 Nov 2024 12:45:14 -0500 > > Hmm...`xterm` is unrelated: you'd run `telnet` or `ssh` *inside* > > `xterm`, no *instead of* `xterm`. > > OK, I understand that. If X11 is running you use xterm or similar. If > X1

Re: Modern HP MFD printers and Debian

2024-11-15 Thread Timothy M Butterworth
On Fri, Nov 15, 2024 at 1:02 PM Tom Browder wrote: > On Thu, Nov 14, 2024 at 7:46 AM Tom Browder wrote: > ... > > I wound up, after some fumbling, to set up everything using some basic > info from HP documentation that came with the printer. I used Firefox to go > to the network address of my pr

Re: utelnetd

2024-11-15 Thread peter
From: Stefan Monnier Date: Fri, 15 Nov 2024 12:45:14 -0500 > Hmm...`xterm` is unrelated: you'd run `telnet` or `ssh` *inside* > `xterm`, no *instead of* `xterm`. OK, I understand that. If X11 is running you use xterm or similar. If X11 is not running you can do "ssh localhost" on the c

Re: utelnetd

2024-11-15 Thread debian-user
pe...@easthope.ca wrote: > Extremely long References header shortened. =8~/ > > From: Timothy M Butterworth > Date: Thu, 14 Nov 2024 14:21:20 -0500 > > SSHD is packaged and available on Debian. > > Timothy, for a console on localhost do you use ssh exclusively? > Never xterm or simila

Re: utelnetd

2024-11-15 Thread peter
Extremely long References header shortened. =8~/ From: Timothy M Butterworth Date: Thu, 14 Nov 2024 14:21:20 -0500 > SSHD is packaged and available on Debian. Timothy, for a console on localhost do you use ssh exclusively? Never xterm or similar? You authenticate every connection to

Re: Modern HP MFD printers and Debian

2024-11-15 Thread Tom Browder
On Fri, Nov 15, 2024 at 08:36 Tom Browder wrote: … So far I cannot get scanning or copying to use the ADF in two-sided mode. > Sorry, I lied about two-sided copying: I can do that, but menu is not easy to use. -Tom

Re: Modern HP MFD printers and Debian

2024-11-15 Thread Tom Browder
On Thu, Nov 14, 2024 at 7:46 AM Tom Browder wrote: ... I wound up, after some fumbling, to set up everything using some basic info from HP documentation that came with the printer. I used Firefox to go to the network address of my printer and it magically showed me the proper setup screen where I

Re: No sound after migrate to Bookworm

2024-11-15 Thread Martin
Hi I have been able to solve my problem. I have a multiarch amd64 installation with some i386 packages. pipewire-bin package was only installed from i386, others pipewire related packages was installed from both amd64 and i386 arch. I reinstalled pipewire-bin from amd64 arch and removed i386