Hello:

Exim4 had a huge lot of issues at one point and it could be that (depending on your installed version / upgrade cycle) you are suffering them now.

You may want to have a read at this thread (specifically the last two posts) to get an idea of what may be going on in your box.

https://dev1galaxy.org/viewtopic.php?pid=30412#p30412
https://dev1galaxy.org/viewtopic.php?pid=30469#p30469

That said and unless you really need something as complex as exim4 running in your box, you may want to consider using a simpler, much lighter and less complicated MTA such as Dragonfly.

See this thread and the DragonflyBSD web page.

Best,

A.

Hello:

So it seems:

File has unexpected size (32 != 12976). Mirror sync in progress?    # <- this 

You may want to consider marking the problem as [Solved].  8^)

Best,

A.

Hello:

Exactly ...
Seems to me that you knew the answer before posting the question. ;^ )

+1

Best,

A.

Hello:

No, I have never used emacs.

To tell you the truth, I don't have much of an idea about it save that it is a well known and very difficult to learn text editor.
One over which (in comparison to Vi) long wars have been fought on the old usenet. (?)

Using it is way above my pay grade, something I expect you already know.

Please see above.

Just so you know, I use jed, nano or mc to edit files.

Hmm ... [Not good day, is it?]

So ...
How is the weather in Battery Point this morning?
I hope it is not raining.

Thank you very much for your input.

Best,

A.

Hello:

Like you said:

~$ df -k /var/run
Filesystem     1K-blocks  Used Available Use% Mounted on tmpfs               # tmpfs
806412   832    805580   1% /run
~$ 

~$ ls -lid /var/run
913937 lrwxrwxrwx 1 root root 4 May 21  2017 /var/run -> /run                # symlink
~$ 

~$ lsattr /etc/resolv.conf
lsattr: Operation not supported While reading flags on /etc/resolv.conf      # same error with [chattr +i]
~$ 

~$ lsattr /var/run/connman/resolv.conf
---------------------- /var/run/connman/resolv.conf
~$ 

~$ lsattr /run/connman/resolv.conf
---------------------- /run/connman/resolv.conf
~$ 

Like I said before, with respect to connman and what it does with /etc/resolv.conf:

Thanks for your input.

Best,

A.

Hello:

Yes.

Check here.
It is the Debian/Ubuntu Wiki which should serve as a guide.

See also the posts in this search result.

Most if not all of them relate to the same problem you are having, probably some installation step skipped/gone south.
But should push come to shove, you can always purge everything Wine from your system and start over.

HTH.

Best,

A.

Hello:

Why would you think that?
I'm up to date, with no bugs.

~$ uname -a
Linux devuan 6.1.0-25-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.106-3 (2024-08-26) x86_64 GNU/Linux
~$ uname -a

~$ sudo apt update
--- snip ---
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
~$ 

While it is not quite clear where the problem may lie, you may want to consider trying the simplest approach first.
eg:

1. empty your Downloads folder, getting rid of all traces of any partly downloaded/unnecessary files, including those in the Trash folder.
2. use wget to download the file.

From the quick look I had, Prusa Slicer 2.8.1 appimages can be downloaded from GitHub but from what the page indicates, they are either 90.2Mb or 94.2Mb, depending on your choice. ie: not 4Gb

So that would be something like this:

~$ wget https://github.com/prusa3d/PrusaSlicer/releases/download/version_2.8.1/PrusaSlicer-2.8.1+linux-x64-newer-distros-GTK3-202409181416.AppImage

It worked perfectly well for me:

~$ wget https://github.com/prusa3d/PrusaSlicer/releases/download/version_2.8.1/PrusaSlicer-2.8.1+linux-x64-newer-distros-GTK3-202409181416.AppImage
--2024-09-21 16:38:44--  https://github.com/prusa3d/PrusaSlicer/releases/download/version_2.8.1/PrusaSlicer-2.8.1+linux-x64-newer-distros-GTK3-202409181416.AppImage
Resolving github.com (github.com)... 20.201.28.151
Connecting to github.com (github.com)|20.201.28.151|:443... connected.
HTTP request sent, awaiting response... 302 Found
--- snip ---
Connecting to objects.githubusercontent.com (objects.githubusercontent.com)|185.199.108.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 98731200 (94M) [application/octet-stream]
Saving to: 'PrusaSlicer-2.8.1+linux-x64-newer-distros-GTK3-202409181416.AppImage'

PrusaSlicer-2.8.1+linux-x64-newer-dis 100%[========================================================================>]  94.16M  36.6MB/s    in 2.6s    

2024-09-21 16:38:48 (36.6 MB/s) - 'PrusaSlicer-2.8.1+linux-x64-newer-distros-GTK3-202409181416.AppImage' saved [98731200/98731200]

~$ 

Best,

A.

Hello:

Getting back on track as per my OP.

1.
any NetworkManager files present in my system while that package was not installed can only be adscribed to remnants from either Jesse or ascii - cannot come up with any other explanation.

2.
evidently both NetworkManager and connman take the liberty of screwing around with /etc/resolv.conf which explains the banner left behind by the first.

With respect to whatever/however it is that connman screws around with /etc/resolv.conf, I have not been able to find a clear answer.
Yes, it does edit/replace the file but when and why is still a mystery.

To wit:
Applying chattr +i as sudo/root did not work and connman kept on changing my local DNS setting for my FO provider's.
This in spite of the local DNS address being set both in the FO provider's router and in the connman settings page.

And then, all of a sudden ...
... It has stopped doing it.

Why?
No idea.
Maybe it has a mind of its own?  8^°

The thing is that my local DNS setting has remained as required by me for ~ 48 hours and survived at least a half dozen reboots.
If it acts up again, I will just nuke the symlink and reinstate /etc/resolv.conf as a text file. 

But still ...
I am not at all happy with not knowing what is going and exactly why.
Much less with applying brute force (chattr +i) to keep it from happening.

So I am planning to approach the solution suggested by Ralph.Ronnquist: use ifupdown.

I found an interesting page with what seem to be a set of comprehensive instructions to make the conversion to ifupdown.

But I'll have to study them before taking any action but I think it is definitely a step in the right direction.

Thank you very much to all those who pitched in.
Marking this one solved.

Best,

A.

Hello:

I see ...

When I left a shared WiFi arrangement to get an ADSL and then went on to fibre, I kept WiCD and a network management application (whatever came with Daedalus as default when I upgraded from Beowulf/Chimaera) just to be able to use a wifi spot nearby, just in case fibre goes down.

But 99% of the time I am using LAN, just like you.
Maybe I should look into doing just that ...  8^°

If you could share your how-to I'd be very obliged.

Thanks in advance.

Best,

A.

Hello:

All this crap has me so annoyed.
It has kept me looking all over the web for anything related to connman+resolv.conf.
There are a great many posts complaining about this same issue, going back as far as 2017 ...

I did find an interesting tidbit with respect to the origins of connman and networkmanager which I could not have imagined.

Who would have guessed?
Those two heavyweights behind a simple application ...

[tin foil]
Make me wonder just much interest they would have in other (competing?) and much less complicated not to mention unobtrusive applications such as WiCD failing or simply just being abandoned. Because, besides connman, networkmanager and WiCD ...

What else is there for Linux?
[/tin foil]

I also found the same opinion/idea already seen in a few forums:

See here.

Also a couple of possible solutions:

See here.

This last one (originally suggested by Ralph.Ronnquist) is what I am interested in doing but I was not so sure as to how to go about it.

Then I found man connman.conf with the explanation to an an entry I had not seen/noticed before and which could be a solution:

* underlining is mine

See here.

But it happens that the entry for etc/connman/main.conf mentioned above is not present in that file so I think that the best go-to solution would be to clobber the resolv.conf with a real file and not a symlink to /etc/connman/resolv.conf.  ie: blunt force, like with a kitchen roach.

Curiously enough, although I have had my box on-line for almost nine hours, so far there has not been a DNS change (!).
So I really do not have a clue as to what is going on with connman or how it decides when to do what it does.

Truth be told, I just want WiCD back. 8^°

Thank your for the instructions, I was thinking of doing more or less the same thing.
What kept me back is the assumption that as it had been set up by connman doing so would break it and things would get worse.

I will wait and see what happens / till I get another DNS change from connman and then proceed.

Thank you very much for your input.

Best,

A.

Hello:

Badly or not-as-expected.

My conky setup queries my DNS and I can see it on-screen.
One moment it was as-expected and the next time I looked it had changed.

As posted previously, I has left it at this ...

~$cat /etc/resolv.conf
# edited by user 17092024
nameserver 192.168.1.11
~$ 

... and now it is this:

~$ cat /etc/resolv.conf
domain Home
search Home
nameserver [my fibre provider DNS]
nameserver [my fibre provider DNS]
~$ 

Maybe I did not do the chattr -f +i /etc/resolv.conf routine correctly?
Cannot say as I am unable to check the file's attrbutes:

~$ lsattr  /etc/resolv.conf
lsattr: Operation not supported While reading flags on /etc/resolv.conf
~$ 

Hmm ...
I finally found what the -f modifier does.
It happens that it does not mean force, it just suppresses error messages.

I will edit the file again, boot into recovery/repair mode and try to set it from there.

What a load of crock ...  8^/
I will report back once I am done.

Best,

A.