"The package system is broken"

[Aravisian]

@total_linux_n0ob

Out of interest, what do you mean by "if there is an additional repository added to your system that is also trying to supply an Unsigned Kernel"?

My answer will cover Hypothetical situations in which a person could have this happen.
Let's say that a Zorin OS user wants a package that is developed by the Pop_OS team. They add the Pop_OS repo and install the package... But they forget to remove the repository after installing the wanted package.
This is true for if you wanted a package from the LinuxMint team.

Or if a person installed a repository for a Later Version of Kernel such as outlined here:

16.3 is supposed to have kernel 6.2 but Lite still has 5.15

Yes, it may be helpful for certain users that have very new hardware and need a later kernel. This may also be of benefit when Zorin OS 17 arrives, since TuxInvader mainline kernel is currently for Focal Only. It provides only Unsigned kernels, so they will not work with Secure Boot which may be a deal breaker for some users. NOTE the warning: If your Ubuntu install works great with Ubuntu’s vanilla kernel(s) do not switch to a mainline build idly. If you can’t think of a reason why you ne…

(The above only contains Unsigned Kernels).

If the user then Updates/Upgrades the system, it will try to pull from that added repository, including the later kernel, even if it is a different kernel than the vetted released Zorin OS Kernel.

Hope this helps and I have marked your post as the solution to the thread.