Announcement

**claydoh** · Apr 08, 2023, 09:34 AM

Odd, will look into it.

In the meantime:
https://www.kubuntuforums.net/forum/...nels-installed
and
https://www.kubuntuforums.net/forum/...en-won-t-start

Originally posted by Silent Observer View Post

how I can get GRUB to default to boot in 5.15.0-67-generic

Grub-customizer can set defualt boot kernels.

**claydoh** · Apr 08, 2023, 09:58 AM

I am not terribly good with the backend stuff with the software, and I can't see what happened to the thread, Apologies.

Def not moderated. We don't actually do that very often. It well could be that I did something accidentally, or triggered a bug in the software, but I can't see any record of the thread that I clearly remember, and iirc commented on.

No idea what this happened. The kernels are not part of any meta-package that would pull them in at all, and are rather specialized.
They probably didn't work as they are either missing support some some things by design since they are meant for servers or cloud instances (-oracle and -nvidia), and/or DKMS failed to build the modules for some reason (Nvidia drivers, for example)

Normally, these would need to be installed manually, and would not be included an any dependency list on their own.

You can use Muon to search for linux-image and linux-headers, and filter for installed packages. Then select anything with -oem, -nvidia, and -oracle, and uninstall them.

No clue why this has happened, so I can't say they won't be pulled in again, since we don't know what you have installed that is depending on these. But I think it is unlikely. Uninstalling these kernels will also want to remove whatever needs these, perhaps, so it might be useful to post the list of everything that is slated for removal, as well as maybe offered for autoremove afterward.

This sort of thing is not related to Plasma or Kubuntu, since the desktop GUI doesn't depend on kernels and I am not seeing reports of this happening in the Ubuntu and Kubuntu places I haunt, so far.

I suspect some odd piece of software or package from a third party, like a PPA. It would be happening *everywhere* if it was a general packaging configuration bug in a standard *buntu package.
And I don't see three people here at the same time having manually installed the same oddball kernels.

**Silent Observer** · Apr 08, 2023, 03:18 PM

Okay, thanks for the help. I've installed grub-customizer, now to remove those kernels.

I'm used to using Synaptic, so I'm using it trying to uninstall those packages, but it wants to reinstall linux-image-5.15.0-69-generic as part of "complete removal" (= purge) of that package along with some others; it's also wanting to install linux-image-unsigned-5.15.0-1018-nvidia along with upgrading a bunch of what look like driver related packages (which I presume would be fine) when I try to remove the installed (without "unsigned") version. The same applies for linux-image-6.1.0-1008-oem. I'm going to dump the others now (success for those not listed above).

Probably significant: here's a fragment of what I get when I used sudo apt purge linux-image-5.15.0-69-generic:

Code:

The following additional packages will be installed:
 linux-image-unsigned-5.15.0-69-generic
Suggested packages:
 fdutils linux-doc | linux-source-5.15.0 linux-tools linux-modules-extra-5.15.0-69-generic
The following packages will be REMOVED:
 linux-generic* linux-image-5.15.0-69-generic* linux-image-generic* linux-modules-extra-5.15.0-69-generic*
The following NEW packages will be installed:
 linux-image-unsigned-5.15.0-69-generic

Note that it would remove the linux-generic* metapackage. This must be why it needs a reinstall of at least some version of those packages that won't go away.

Just to make sure I don't have something else that might confuse things, I'm pasting in my repository list:

Code:

# deb cdrom:[Kubuntu 22.04.1 LTS _Jammy Jellyfish_ - Release amd64 (20220809.1)]/ jammy main multiverse restricted universe

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://us.archive.ubuntu.com/ubuntu/ jammy restricted main
# deb-src http://us.archive.ubuntu.com/ubuntu/ jammy main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://us.archive.ubuntu.com/ubuntu/ jammy-updates restricted main
# deb-src http://us.archive.ubuntu.com/ubuntu/ jammy-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ jammy universe
# deb-src http://us.archive.ubuntu.com/ubuntu/ jammy universe
deb http://us.archive.ubuntu.com/ubuntu/ jammy-updates universe
# deb-src http://us.archive.ubuntu.com/ubuntu/ jammy-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://us.archive.ubuntu.com/ubuntu/ jammy multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ jammy multiverse
deb http://us.archive.ubuntu.com/ubuntu/ jammy-updates multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ jammy-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ jammy-backports universe restricted main
# deb-src http://us.archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse

deb http://security.ubuntu.com/ubuntu/ jammy-security restricted main
# deb-src http://security.ubuntu.com/ubuntu/ jammy-security main restricted
deb http://security.ubuntu.com/ubuntu/ jammy-security universe
# deb-src http://security.ubuntu.com/ubuntu/ jammy-security universe
# deb http://security.ubuntu.com/ubuntu/ jammy-security
# deb-src http://security.ubuntu.com/ubuntu/ jammy-security multiverse

# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.

deb http://downloads.sourceforge.net/project/ubuntuzilla/mozilla/apt/ all main

I also have the following PPA folders in sources.list.d.

Code:

$ ls
alexlarsson-ubuntu-flatpak-jammy.list  teejee2008-ubuntu-ppa-jammy.list
megasync.list                          trebelnik-stefina-ubuntu-grub-customizer-jammy.list

The only thing I'm aware of that amounts to "pushing" my install is llvm which is needed to have math libraries for a Kerbal Space Program mod that I'm pretty sure at least hundreds of Kubuntu users run. I can post a package list if that will help, but it's biggish...

**Silent Observer** · Apr 09, 2023, 07:08 AM

Thinking about what I might have installed that could have pulled this (though at least one of the bad kernels was apparently pulled by linux-generic metapackage) -- I run GIMP from Snap, Kerbal Space Program manually installed, Vuescan 64 manually installed, GURPS Character Sheet manually installed. The PPA entries above are for Megasync (remote archive downloader I got for itch.io distributed indy games), grub-customizer, and flatpak, which ought not to pull anything as dependencies (and doesn't show any dependencies anyway).

Everything else installed is from main, backports, multiverse, universe, or restricted.

Could this be coming from something installed via backports (Libre Office)? Those are packages from newer Ubuntu versions, ported to work on this LTS, right?

**claydoh** · Apr 09, 2023, 09:34 AM

Originally posted by Silent Observer View Post

though at least one of the bad kernels was apparently pulled by linux-generic metapackage)

if the linux-generic metapackage pulled these in, it would have affected *everyone*, or at least a very significant portion of those running *buntu and unofficial variants.
Unless it was a mistake that was caught so fast that only a small few were caught but it (pure conjecture here. There are interconnecting and overlapping meta-packages, virtual packages, and all sorts of other goodies involved in Debian packaging).

Even PPAs would be a low-chance cause, I think.

Originally posted by Silent Observer View Post

Could this be coming from something installed via backports (Libre Office)? Those are packages from newer Ubuntu versions, ported to work on this LTS, right?

The versions of the packages installed don't seem to be from jammy-backports. Still, this would have affected most people.
An example:

Code:

apt policy linux-image-5.15.0-69-generic
linux-image-5.15.0-69-generic:
Installed: 5.15.0-69.76
Candidate: 5.15.0-69.76
Version table:
*** 5.15.0-69.76 500
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status

Now, these could have previously been in jammy-proposed, but that definitely takes manual intervention to enable (and it isn't seen in your sources.list)

Now, as to your PPAs, what is this one from, exactly?
alexlarsson-ubuntu-flatpak-jammy.list

If it is from HERE, it would not have any Jammy packages to begin with - it is old, no packages past 20.04. You should be seeing errors/warnings about it in apt.
You can safely delete that file. This has no effect on these odd kernels, though.

**claydoh** · Apr 09, 2023, 10:20 AM

Also, your sources.list need fixing:

Code:

deb http://security.ubuntu.com/ubuntu/ jammy-security restricted main
# deb-src http://security.ubuntu.com/ubuntu/ jammy-security main restricted
deb http://security.ubuntu.com/ubuntu/ jammy-security universe
# deb-src http://security.ubuntu.com/ubuntu/ jammy-security universe
# deb http://security.ubuntu.com/ubuntu/ jammy-security  <-----------------------------THIS
# deb-src http://security.ubuntu.com/ubuntu/ jammy-security multiverse

should be:

Code:

deb http://security.ubuntu.com/ubuntu/ jammy-security multiverse

It needs to be un-commented, and have 'multiverse' at the end.
This also isn't any reason for the odd kernel installs. But it is good to have all security updates available

**Silent Observer** · Apr 09, 2023, 11:21 AM

I don't recall where the alexlarsson-ubuntu-flatpak-jammy.list came from, but probably got upgraded from 20.04 to 22.04 during my failed upgrade attempt and install-over to fix my system, over Christmas break. Obviously, I had it there to be able to install a flatpak, but I don't recall which -- maybe I had a flatpak version of SeaMonkey browser on 20.04, but got it from multiverse after my upgrade was completed. As you note, Synaptic doesn't show any packages installed from it.

I've removed it, and updated the jammy-security line as you recommend. After doing so, ran sudo apt update and sudo apt dist-upgrade, got no changes but once again saw the "advertising" recommendations for the Ubuntu Pro security extensions....

I get the same you do on policy:

sudo apt policy linux-image-5.15.0-69-generic
linux-image-5.15.0-69-generic:
Installed: 5.15.0-69.76
Candidate: 5.15.0-69.76
Version table:
*** 5.15.0-69.76 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
100 /var/lib/dpkg/status

But then:

$ sudo apt policy linux-image-5.15.0-1018-nvidia
linux-image-5.15.0-1018-nvidia:
Installed: 5.15.0-1018.18
Candidate: 5.15.0-1018.18
Version table:
*** 5.15.0-1018.18 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status

and:

$ sudo apt policy linux-image-6.1.0-1008-oem
linux-image-6.1.0-1008-oem:
Installed: 6.1.0-1008.8
Candidate: 6.1.0-1008.8
Version table:
*** 6.1.0-1008.8 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
100 /var/lib/dpkg/status

These are the three I can't remove without Synaptic (presumably to fulfill some dependency) wanting to install an alternative version.

if the linux-generic metapackage pulled these in, it would have affected *everyone*, or at least a very significant portion of those running *buntu and unofficial variants.
Unless it was a mistake that was caught so fast that only a small few were caught but it (pure conjecture here. There are interconnecting and overlapping meta-packages, virtual packages, and all sorts of other goodies involved in Debian packaging).

If that were the case, would reinstalling linux-generic fix the dependencies and let me at least remove the stuck -nvidia and -oem packages? Or would that have other unwanted effects?

$ sudo apt reinstall linux-generic*
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'linux-generic-hwe-20.04' for glob 'linux-generic*'
Note, selecting 'linux-generic' for glob 'linux-generic*'
Note, selecting 'linux-generic-hwe-22.04' for glob 'linux-generic*'
Note, selecting 'linux-generic-hwe-20.04-edge' for glob 'linux-generic*'
Note, selecting 'linux-generic-hwe-22.04-edge' for glob 'linux-generic*'
The following additional packages will be installed:
linux-headers-5.19.0-38-generic linux-headers-generic-hwe-22.04
linux-headers-generic-hwe-22.04-edge linux-hwe-5.19-headers-5.19.0-38
linux-image-5.19.0-38-generic linux-image-generic-hwe-22.04
linux-image-generic-hwe-22.04-edge linux-modules-5.19.0-38-generic
linux-modules-extra-5.19.0-38-generic
Suggested packages:
fdutils linux-doc | linux-hwe-5.19-source-5.19.0 linux-hwe-5.19-tools
The following NEW packages will be installed:
linux-generic-hwe-20.04 linux-generic-hwe-20.04-edge linux-generic-hwe-22.04
linux-generic-hwe-22.04-edge linux-headers-5.19.0-38-generic
linux-headers-generic-hwe-22.04 linux-headers-generic-hwe-22.04-edge
linux-hwe-5.19-headers-5.19.0-38 linux-image-5.19.0-38-generic
linux-image-generic-hwe-22.04 linux-image-generic-hwe-22.04-edge
linux-modules-5.19.0-38-generic linux-modules-extra-5.19.0-38-generic
0 upgraded, 13 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 124 MB/124 MB of archives.
After this operation, 739 MB of additional disk space will be used.

**Snowhog** · Apr 09, 2023, 11:44 AM

Originally posted by Silent Observer View Post

I don't recall where the alexlarsson-ubuntu-flatpak-jammy.list came from, but probably got upgraded from 20.04 to 22.04 during my failed upgrade attempt and install-over to fix my system, over Christmas break.

The only packages in that PPA for Focal Fossa are/were:

First • Previous • Next • Last

flatpak	1.12.4-1flatpak1~20.04	Simon McVittie (2022-01-20)
flatpak-builder	1.2.2-2flatpak1~20.04	Simon McVittie (2022-01-20)
ostree	2020.8-flatpak1~focal	Alexander Larsson (2020-11-19)
xdg-desktop-portal	1.8.1-1~flatpak1~20.04	Simon McVittie (2022-01-13)
xdg-desktop-portal-gtk	1.8.0-1~flatpak1~20.04	Simon McVittie (2022-01-13)

**claydoh** · Apr 09, 2023, 01:23 PM

Originally posted by Silent Observer View Post

I don't recall where the alexlarsson-ubuntu-flatpak-jammy.list came from, but probably got upgraded from 20.04 to 22.04

Then it is disabled, anyway. The upgrade process does that to PPAs, so it isn't actually being used, which explains a lack of messages (doh!)

Originally posted by Silent Observer View Post

wanting to install an alternative version.

That may be a clue - a virtual package that needs one of a list of items to satisfy.
I admit these are weird and I don't understand well. I barely understand some of the basics.
A virtual package is satisfied with any one of a number of packages that are designated to "Provide" it. One would be installed, not all of them, though.
I think.
Maybe.
I think have a headache now lol!

Originally posted by Silent Observer View Post

If that were the case, would reinstalling linux-generic fix the dependencies and let me at least remove the stuck -nvidia and -oem packages? Or would that have other unwanted effects?

Actually, it might.

But: Hmmmm:

Originally posted by Silent Observer View Post

sudo apt reinstall linux-generic*

<--- I spy an extra bit here

Using the wildcard option ( the * ) in a command will Install all packages with that text in the name.
Try it without the star. Actually, linux-generic-hwe-22.04 is the appropriate kernel metapackage for the 5.19 kernel that most people on 22.04 are running. It shouldn't make things worse.

(the * at the end of some package names WILL be seen in the output when using apt purge. This designates which packages are having system config files removed, etc. In most other places, the star is just a simple regex to "match everything")

**Silent Observer** · Apr 09, 2023, 01:57 PM

Okay, I'll try reinstalling linux-generic-hwe-22.04 (will need a restart, so I'll have to come back and post results). I've run HWE kernel series on 16.04 and 20.04, don't remember why I started doing so, I certainly don't have any cutting-edge hardware (obsolete motherboard, FX8350 CPU, GTx 1070 GPU).

Okay, installed that meta-package(sudo apt install linux-generic-hwe-22.04), nothing was removed (installed 8 packages, all for the 5.19.0-38 HWE stack). Ran sudo update-grub, then used Configure GRUB (from GUI) to check that hadn't added back the non-working kernels. Rebooted into 5.19.0-38 -- and got a lockup on console screen after a short period with Kubuntu logo and "press any key to stop disk checks in progress." No login prompt, even with Alt-F1 (or Ctl-Alt-F1, never can remember which I want and tried both). So I'm back to 5.15.0-67, and attempting to purge 5.15.0-69 still results in apt trying to install the *-unsigned-* version.

**Silent Observer** · Apr 19, 2023, 03:22 PM

Sigh...

Got another routine update today. That installed kernel 5.15.0-70-generic, as one might expect, as well as 5.19.0-40-generic (which I presume is the HWE path).

Neither one will boot. Where can I find the logs that will help nail down what's going on here? Getting one bad upgrade I can understand; that's most of why the updater keeps some old kernel versions -- but getting two in a row that won't boot?

**oshunluvr** · Apr 19, 2023, 03:54 PM

Sounds like you might be missing some needed packages. Are you using a DKMS driver like nVidia?

Run dkms status and if you get nothing then your not using dkms. If you do get output, make sure all the kernels have whatever dkms module is built.

If dkms isn't the issue, look at whats installed to verify all needed extra packages are there. For example, I'm using 5-15.0-69-generic kernel Entering this:

dpkg -l |grep 5.15.0-69 | awk '{print $2}'

Code:

returns this output
linux-headers-5.15.0-69
linux-headers-5.15.0-69-generic
linux-image-5.15.0-69-generic
linux-modules-5.15.0-69-generic
linux-modules-extra-5.15.0-69-generic

Run the above dpkg statement on the working and then on the non-working kernels to see if all the packages were installed.

**Silent Observer** · Apr 19, 2023, 05:24 PM

I had to install

dkms

but once that was done I got no output from it (currently running 5.15.0-67-generic, as it's the latest that will boot to GUI). I do have nVidia driver 515 metapackage, and my display performance seems normal (very similar to what I had in 20.04 a few months ago); also, I have the nVidia X control panel showing, though it's less detailed than it used to be (that may be an nVidia change).

For the one that works (5.15.0-67-generic):

$ dpkg -l | grep 5.15.0-67 | awk '{print $2}'
linux-headers-5.15.0-67
linux-headers-5.15.0-67-generic
linux-image-5.15.0-67-generic
linux-modules-5.15.0-67-generic
linux-modules-extra-5.15.0-67-generic
linux-modules-nvidia-515-5.15.0-67-generic
linux-objects-nvidia-515-5.15.0-67-generic
linux-signatures-nvidia-5.15.0-67-generic

For the newest HWE kernel installed today:

$ dpkg -l | grep 5.19.0-40 | awk '{print $2}'
linux-headers-5.19.0-40-generic
linux-hwe-5.19-headers-5.19.0-40
linux-image-5.19.0-40-generic
linux-modules-5.19.0-40-generic
linux-modules-extra-5.19.0-40-generic

For the newest non-HWE, also installed today, that also won't boot:

$ dpkg -l | grep 5.15.0-70 | awk '{print $2}'
linux-headers-5.15.0-70
linux-headers-5.15.0-70-generic
linux-image-5.15.0-70-generic
linux-libc-dev:amd64
linux-modules-5.15.0-70-generic
linux-modules-extra-5.15.0-70-generic

Apparently, the nVidia blob isn't getting into these newer kernels (why? Dunno). If I change the nVidia version I'm using via Driver Manager, I believe that will install itself in every kernel it finds, correct? I have nVidia 530 listed as (proprietary, tested) in Driver Manager, I could upgrade to that.

**Schwarzer Kater** · Apr 20, 2023, 01:11 AM

Originally posted by Silent Observer View Post

[…]
I have nVidia 530 listed as (proprietary, tested) in Driver Manager, I could upgrade to that.

Do that - best in Konsole with
ubuntu-drivers devices to list the available drivers and
sudo ubuntu-drivers autoinstall OR sudo ubuntu-drivers install nvidia:530 to install it,
so you can see what is happening (e.g. for which kernels the additional Nvidia stuff is installed).

See: https://help.ubuntu.com/community/Nv...rsInstallation

Announcement

Today's kernel update loaded multiple kernel versions, none of which work

Today's kernel update loaded multiple kernel versions, none of which work

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment