I have to admit that I wasn't paying attention during the update, and after the restart of my HP Elite SFF 805 G9 desktop PC I suddenly had no sound at all anymore.
I realized that Kubuntu 26.04 LTS on the HP had started with linux-image-7.0.0-1004-azure.
What the h…?!?
--> addition: this did not happen in a virtual machine or on another computer with Kubuntu 26.04 LTS. Their updates proceeded smootly and and resulted solely in linux-image-7.0.0-22-generic.
Something during today's update had led to the installation of linux-base-sgx, which then possibly must have installed the dependencies linux-image-7.0.0-1004-azure, linux-main-modules-zfs-7.0.0-1004-azure and linux-modules-7.0.0-1004-azure…- or vice versa?
I have had no time to search for the real culprit or dependencies, but
sudo purge linux-base-sgx
and a reboot solved it for now.
PS: And no, I don't have any NVIDIA graphics card and the CPU is AMD - not Intel (so no SGX here)…
--> addition
I still don't know exactly what has led to the installation of sgx/azure, but I have come up with three possible explanations:
Unless any further problems arise, I will mark this thread as "resolved"…
I realized that Kubuntu 26.04 LTS on the HP had started with linux-image-7.0.0-1004-azure.
What the h…?!?
--> addition: this did not happen in a virtual machine or on another computer with Kubuntu 26.04 LTS. Their updates proceeded smootly and and resulted solely in linux-image-7.0.0-22-generic.
Something during today's update had led to the installation of linux-base-sgx, which then possibly must have installed the dependencies linux-image-7.0.0-1004-azure, linux-main-modules-zfs-7.0.0-1004-azure and linux-modules-7.0.0-1004-azure…- or vice versa?
I have had no time to search for the real culprit or dependencies, but
sudo purge linux-base-sgx
and a reboot solved it for now.
PS: And no, I don't have any NVIDIA graphics card and the CPU is AMD - not Intel (so no SGX here)…
--> addition
I still don't know exactly what has led to the installation of sgx/azure, but I have come up with three possible explanations:
- some remnants of the developer release/beta version caused this (as the HP is the only computer/virtual machine on which I have not performed a clean installation following the official release.…)
- an external repository (such as the one for VirtualBox) that is not used in any other of my Kubuntu 26.04 installations caused this
- something hardware-specific of my HP desktop caused this (the most unlikely explanation IMHO).
Unless any further problems arise, I will mark this thread as "resolved"…