So the big thing about having an organization to help support a massive operating system is that all the parts are supposed to function as one, right?

So why has Canonical kept releasing kernel versions that aren't even compatible with the system due to requiring a library that isn't even compiled with the system?

Next question: Why was this chosen for the mainstream supported OS on GOG, instead of something with a better reputation for upgrades and support? (Instead of backports and patched out the wazoo.)

Canonical's choice of kernels has always been... interesting to say the least. They usually don't care much about the official LTS support and go with whatever's available. Their backported HWE kernels are also poorly tested also come with issues, missing firmware etc. Probably because it's what developers provide wide support for and test on. Though why this is not Arch or simply Debian beats me.

linux is perfect , and clearly distro flood is not a problem at all
i wonder why anybody still uses ubuntu

Well, that'll hopefully change with the Steam Deck.

Because, for better or for worse, as far as beginner friendly and "mainstream" goes Ubuntu is the closest you can ever find, Mint being a close second. Most users don't care about the kernel thingy or whatever workaround they only want something that works out of the box with as little hassle as possible.

I must admit I am not fully sure what that long discussion was about.

Was it about LTS users, who wish to use newer "experimental" kernels that are unofficially available for their LTS, have now some kind of dependency problem? Or is this an issue that affects all LTS (e.g. Ubuntu 20.04) users, and they are unable to successfully run sudo apt update && sudo apt full-upgrade && sudo apt autoremove anymore?

If it is the former, then it is not a problem for your normal Ubuntu user, I guess.

It's definitely not a problem for regular users, since they will stick with whatever ancient kernel came with their Ubuntu version (5.4 for the current LTS).

[url=https://kernel.ubuntu.com/~kernel-ppa/mainline/]Mainline kernels[/url] are simply bleeding edge packs provided by Canonical outside of regularly supported kernels. If there's a place for problems and breakage, this is it, though it is handled somewhat poorly even so.

thats why they chose win10 ,hope linux will be able to reach the same level

Ok then, I guess I understood it mostly correctly then. It was hard to tell from the discussion how widespread the problem really is, and if it was affecting all Ubuntu 20.04 LTS users, it would totally be in the headlines, instead of some odd discussion somewhere.

I guess it is safe for me to update a few 18.04 and 20.04 servers at work next week, then... I was already wondering if I had to postpone their updates until this problem is sorted out (if it isn't already).

Yeah I guess it sucks for people who want newer kernels because of support for some brand-new piece of hardware etc. I guess in such case I would use some more frequently updated distro, like Fedora or Manjaro or whathaveyou. Or couldn't they use Ubuntu 21.04 instead, if they have to be so bleeding edge?

(Yeah I still have nightmares about using Fedora, how unstable it was for me for being so bleeding edge, but that was many many years ago and I don't know if it is still that overly "beta" when a new Fedora release comes out. And I recently did run into a dependency problem in Manjaro, when running the normal sudo pacman -Syyu ; the fix was to run "pamac update" instead, it somehow sorted out the dependency problem, and pacman would work after that as well.)

I guess. Maybe two months ago I was trouble-shooting my relative's Windows 10 update problems, it wouldn't update for him but gave some cryptic error message instead. With googling I finally found out how to manually sort that one out, and he was able to once again receive Windows 10 updates.

Also many many years ago a friend's Windows 8.1. would boot into a black screen after some failed Windows update. I had to reinstall it from scratch, even safe mode didn't work for some reason.

all this package thing is so badly thought out, isnt it there to make sure an app have the correct dependencies , yet for some reasons it just doesnt work well, and distros use different managers just make it worse
probably it is is just badly made in the first place and they have to use the system to be backward compatible :I
some even call it dependence hell ... not promising at all

no wonder those image files appeared similar to what windows apps look like

yeah it can happen on win too if some apps missing dependencies but that is rare and easy to fix

Wait, did you inadvertently figure out how to disable windows updates? Any way I could reproduce this? On my todo list is to get an HDD for the HDD expansion slot in this computer so i can disable the wireless driver in windows and install linux and have a dual boot system. I could use something to buy me time so i'm not forced into win11, since i'm not made of money for getting that HDD.

it should be easy just disable the update service
win11 looks cool , i wanted to try out the style on manjaro kde but that failed to put the icons in the middle ... i dunno whats wrong with linux but every time i want to do something it just fails

That's what i thought. Try it once, though. WIndows will only let you do it for so many days.