linux-generic-hwe-18.04=5.3.0.25.94 in bionic-proposed causes a conflict with virtualbox-guest-x11-hwe

Bug #1856492 reported by m4dm4x1337
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-meta-hwe (Ubuntu)
New
Undecided
Unassigned

Bug Description

How to reproduce this bug?
--------------------------

1.) create a minimal ubuntu with debootstrap

2.) use this sources.list:

deb http://de.archive.ubuntu.com/ubuntu bionic main restricted universe multiverse
deb http://de.archive.ubuntu.com/ubuntu bionic-security main restricted universe multiverse
deb http://de.archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse
deb http://de.archive.ubuntu.com/ubuntu bionic-proposed main restricted universe multiverse
deb http://de.archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
deb http://archive.canonical.com/ubuntu bionic partner

3.) update package lists

apt-get update

4.) install kernel 5.3.0 from bionic-proposed

apt-get install linux-generic-hwe-18.04

5.) install virtualbox

apt-get install virtualbox virtualbox-guest-x11-hwe virtualbox-ext-pack

---------------------------------------

actual result:

linux-generic-hwe-18.04 is being removed due to invalid dependencies

expected result:

linux-generic-hwe-18.04 keeps installed

Revision history for this message
Sultan Alsawaf (kerneltoast) wrote :

The problem is that linux-generic-hwe-18.04 is a signed kernel, and virtualbox-guest-x11-hwe is a dkms package, so they cannot mix because you don't have our signing key to make the dkms virtualbox module fit with our signed kernel. When you try to install virtualbox-guest-x11-hwe and have our signed kernel installed, apt will remove the signed kernel and attempt to install the unsigned version instead. This seems like a sane thing to do, except that it breaks secure boot if you need the kernel to be signed.

Revision history for this message
m4dm4x1337 (m4dm4x1337) wrote :

@Sultan Alsawaf

Thanks for the feedback, but it must be a dependency problem for the following reasons:

1.) If I had a signed kernel, I could see it when I query the list of installed packages with dpkg -l

2.) It worked until mid-December when Kernel 5.0.0 was available (Kernel 5.3.0 was only in bionic-proposed at that time)

--------------------------------------------------------

Kernel 5.0.0:
=============

root@ubuntu:~# dpkg -l | grep linux-image
ii linux-image-5.0.0-31-generic 5.0.0-31.33~18.04.1 i386 Linux kernel image for version 5.0.0 on 32 bit x86 SMP
ii linux-image-generic-hwe-18.04 5.0.0.31.88 i386 Generic Linux kernel image

apt-get install virtualbox virtualbox-guest-x11-hwe virtualbox-ext-pack (no problems)

--------------------------------------------------------

Kernel 5.3.0:
=============

root@ubuntu:~# dpkg --list | grep linux-image
ii linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 i386 Linux kernel image for version 5.3.0 on 32 bit x86 SMP
ii linux-image-generic-hwe-18.04 5.3.0.42.99 i386 Generic Linux kernel image

apt-get install virtualbox virtualbox-guest-x11-hwe virtualbox-ext-pack (kernel gets removed)

--------------------------------------------------------

Someone screwed it up when creating the new packages and nobody is fixing it... as usual...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.