v4l2loopback-dkms 0.9.1-4: v4l2loopback kernel module failed to build

Bug #1761190 reported by roshan
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
v4l2loopback (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

In other modules also the problem seems to be due to an implicit declaration of a function and unknown member access.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: v4l2loopback-dkms 0.9.1-4
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
DKMSKernelVersion: 4.15.0-13-generic
Date: Wed Apr 4 18:46:50 2018
DuplicateSignature: dkms:v4l2loopback-dkms:0.9.1-4:/var/lib/dkms/v4l2loopback/0.9.1/build/v4l2loopback.c:2181:2: error: implicit declaration of function ‘setup_timer’ [-Werror=implicit-function-declaration]
InstallationDate: Installed on 2017-03-12 (388 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
PackageVersion: 0.9.1-4
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt 1.2.26
SourcePackage: v4l2loopback
Title: v4l2loopback-dkms 0.9.1-4: v4l2loopback kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
roshan (roshande) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in v4l2loopback (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1760876, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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.