There is something wrong therefore with your subscription… or the esm repos are still being resurrected. This is Canonical matter. Not something flavours can easily help with. Suggest raise a support request here on discourse.ubuntu.com and tag it esm in the support category.
For others reading this later, a flavours commitment with Canonical is max 3 years after a release. So jammy ended Apr 2025.
Noble ends Apr 2027 and the just launched resolute ends Apr 2029.
Understood. I understand that you can no longer help me with this.
But the flavours are with Canonical. Over and out.
Could you send the contents of /etc/apt/sources.list?
Thanks jlb but I have had enough of this. I will be leaving the distro. It is clear that ESM means nothing when the chips are down. Adios and thank you.
You’re welcome.
You’re free to go, of course, but just one question before you leave: why didn’t you upgrade to UB 24.04?
Besides, I don’t think that’s the cause of your problem: on my multiboot system, I have a distribution that’s also based on Jammy (Zorin 17), and its updates are still going smoothly, even without ESM.
With Ubuntu Pro, security support for Ubuntu 24.04 will extend until 2034:
Good question.
The simple reason was Ubuntu Pro.
I understood that I would be supported in terms of security. Older versions of Ubuntu are also more stable and this appealed too. This was offered and promoted by this flavour of Ubuntu so I decided to go with that.
Had Ubuntu Pro not been offered by this flavour of Ubuntu I would not have subscribed to it in the first place-obviously. But it was-and I did.
I have had a conversation with you before where I stated that security and stability was my primary consideration.
The DDOS attack is the problem. Everything was running smoothly until then. The problems I am experiencing are definitely connected to this. I previously thought it was the kernel I upgraded to but am satisfied that is not the source thanks to Fossfreedom’s response.
I was patient as Fossfreedom recommended. But there is a limit.
This has been an ongoing problem since the end of April. And he knows those engineers..
Not sorted. And after all this time to be told that it is a Canonical problem and to talk to them..no thanks.
I have appreciated the responses received previously from Fossfreedom and the timely responses.
However the latest response was most disappointing. It was a deal-breaker.
Maybe Zorin from now on-I will check it out!
could not resolve error messages are basically DNS issues.
Given that jammy is out of support from this flavour point of view, the OP has been guided to the correct forum for future support.
Thus I’m closing this topic.
