modprobe: ERROR: could not insert 'v4l2loopback': Invalid argument

Bug #1936250 reported by Erich Eickmeyer
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
v4l2loopback (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

This looks like it has to do with a recent version of the package.

A recent update to v4l2loopback has caused it to fail with the following error message when modprobe is done:

modprobe: ERROR: could not insert 'v4l2loopback': Invalid argument

This may have to do with an incompatibility with the kernel version and the dkms module. It seems to compile fine, but cannot be inserted.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: v4l2loopback-dkms 0.12.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-lowlatency 5.11.21
Uname: Linux 5.11.0-20-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Jul 14 12:11:36 2021
InstallationDate: Installed on 2021-03-20 (115 days ago)
InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320)
PackageArchitecture: all
SourcePackage: v4l2loopback
UpgradeStatus: Upgraded to impish on 2021-06-13 (31 days ago)

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :
Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Looks like this is fixed upstream. I'll put the commit into a patch and upload. https://github.com/umlaeute/v4l2loopback/issues/439

Changed in v4l2loopback (Ubuntu):
assignee: nobody → Erich Eickmeyer  (eeickmeyer)
assignee: Erich Eickmeyer  (eeickmeyer) → nobody
importance: Undecided → Medium
status: New → In Progress
Changed in v4l2loopback (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package v4l2loopback - 0.12.5-1ubuntu3

---------------
v4l2loopback (0.12.5-1ubuntu3) impish; urgency=medium

  * Don't fail if allocating 0-sized buffers (LP: #1936250)

 -- Erich Eickmeyer <email address hidden> Thu, 29 Jul 2021 17:54:49 +0000

Changed in v4l2loopback (Ubuntu):
status: Fix Committed → Fix Released
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.