This bug was fixed in the package ubuntustudio-meta - 0.266.2
---------------
ubuntustudio-meta (0.266.2) jammy; urgency=medium
* Refreshed dependencies
* Removed v4l2loopback-dkms from video-recommends (LP: #1983136)
* Removed v4l2loopback-utils from video-recommends
-- Erich Eickmeyer <eeickme...@ubuntu.com> Sat, 30 Jul 2022 16:58:26
-0700
** Changed in: ubuntustudio-meta (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1983136
Title:
[SRU] v4l2loopback-dkms breaks secure boot installation in seed
Status in ubuntustudio-meta package in Ubuntu:
Fix Released
Status in ubuntustudio-meta source package in Jammy:
Fix Released
Status in ubuntustudio-meta source package in Kinetic:
Fix Released
Bug description:
[Impact]
* For users installing Ubuntu Studio 22.04 LTS on secure boot
machines, this is currently not possible as v4l2loopback-dkms is
currently seeded.
* When v4l2loopback-dkms attempts to compile during installation on a
secure boot machine without user interaction with calamares, it
completely fails and the system installation fails.
* In order to proceed, v4l2loopback-dkms must be removed from the
seed and the ubuntustudio-video meta.
* This was recently discovered while working with the Lubuntu team
and undergoing extensive testing with the new Calamares. While it was
not an issue with Calamares, it did point to the issue with
v4l2loopback and explained some complaints received in the
#ubuntustudio IRC chat.
[Test Plan]
* Download Ubuntu Studio 22.04 ISO image.
* Attempt to install on machine with Secure Boot enabled.
* Installation will fail when v4l2loopback-dkms modules attempt to
compile and install to kernel.
[Where problems could occur]
* Problems can occur when existing users update and end up with
v4l2loopback-dkms marked as autoremovable and run 'sudo apt
autoremove', which will unexpectedly remove this package from their
system. Unfortunately, there's no good way to mitigate this except to
advise to reinstall this package.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1983136/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help : https://help.launchpad.net/ListHelp
