v4l2loopback-dkms fails to build with linux 5.19 on jammy

Bug #1999670 reported by Andrea Righi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
v4l2loopback (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned

Bug Description

[Impact]

v4l2loopback-dkms fails to build with linux 5.19 on jammy.

[Test case]

 $ sudo apt install v4l2loopback-dkms

[Fix]

Backport v4l2loopback-dkms 0.12.7 from kinetic that works both with 5.19 and 5.15 kernels.

[Regression potential]

Many custom patches that used to be present in Ubuntu builds of 0.12.5 were merged upstream, in adapted form, hence got dropped in 0.12.7. There are slight behavior differences in the upstream version versus previously patched code.

Revision history for this message
Andrea Righi (arighi) wrote :

Debdiff in attach (that doesn't have very much, it's just a rebuild of the kinetic dkms) seems to build fine both with 5.15 and 5.19 kernels.

tags: added: patch
Revision history for this message
Andrea Righi (arighi) wrote :

New debdiff with the correct release name (focal -> jammy).

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

The debdiff uses incorrect version numbers.

The new version number in jammy must not be higher than those that already exist in kinetic and lunar. Instead it should use something like ~22.04 or some such.

description: updated
Changed in v4l2loopback (Ubuntu):
status: New → Fix Released
Changed in v4l2loopback (Ubuntu Jammy):
status: New → In Progress
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

Hello Andrea, or anyone else affected,

Accepted v4l2loopback into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/v4l2loopback/0.12.7-2ubuntu2~22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in v4l2loopback (Ubuntu Jammy):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-jammy
Revision history for this message
Simon Gerber (gesimu) wrote :

I found this issue after trying to install v4l2loopback-dkms on Jammy a few minutes ago. The proposed package has fixed the DKMS build issue for me.

Revision history for this message
Kleber Sacilotto de Souza (kleber-souza) wrote :

Thank you @gesimu for your feedback.

I can also confirm that it can be built for both generic 5.15 and hwe 5.19 kernels:

=========================================================
Setting up v4l2loopback-dkms (0.12.7-2ubuntu2~22.04.1) ...
Loading new v4l2loopback-0.12.7 DKMS files...
Building for 5.15.0-60-generic 5.19.0-32-generic
Building initial module for 5.15.0-60-generic
EFI variables are not supported on this system
/sys/firmware/efi/efivars not found, aborting.
Done.

v4l2loopback.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/5.15.0-60-generic/updates/dkms/

depmod....
Building initial module for 5.19.0-32-generic
EFI variables are not supported on this system
/sys/firmware/efi/efivars not found, aborting.
Done.

v4l2loopback.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/5.19.0-32-generic/updates/dkms/

depmod....
=========================================================

tags: added: verification-done-jammy
removed: verification-needed-jammy
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package v4l2loopback - 0.12.7-2ubuntu2~22.04.1

---------------
v4l2loopback (0.12.7-2ubuntu2~22.04.1) jammy; urgency=medium

  * Backport dkms support for HWE kernels. LP: #1999670

v4l2loopback (0.12.7-2ubuntu2) kinetic; urgency=medium

  * Preserve CC setting when invoking sub-make, to ensure module can be
    built correctly with the kernel's custom compiler. Fixes FTBFS in
    hwe-5.19 build. LP: #1991664

v4l2loopback (0.12.7-2ubuntu1) kinetic; urgency=medium

  * Merge from Debian, remaining changes:
    - drop module-assistant autopkgtest
    - add Ubuntu patch track active-readers
    - add Ubuntu patch implement support for V4L2_EVENT_PRI_CLIENT_USAGE

v4l2loopback (0.12.7-2) unstable; urgency=medium

  * Fix DKMS build on linux>=5.18

v4l2loopback (0.12.7-1) unstable; urgency=medium

  * New upstream version 0.12.7

  [ Andreas Beckmann ]
  * Switch to dh-sequence-dkms.
  * Switch to Testsuite: autopkgtest-pkg-dkms.

  [ Debian Janitor ]
  * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
    Repository-Browse.
  * Remove constraints unnecessary since buster

  [ IOhannes m zmölnig ]
  * Drop patches applied upstream
  * Drop unnecessary B-Ds
  * Bump dh-compat to 13
  * Bump standards version to 4.6.1

v4l2loopback (0.12.5-1ubuntu7) kinetic; urgency=medium

  * Drop obsolte REMAKE_INITRD option from dkms.conf.
  * Update module init & exit calls to use kernel provided macros, such
    that they gain correct IBT attributes. LP: #1980484

v4l2loopback (0.12.5-1ubuntu6) kinetic; urgency=low

  * Check CONFIG_VIDEO_DEV against kernel version >= 5.18. (LP: #1970983)

 -- Dimitri John Ledkov <email address hidden> Mon, 16 Jan 2023 11:22:08 +0000

Changed in v4l2loopback (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for v4l2loopback has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

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.