Re: [FIXED] Re: brltty=huge distraction for folks that don't need it.

On 1/3/22 02:46, gene heskett wrote: > On Monday, January 3, 2022 1:59:56 AM EST john doe wrote: ... >> >> It would be nice if you could replicate the issue and file a bug report >> against the Debian Installer with the D-I logs. > > I appreciate that, but that means I'd have to do a complete

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

On Mon, Jan 03, 2022 at 11:01:34PM +0100, local10 wrote: > Hi, > > Am I the only one who's getting this error? When I go to the USPS.com[1] to > track a package I get this "Warning: Potential Security Risk Ahead" error ( > Error code: SSL_ERROR_BAD_CERT_DOMAIN ). It's been like this for a couple

Re: Hyper-typematic and Firefox responsiveness in Weston.

On Tue, 4 Jan 2022 at 14:40, David wrote: > There are a couple of unexpected aspects to script #2, which I will > explain ... > > a) Script sequencing > > or "Why has he put it under /usr ?" > > All the PREREQ= and prereqs stuff is a mechanism to control the > sequencing of scripts in each subdir

Re: Hyper-typematic and Firefox responsiveness in Weston.

On Tue, 4 Jan 2022 at 08:42, David Wright wrote: > On Mon 03 Jan 2022 at 16:25:47 (+1100), David wrote: > > So I now run 'kbdrate' inside the initrd. This seems to have > > solved the problem there and in all subsequent layers. > I presume you do this by placing something like > /sbin/kbdrate

Re: couldn't build pipe-viewer with debian

I put libreadline-dev on the machine since that wasn't installed and ran the instructions in the README.md file in pipe-viewer directory and the whole package built and installed. Thanks for the pointer on that -dev file. I'll have to check for those in the future. On Mon, 3 Jan 2022, Jude DaShi

Re: couldn't build pipe-viewer with debian

I forgot to install the -dev package. I'll try this again and see if it goes through. On Mon, 3 Jan 2022, Greg Wooledge wrote: > On Mon, Jan 03, 2022 at 07:38:25PM -0500, Jude DaShiell wrote: > > pipe-viewer youtube-viewer and straw-viewer cannot be built with debian. > > The reasons for that a

Re: why bash completion sometimes doesn't work?

On Tue, Jan 04, 2022 at 02:39:24AM +, Long Wind wrote: > > Thank Greg Wooledge! > > it seems solved, > there's more whitespace between iface and device name, > i correct it to just one space, and bash completion works for ifup/ifdown Might be worth a bug report.

Re: why bash completion sometimes doesn't work?

Thank Greg Wooledge! it seems solved, there's more whitespace between iface and device name, i correct it to just one space, and bash completion works for ifup/ifdown

Re: couldn't build pipe-viewer with debian

On Mon, Jan 03, 2022 at 07:38:25PM -0500, Jude DaShiell wrote: > pipe-viewer youtube-viewer and straw-viewer cannot be built with debian. > The reasons for that are each of those packages require > Term::ReadLine::Gnu and Term::ReadLine::Gnu cannot be built withreadline > 2.0. That's an ancient ve

Re: why bash completion sometimes doesn't work?

On Mon, Jan 03, 2022 at 11:56:57PM +, Long Wind wrote: > Thank Greg and David! > > i type "ifdown ", it add lo automatically, > wireless device isn't shown, though wireless connection works well > > i think "ip a" can list wireless device Well, it sounds like _configured_interfaces on your s

couldn't build pipe-viewer with debian

pipe-viewer youtube-viewer and straw-viewer cannot be built with debian. The reasons for that are each of those packages require Term::ReadLine::Gnu and Term::ReadLine::Gnu cannot be built withreadline 2.0. That's an ancient version of readline. I tried with readline 2.01 and my x86_64 equipment

Re: brltty=huge distraction for folks that don't need it.

On Monday, January 3, 2022 4:42:56 PM EST David Wright wrote: > On Mon 03 Jan 2022 at 04:33:53 (-0500), gene heskett wrote: > > On Sunday, January 2, 2022 10:47:08 PM EST David Wright wrote: > > > On Sun 02 Jan 2022 at 22:31:27 (-0500), gene heskett wrote: > > > > On Sunday, January 2, 2022 9:54:29

[SOLVED] Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

Jan 3, 2022, 23:53 by loca...@tutanota.com: > Jan 3, 2022, 23:08 by d...@randomstring.org: > >> Alright. Put this into your /etc/hosts temporarily: >> >> 152.195.33.23 www.usps.com tools.usps.com www.usps.gov >> >> That's unlikely to be an optimal IP from their CDN, but it is >> currently working

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

Jan 3, 2022, 23:08 by d...@randomstring.org: > Alright. Put this into your /etc/hosts temporarily: > > 152.195.33.23 www.usps.com tools.usps.com www.usps.gov > > That's unlikely to be an optimal IP from their CDN, but it is > currently working. > That fixed it, I got the USPS tracking page to lo

Re: Reasonably simple setup for 1TB HDD and 250GB M.2 NVMe SSD

Hi! Em [2022-01-03 seg 10:03:08-0500], Michael Stone escreveu: > On Mon, Jan 03, 2022 at 08:42:29AM -0300, Jorge P. de Morais Neto wrote: >>Indeed I use such high compression to prolong SSD lifetime. > > This is probably misguided and useless at best, at worst you're causing > additional writes

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

# host usps.com usps.com has address 56.0.134.100 usps.com mail is handled by 10 usps-com.mail.protection.outlook.com. # host tools.usps.com tools.usps.com is an alias for cs1799.wpc.upsiloncdn.net. cs1799.wpc.upsiloncdn.net has address 152.195.33.23 cs1799.wpc.upsiloncdn.net has IPv6 address 2

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

On 4/1/22 7:37 am, Jeremy Ardley wrote: On 4/1/22 7:27 am, local10 wrote: I have no problems accessing the www.usps.com , it's when I go to tools.usps.com that's when I have the issue: # host usps.com usps.com has address 56.0.134.100 usps.com mail is handled by 10 us

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

Jan 3, 2022, 23:37 by jer...@ardley.org: > If you are running IPV6 > Not running IPV6. Regards,

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

On 4/1/22 7:27 am, local10 wrote: I have no problems accessing the www.usps.com , it's when I go to tools.usps.com that's when I have the issue: # host usps.com usps.com has address 56.0.134.100 usps.com mail is handled by 10 usps-com.mail.protection.outlook.com. # host

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

Jan 3, 2022, 22:42 by jer...@ardley.org: > I too have no problems. > > My best guess is the OP DNS has been compromised. A simple check such as > using the host command should produce > > host usps.com > usps.com has address 56.0.134.100 > usps.com mail is handled by 10 usps-com.mail.protection.o

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

local10 wrote: > Jan 3, 2022, 22:29 by d...@randomstring.org: > > > Costco is definitely not the US Postal Service. > > > > No argument here. > > > > flush caches. Restart Firefox. Check your net connection. > > > > I've done this a number of times. The connection is direct, no proxy. Alrigh

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

Jan 3, 2022, 22:29 by d...@randomstring.org: > Costco is definitely not the US Postal Service. > No argument here. > flush caches. Restart Firefox. Check your net connection. > I've done this a number of times. The connection is direct, no proxy. Regards,

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

Jan 3, 2022, 22:30 by m...@allums.com: > Did you click on a phishing link? > > Mark Allums > No, I have some USPS.com tracking links bookmarked and they were working fine until about two weeks ago. Could it be perhaps related to the Firefox upgrade from 78esr to 91esr? Regards,

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

local10 wrote: > Jan 3, 2022, 22:11 by robe...@debian.org: > > > The site works fine for me. > > > > In FF, click on 'SSL_ERROR_BAD_CERT_DOMAIN', which should take you to > > the full error output. Then click 'Copy text to clipboard' and paste > > the full text into an email. Someone on the lis

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

On 4/1/22 6:36 am, Charles Curley wrote: On Mon, 3 Jan 2022 23:01:34 +0100 (CET) local10 wrote: Am I the only one who's getting this error? I am not. Vivaldi (vivaldi-stable, 5.0.2497.32-1, amd64) on bullseye. The cert looks like: Common Name (CN)*.usps.com Organization (O)U

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

Jan 3, 2022, 22:16 by loca...@tutanota.com: > Jan 3, 2022, 22:11 by robe...@debian.org: > >> The site works fine for me. >> >> In FF, click on 'SSL_ERROR_BAD_CERT_DOMAIN', which should take you to >> the full error output. Then click 'Copy text to clipboard' and paste >> the full text into an ema

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

On Mon, 3 Jan 2022 23:01:34 +0100 (CET) local10 wrote: > Am I the only one who's getting this error? I am not. Vivaldi (vivaldi-stable, 5.0.2497.32-1, amd64) on bullseye. The cert looks like: Common Name (CN)*.usps.com Organization (O)United States Postal Service Organizational

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

Did you click on a phishing link? Mark Allums On 1/3/22 16:16, local10 wrote: Jan 3, 2022, 22:11 by robe...@debian.org: The site works fine for me. In FF, click on 'SSL_ERROR_BAD_CERT_DOMAIN', which should take you to the full error output. Then click 'Copy text to clipboard' and paste th

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

Jan 3, 2022, 22:11 by robe...@debian.org: > The site works fine for me. > > In FF, click on 'SSL_ERROR_BAD_CERT_DOMAIN', which should take you to > the full error output. Then click 'Copy text to clipboard' and paste > the full text into an email. Someone on the list ought to be able to > help d

Re: Firefox: Warning: Potential Security Risk Ahead for the USPS.com

On Mon, Jan 03, 2022 at 11:01:34PM +0100, local10 wrote: > Hi, > > Am I the only one who's getting this error? When I go to the USPS.com[1] to > track a package I get this "Warning: Potential Security Risk Ahead" error ( > Error code: SSL_ERROR_BAD_CERT_DOMAIN ). It's been like this for a couple

Firefox: Warning: Potential Security Risk Ahead for the USPS.com

Hi, Am I the only one who's getting this error? When I go to the USPS.com[1] to track a package I get this "Warning: Potential Security Risk Ahead" error ( Error code: SSL_ERROR_BAD_CERT_DOMAIN ). It's been like this for a couple of weeks for me so it looks really strange that the USPS has fixe

Re: brltty=huge distraction for folks that don't need it.

On Mon 03 Jan 2022 at 04:33:53 (-0500), gene heskett wrote: > On Sunday, January 2, 2022 10:47:08 PM EST David Wright wrote: > > On Sun 02 Jan 2022 at 22:31:27 (-0500), gene heskett wrote: > > > On Sunday, January 2, 2022 9:54:29 PM EST David Wright wrote: > > > > On Sun 02 Jan 2022 at 17:53:19 (-0

Re: Hyper-typematic and Firefox responsiveness in Weston.

On Mon 03 Jan 2022 at 16:25:47 (+1100), David wrote: > On Mon, 3 Jan 2022 at 14:05, David Wright wrote: > > On Thu 30 Dec 2021 at 19:48:05 (-0800), pe...@easthope.ca wrote: > > > > In weston, keyboard response can be hyper-typematic. > > > The kbdrate can be set at @reboot in root's > > crontab

Re: why bash completion sometimes doesn't work?

On Mon 03 Jan 2022 at 20:12:50 (+), Long Wind wrote: > Thank Greg!  i use bash 5.0-4 and bash-completion 1:2.8-6 > all bash setting for root is default except 3 alias > >  alias rm='rm -i' >  alias cp='cp -i' >  alias mv='mv -i' > > i type "ifdown wl" and press Tab, nothing happens > there's

Re: why bash completion sometimes doesn't work?

On Mon, Jan 03, 2022 at 08:12:50PM +, Long Wind wrote: > Thank Greg!  i use bash 5.0-4 and bash-completion 1:2.8-6 > i type "ifdown wl" and press Tab, nothing happens > there's only one wireless device in /etc/network/interfaces > it shall complete command to "ifdown wlx12345" > > i've read

Re: How i can resolve the problem of packages?

On Sun, Oct 10, 2021 at 5:43 PM Cindy Sue Causey wrote: > On 10/10/21, Dan Ritter wrote: > > William Torrez Corea wrote: > >> I try execute the followings tasks but i get the same error: > >> > >> ldconfig: Can't create temporary cache file /etc/ld.so.cache~: Read-only > >> > file system > > > >

Re: having high cpu problem related to kernel version

I found that this is a bug of kernel module "rtl8723ae" and it also happens on kernel 5.10 i wasn't able to pin it out because i updated packages right after i installed it i was able to find related thread on askubuntu https://askubuntu.com/questions/846830/irq-from-realtek-wifi-are-loading-cpu ty

Re: 8 -> 9 update changing things

On Sunday 02 January 2022 09:56:14 pm David Wright wrote: > On Sat 18 Dec 2021 at 11:24:34 (-0500), Roy J. Tellason, Sr. wrote: > > On Friday 17 December 2021 11:53:20 am David Wright wrote: > > Yeah, except that I don't run KDE. I do have it installed, to be able to > > access certain programs

Re: Reasonably simple setup for 1TB HDD and 250GB M.2 NVMe SSD

On Mon, Jan 03, 2022 at 10:33:59AM -0500, Dan Ritter wrote: Michael Stone wrote: On Mon, Jan 03, 2022 at 08:42:29AM -0300, Jorge P. de Morais Neto wrote: > Indeed I use such high compression to prolong SSD lifetime. This is probably misguided and useless at best, at worst you're causing additio

Re: brltty=huge distraction for folks that don't need it.

On Mon, 03 Jan 2022 04:33:53 -0500 gene heskett wrote: > Do we still have a working usbtree like utility that might discover > this? Such useful stuff seems to be falling off the edge in later > versions of linux. Do you mean something like 'lsusb -t'? -- Does anybody read signatures any more?

Re: Reasonably simple setup for 1TB HDD and 250GB M.2 NVMe SSD

Michael Stone wrote: > On Mon, Jan 03, 2022 at 08:42:29AM -0300, Jorge P. de Morais Neto wrote: > > Indeed I use such high compression to prolong SSD lifetime. > > This is probably misguided and useless at best, at worst you're causing > additional writes because compressed data is generally hard

Re: Reasonably simple setup for 1TB HDD and 250GB M.2 NVMe SSD

On Mon, Jan 03, 2022 at 08:42:29AM -0300, Jorge P. de Morais Neto wrote: Indeed I use such high compression to prolong SSD lifetime. This is probably misguided and useless at best, at worst you're causing additional writes because compressed data is generally hard to modify in place without r

Re: why bash completion sometimes doesn't work?

Greg Wooledge writes: > By default, Debian installs the bash-completion package, which contains > programmable completions for a whole bunch of commands. This is > enabled by dotting in a file from ~/.bashrc (the code to do this is > at the end of /etc/skel/.bashrc, which becomes the default use

Re: Replace line in file based on pattern

On 1/2/22 11:03 PM, Greg Wooledge wrote: On Sun, Jan 02, 2022 at 09:59:08PM -0500, Paul M. Foster wrote: Regarding "patch", let's consider a "stock" config file from a fresh install (call it NEW), and an existing config which is tweaked for my purposes (call it OLD). Assume I want the stock conf

Re: why bash completion sometimes doesn't work?

On Mon, Jan 03, 2022 at 05:25:31AM +, Long Wind wrote: > when i type "ifdown wl" and press Tab, it shall complete it with full device > name wlx12345 > i believe it's taken from /etc/network/interfaces > but sometimes it doesn't work in buster You're describing "programmable completion", whic

Re: Reasonably simple setup for 1TB HDD and 250GB M.2 NVMe SSD

Em [2022-01-02 dom 23:38:48+], piorunz escreveu: > On 02/01/2022 16:33, Jorge P. de Morais Neto wrote: >> I am currently using compress-force=zstd:12 for the SSD and >> compress=zstd:12 for both HDD (internal SATA and external USB3)¹. >> Despite the strong compression level, performance is pre

Re: cpan

Thanks, I had no idea that would work! On Mon, 3 Jan 2022, Jeremy Ardley wrote: > Pipe the output of the cpan command to less? > > | less > > On 3/1/22 1:14 pm, Jude DaShiell wrote: > > when displaying results from a cpan search, is it possible to limit the > > number of displayed results to th

Re: Packaging help: users and directories

Got access to salsa.debian.org today! Woot! On Thu, 30 Dec 2021, 08:55 Gavin Henry, wrote: > Thanks! > > I've managed to build it. Just going through debuild now to clean up > lintian issues and pbuilder. > > Suprisingly enjoyable! > > I've emailed the VoIP packaging group to see if I can help n

Re: [FIXED] Re: brltty=huge distraction for folks that don't need it.

On Monday, January 3, 2022 1:59:56 AM EST john doe wrote: > On 1/3/2022 4:44 AM, gene heskett wrote: > > On Sunday, January 2, 2022 9:57:05 PM EST Jean-Philippe MENGUAL wrote: > >> Hi, > >> > >> Le 02/01/2022 à 23:53, gene heskett a écrit : > >>> Greetings All; > >>> > >>> Without any conscious p

Re: brltty=huge distraction for folks that don't need it.

On Sunday, January 2, 2022 10:47:08 PM EST David Wright wrote: > On Sun 02 Jan 2022 at 22:31:27 (-0500), gene heskett wrote: > > On Sunday, January 2, 2022 9:54:29 PM EST David Wright wrote: > > > On Sun 02 Jan 2022 at 17:53:19 (-0500), gene heskett wrote: > > > > Without any conscious prompting by