That last image is not a login screen, but a "Unlock the volume" password entry screen. The words are pretty clear about that 🤐

This seems also to be a duiplicate of your previous question.

@mook765 This literally happened to me. They were saying "It's impossible to have a 1GB update" but that's what happened to me, and I want to get feedback about this from the experts here. Please don't close this!!!! My computer is literally broken now from a 1GB update. I'd like some feedback from the community is all. And yes this really happened.

@matigo I hope you at least read my whole post thoroughly because I explain everything in detail.

I really want the Ubuntu experts to see this post, I want to hear what the experts have to say about what happened to me. Yes I had a 1GB update and it broke my computer. I'm not a computer expert at all and I just want some feedback. Honestly I can't believe this even happened to me, it's very frustrating. I never would have thought that a simple update would break my machine, something like this never happened to me on Windows.

Use the supported kernels for Ubuntu 22.04 LTS, stable is still 5.15 last I checked, with -edge being 5.19, with a few other OEM options, but you've added many different testing kernels. Use them for testing & report your findings, or if you want a stable system, stick to a supported kernel (which receives all security fixes & patches automatically for the life of the product, instead of you doing it yourself).

@guiverc "but you've opted to not use a supported kernel" I promise you I haven't opted to do anything, the computer prompted me and told me that an update was available, and it was just under a gigabyte as I remember, so I said sure go ahead and update. I didn't change anything or opt for anything, I just simply said sure go ahead and update. This thing is bugged.

-1: I think this story will confuse more future readers than it helps. The assertion that a large Ubuntu update was the primary cause of breaking the system seems unsupported. It seems more likely that the chain of decisions by the user doomed it, and that the update was merely a proximate cause that nudged the already-teetering system over the edge. The story and images show a tale of kernel experimentation --and corresponding lack of clean-up afterward-- that could reasonably be expected to expose bugs and crashes that might limit basic functionality.

@user535733 Hey come back here and read the post again as I made another edit, I included more information. This update broke my computer, I wasn't experimenting with anything, I'm a total novice when it comes to Linux. I'm telling you this weird 1GB update that I just got out of the blue broke my computer.

If you get rid of all those unnecessary kernel packages you won't get updates for them and your download will be a lot smaller. Since you manually installed all those kernel packages, you are complaining about a self-inflicted problem. It didn't come out of the blue, you did it.

I'm a total newb when it comes to Linux, what unnecessary kernel packages are you talking about, I'm not sure what you mean here, I know I added extra programs like Dolphin file manager, TOR, Brave browser, VLC, PeaZip, and some others, is this what you mean by unnecessary kernel packages? Can you please explain to me exactly what you mean?

@Cool124 - reading the comments, you’ve got a whole load of unusual kernel packages you didn’t even know you’d installed. I think your best option is to reinstall a fresh 22.04LTS and restore your data from backup.

The first two screenshots of the Updater GUI show a bunch of kernel modules to be updated, and (as guiverc pointed out) some are with version numbers that are not yet released as stable (in other words, early, almost like experimental releases). All those redundant kernels got onto your computer somehow, and we seem to conclude that you installed them. Linux is extremely customizable, but it does not mean that it has to be customized heavily as an everyday lifestyle. Customizations do have a price wherein they introduce degraded stability. The more you customize, the more the surprises.

@Will I don't even know what a kernel is. I'm being serious.

@Levente I made another edit to the post to include more information, can you please come back here and read it? Thanks.

I think others' comments have been pretty clear. The only thing I would add is that it's great that Linux/Ubuntu has attracted novices like yourself. You asked for some expert advice -- my advice to you is if you're new to Linux/Ubuntu, this is normal. We've all been there when we were starting out. Don't give up on Linux, but play with it on a "junk" computer that isn't your main computer -- get an old, used one that you can break, erase, format, etc. many times over. That's the only way you will learn. Keep your main computer on the OS you're familiar with (Windows, etc.) until you're ready.

"I have entered some things in the command line to fix bugs but I haven't done any customizing to Ubuntu". That was enough to break the system. If you didn't mean to install kernels, and have no idea what the commands mean, then it doesn't mean that you didn't install kernel.

You mention bug a few times, where if this is the result of a Ubuntu bug, the bug was during installation, as the issue is as I see it anyway the many kernels that co-exist that should not co-exist on an install. I regularly have GA & HWE kernels co-exist as they can, but I rarely use NVidia closed kernel modules (drivers) as they create problems if more than a single is installed. On your system I see many, and you've not said how they were installed (many OEMs are listed); I believe it was by user install - thus user-created issue, but you've given no clear clues. I'd check your apt logs

how do I check my apt logs? I'm a newb so please explain?

@guiverc what command do I enter in the command line to check my apt logs? Thanks