Still having this issue, just doing an apt dist-upgrade or pkcon update
gives the same result as it has for weeks. I just revert back to my backup and wait for this to be resolved. Has anyone else had this issue?
Using kernel 6.8.0-35240528-generic
I have plucky installed on a different m2 drive - same machine, not affected by this.
This is not an Ubuntu tool …
This is not an Ubuntu kernel…
You seem to not be using Ubuntu at all, you should consider asking at a help forum of the distro you actually use…
@ogra _ I have no idea what you are on about, both the kernel and pkcon are all part of the Kubuntu world. Pkcon is now apparently the recommended replacement for apt on distribution updates.
Are you saying that Kubuntu is not a flavour of Ubuntu? That seems to be what you are saying.
Tony
O RLY.
$ pkcon update
Getting updates [=========================]
Finished [=========================]
Loading cache [=========================]
Testing changes [=========================]
Finished [ ] (0%)
The following packages have to be updated:
code-1.97.2-1739406807.amd64 Code editing. Redefined.
microsoft-edge-stable-133.0.3065.69-1.amd64 The web browser from Microsoft
quickemu-4.9.7-1~noble24365.1229.all Quickemu creates and runs optimised virtual machines.
unityhub-3.11.1.amd64 The Official Unity Hub
Proceed with changes? [N/y] y
$ apt-cache policy $(dpkg -S $(which pkcon) | awk -F ':' '{print $1}')
packagekit-tools:
Installed: 1.2.8-2build3
Candidate: 1.2.8-2build3
Version table:
*** 1.2.8-2build3 500
500 http://gb.archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
Well, the kernel is definitely not an Ubuntu kernel, no idea where you got it from but Ubuntu kernels use a completely different naming scheme…
To my knowledge apt and Update-Manager are the packaging management tools even on kubuntu (not being a KDE user I might be wrong with this, but in 21y of working on Ubuntu I can guarantee you that your kernel is definitely not from Ubuntu in any way)
Back on topic. When the kernel panics, is there a log?
e.g. if you run jouralctl --list-boots and find a recent one (where it went awry) is there anything useful from journalctl --boot=-1 | (head -n 500; tail -n 500) | pastebinit?
Oh ! Heh, okay, I admit I never used pkcon, mea culpa
(This still leaves the question open what kind of kernel that is )
(neither did I before about 3 minutes ago)
On kubuntu You should have the kernel: linux-image-6.11.0-17-generic 6.11.0-17.17~24.04.2
OK perhaps your knowledge is superior to mine in Ubuntu world, although I have been a Linux user since 1997. I have been using Ubuntu flavours since about 2008.
The weird thing is, I also have wondered about the naming of this kernel, perhaps it’s something unique to Kubuntu, I just know it works really smoothly on my machine. I haven’t got any weird hardware other than lots of m2 devices and add-on cards to hold them and a Hauppauge 4-tuner pcie card.
This is the clue as to where your kernel came from. You probably used GitHub - b-rad-NDi/Ubuntu-media-tree-kernel-builder: Slip stream the latest LinuxTV.org media drivers into an installable Ubuntu kernel package which may well have built you a special snowflake kernel.
I found this via judicious searching online and stumbling on this issue on their project.
So, yes, you have a custom kernel, which means you should probably seek support by
a) switching to a default kernel, and
b) come back if it still happens.
Here is a screenshot of my root file system with the /boot directory in the left pane showing all kernels.
The kernel used from Kubuntu 24.04 is listed here: https://cdimages.ubuntu.com/kubuntu/releases/24.04.2/release/kubuntu-24.04.2-desktop-amd64.manifest
Well, if you can find the correct package name for that kernel the apt policy <package name> command should tell you what apt thinks where it comes from
@popey I think you probably nailed it, there was a Hauppauge instruction to add a different media-tree to the system to get the tuner card to work.
I think that the newer kernels used in plucky penguin have incorporated the required bits of the media tree as I only had to add the new firmware into /lib/firmware and it just worked out of the box.
Thanks Alan.
