Reloading Synaptic threw up an error message which told me to run a sudo dpkg configure to fix the problem. See Screenshot below. Running this configure seemed to send me round a loop no matter which options I chose (Y or N)
A complete software update via control centre got locked into the same loop..!

Having recently made first ever Snapshot; though untested, I decided to wipe my HP G60 Laptop’s SSD and install Loc-OS to play with and evaluate.
Deciding to go back and see if this Snapshot actually worked..? It worked faultlessly off the memory stick so used Install via the Control Centre – everything working as it should with all my files and directory structures as it was. Very impressed.
However rebooting after a successful update I found that Synaptic was showing that a plethora of packages needed updating (see imgur pictures)
https://imgur.com/a/IRL8cKk

I marked all of the packages for updating and clicked Apply – everything seems okay after a few weeks of use and reloading Synaptic many times gives no issues.
As to why Synaptic and dpkg config threw a wobble in the first place – I do not know – perhaps trying to add more LXDE packages for keyboard shortcuts etc?

Attached Thumbnails

 

The wobble was caused by a bad package of nano as one of your screenshots shows.
I fixed this and so when you next upgraded you got the wobble-free version of nano.
No lxde shenanigans were involved

1 members found this post helpful.

Hey, thanks for that – I thought it was me tweaking my Antix-LXDE setup.

Love that word – shenanigans – have not seen it used in decades..!

Back to rock solid reliability again without a whiff of Lubuntu. Superb

I know you have written that you do not want Antix to be a Lubuntu type version of Debian but that is what I have got with Antix-LXDE only way better than Lubuntu users can dream of. My original miniMAX was a tweaked version of Lubuntu based Trisquel-mini. To peal off that unwanted unnecessary ubuntu layer is a major bonus with Antix-LXDE. Another major bonus is that I am not having to use Lubuntu’s LXQT mess; such that I can run as fast as my hardware or any other hardware will allow.

As you know I cannot abide inefficiency in any form; stemming from my engineering skills. I see no reason whatsoever for restricting Antix to old or low specification computers. My miniMAX (Antix-LXDE) is just as good on an i7 laptop-computer as it is on this 2008 HP G60 3GiB laptop.

It isn't!!!

I was using it for years, since the demise of #! (crunchbang), on any & all of my computers, from decades old to fairly recent, (never bought cutting edge, as you would have to wait for drivers to be written for them in Linux).

Wiped ZorinOS-16 from my Dell Latitude E6420 Laptop..

Memory: RAM: total: 7.73 GiB
CPU: Info: model: Intel Core i7-2640M bits: 64 type: MT MCP arch: Sandy Bridge gen: core 2 - Speed (MHz): avg: 1642 high: 3292 min/max: 800/3500 scaling: driver: intel, bogomips: 22349

Installed Antix-22 base, but wiped that too as could not get efficiency better than 198MiB RAM at idle – most tests gave around 225MiB and that was with LXDE. So I installed the snapshot from my old 2008 HP G60 Laptop – Antix-22 Full LXDE with Gimp, Drawing, LO, Hardinfo, openshot, and Simple Screen Recorder added.
Noticed that the fan does not run so often or for long - a bit unnerving - suppose I will get used to the silent operation?

So I now have two near identical Antix-LXDE installations on two diverse laptops.

Antix had a very minor wobble again when Synaptic fully removed the unused calendar app Calcurse:
It threw up an error about sandboxing - see attached
I do not need anything fixing but suspect Anticapitalista keeps a critical eye for perfection?

I suppose calcurse will stay in the menu listing as "remove from menu" app does not work under LXDE menu-manager does not work either? No problem as everything else is very good.

Thanks -

Attached Thumbnails

 

That is not AntiX having a "wobble", it's a bug in Synaptic that affects multiple distros.

1 members found this post helpful.

Hey Boughtonp - Thank you
I was suspecting it was a permission issue...

It is a permission issue - Apt prefers to run as _apt user (not root), but Synaptic is storing temporary files within root user's home - a directory that the apt user doesn't have permission to access. Since Apt can regain root permissions, it does so, emits the warning, and keeps going, but Synaptic shouldn't be using that directory.

1 members found this post helpful.

Thank you so much for full description in understandable terminology - appreciated