On 3/1/25 09:33, Greg wrote:

On 2025-03-01, gene heskett <gheskett@shentel.net> wrote:

On 3/1/25 07:20, Richmond wrote:

It's worth reading this too.

https://blog.mozilla.org/en/products/firefox/update-on-terms-of-use/

Which, while rewriting it to use more palatable language, does not
change it to where it only needs lots of salt.

What about Chromium? Or let's write one ourselves!!!

Chromium has hijacked port 80 for google's exclusive use, bypassing
totally my /etc/hosts file for my local network. If I want to use it to
my local network, I'd have to convert my local net to all https access
on ipv6. I can still watch klipper running a local 3d printer with
firefox just by typing e5p or mks into the firefox address bar.

I did use chromium for that for a year or so, but no more so its been
expunged from my installs.  Now my fav slicer, prusaslicer has gone to flatpak, not AppImage as of 2.9.0 and no one can tell me how to make
that work on an amd64 with 32Gigs of ram and a 6 core I5. so I'm stuck
at 2.8.1, which is an AppImage which works but has some warts. The odd
part is that flatpaks work fine on my armbian installs, as the arm64 ff
has been a flatpak most of a year now with automatic weekly updates..
Why can't I make a flatpak work on amd64?  But this is what I get: With
a link from PS290 to the executable, unpacked zip.

error: app/com.prusa3d.PrusaSlicer/x86_64/master not installed

and there is no such file available to install. Not in synaptic, nor
available on prusa's site.  And I've gone thru all the upgrade steps on prusa's site to install flatpak 4 times now.  So whats the magic secret
sauce that is missing?  Thank you All.

I guess that would be easier said than done.

The thing that irks me is that they have replaced my daily tour icons
on the opening screen with their obviously for sale commercial links
which now occupy many of my favorite spots with their BS links I've yet
to grace with a single click. Displacing my own popularity choices.
Color me disgruntled.

Cheers, Gene Heskett, CET.

.

Cheers, Gene Heskett, CET.
--
"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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, Mar 01, 2025 at 15:43:39 -0500, gene heskett wrote:

Chromium has hijacked port 80 for google's exclusive use, bypassing totally my /etc/hosts file for my local network.

You keep saying this, but nobody else is having this issue.

The closest approximation to your experience that anyone has been able to
come up with is:

Local host names don't work because the browser is using DNS over HTTP.
This configuration can be changed.

It's also possible that you've got some bizarre firewall configuration.
Or that your local web service isn't listening on all interfaces.
Or there's just a misconfiguration of *some* part of the name resolution system.

Simply repeating your claim over and over, after other people have
offered suggestions on how to fix it, is not helpful. It almost seems
that you would prefer to *have* a problem that you can gripe about
constantly, rather than to *fix* said problem.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 3/1/25 16:11, Greg Wooledge wrote:

On Sat, Mar 01, 2025 at 15:43:39 -0500, gene heskett wrote:

Chromium has hijacked port 80 for google's exclusive use, bypassing totally >> my /etc/hosts file for my local network.

You keep saying this, but nobody else is having this issue.

The closest approximation to your experience that anyone has been able to come up with is:

Local host names don't work because the browser is using DNS over HTTP.
This configuration can be changed.

How Greg? or better yet, where? I'll reinstall it and change it if I
knew how to change it. I do not enjoy being the odd man out.

It's also possible that you've got some bizarre firewall configuration.

Or that your local web service isn't listening on all interfaces.
Or there's just a misconfiguration of *some* part of the name resolution system.

Simply repeating your claim over and over, after other people have
offered suggestions on how to fix it, is not helpful. It almost seems
that you would prefer to *have* a problem that you can gripe about constantly, rather than to *fix* said problem.

.

Cheers, Gene Heskett, CET.
--
"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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, Mar 01, 2025 at 16:49:05 -0500, gene heskett wrote:

On 3/1/25 16:11, Greg Wooledge wrote:

On Sat, Mar 01, 2025 at 15:43:39 -0500, gene heskett wrote:

Chromium has hijacked port 80 for google's exclusive use, bypassing totally
my /etc/hosts file for my local network.

You keep saying this, but nobody else is having this issue.

The closest approximation to your experience that anyone has been able to come up with is:

Local host names don't work because the browser is using DNS over HTTP.
This configuration can be changed.

How Greg? or better yet, where? I'll reinstall it and change it if I knew
how to change it. I do not enjoy being the odd man out.

https://www.google.com/search?q=how+to+stop+chromium+using+dns+over+http

AI Overview

To stop Chromium from using DNS over HTTPS (DoH), navigate to your
browser settings, go to "Privacy and security" then "Security", and
under the "Advanced" section, toggle off the "Use secure DNS" option;
this effectively disables DoH in Chromium.

Or follow any of the human-written links that are provided as well.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 3/1/25 17:06, Greg Wooledge wrote:

On Sat, Mar 01, 2025 at 16:49:05 -0500, gene heskett wrote:

On 3/1/25 16:11, Greg Wooledge wrote:

On Sat, Mar 01, 2025 at 15:43:39 -0500, gene heskett wrote:

Chromium has hijacked port 80 for google's exclusive use, bypassing totally
my /etc/hosts file for my local network.

You keep saying this, but nobody else is having this issue.

The closest approximation to your experience that anyone has been able to >>> come up with is:

Local host names don't work because the browser is using DNS over HTTP.
This configuration can be changed.

How Greg? or better yet, where? I'll reinstall it and change it if I knew
how to change it. I do not enjoy being the odd man out.

https://www.google.com/search?q=how+to+stop+chromium+using+dns+over+http

AI Overview

To stop Chromium from using DNS over HTTPS (DoH), navigate to your
browser settings, go to "Privacy and security" then "Security", and
under the "Advanced" section, toggle off the "Use secure DNS" option;
this effectively disables DoH in Chromium.

Or follow any of the human-written links that are provided as well.

it still disabled after turning that off, Greg.  Only works if I use the
ipv4 address of that 3d printer.  Noticeably a hell of a lot faster than firefox-esr which is why I liked it in the first place.  Is there
something else I should turn on?

chromium also try's to open kwallet at launch time but does not accept
my pw and root pw has not been set as I use sudo for

ALL of  that stuff.  Tnx.

.

Cheers, Gene Heskett, CET.
--
"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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sat, Mar 01, 2025 at 22:55:06 -0500, gene heskett wrote:

On Sat, Mar 01, 2025 at 15:43:39 -0500, gene heskett wrote:

Chromium has hijacked port 80 for google's exclusive use, bypassing totally
my /etc/hosts file for my local network.

[Turn off DNS over HTTP.]

it still disabled after turning that off, Greg.  Only works if I use the ipv4 address of that 3d printer.  Noticeably a hell of a lot faster than firefox-esr which is why I liked it in the first place.  Is there something else I should turn on?

At this point, we need the full details.

* What version of Debian?
* What version of Chromium?
* What is the EXACT thing you are typing into the URL bar?
* After you press Enter, what does Chromium rewrite the URL bar to (i.e.
what do you see without clicking on it)?
* Triple-click the rewritten URL bar, and then paste it.
* What results do you see in the browser?

And some additional background details:

* grep hosts /etc/nsswitch.conf
* ls -ld /etc/resolv.conf
* cat /etc/resolv.conf

And for whatever local name $NAME you're putting into the URL bar:

* getent hosts $NAME
* grep $NAME /etc/hosts


I'm not using Chromium, but I'll start by showing what I get in Google
Chrome:

hobbit:~$ cat /etc/debian_version
12.9

hobbit:~$ dpkg -l google-chrome-stable | tail -n1
ii google-chrome-stable 133.0.6943.141-1 amd64 The web browser from Google

What I type into the URL bar: http://hobbit

After pressing Enter, it says: hobbit/

After triple-clicking, it pastes as: http://hobbit/

What I see in the browser: =========================================================
This site can’t be reached
hobbit refused to connect.
Try:

Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_REFUSED =========================================================

hobbit:~$ grep hosts /etc/nsswitch.conf
hosts: files dns

hobbit:~$ ls -ld /etc/resolv.conf
-rw-r--r-- 1 root root 84 Feb 9 09:04 /etc/resolv.conf

hobbit:~$ cat /etc/resolv.conf
# Generated by resolvconf
domain home
search wooledge.org home
nameserver 127.0.0.1

hobbit:~$ getent hosts hobbit
127.0.1.1 hobbit.wooledge.org hobbit

hobbit:~$ grep hobbit /etc/hosts
127.0.1.1 hobbit.wooledge.org hobbit

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 3/2/25 04:55, gene heskett wrote:

On 3/1/25 17:06, Greg Wooledge wrote:

https://www.google.com/search?q=how+to+stop+chromium+using+dns+over+http

   AI Overview

   To stop Chromium from using DNS over HTTPS (DoH), navigate to your
   browser settings, go to "Privacy and security" then "Security", and
   under the "Advanced" section, toggle off the "Use secure DNS" option; >>    this effectively disables DoH in Chromium.

Or follow any of the human-written links that are provided as well.

it still disabled after turning that off, Greg.  Only works if I use the ipv4 address of that 3d printer.  Noticeably a hell of a lot faster than firefox-esr which is why I liked it in the first place.  Is there
something else I should turn on?

This is a known problem of the chromium engine.
It's called 'Async DNS resolver'.

<https://bugdrivendevelopment.net/browser-ignore-internal-dns/>
gives some hints that you may try, but according to <https://stackoverflow.com/questions/78393737/chrome-ignores-local-dns-despite-flag-settings>
they don't work (anymore?).

What I've read (in an artice in a German magazine that's behind
a paywall (<https://www.heise.de/select/ct/2024/9/2406014455006618241>)
the only thing that really works is if you setup your own DoH server
and tell Chromium to use it:
In chrome://settings/security:
- enable "Use secure DNS"
- "Select DNS provider": "Add custom DNS service provider"

But I haven't tried it myself.

Detlef

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)