Ubuntu
v4l2loopback package

v4l2loopback-dkms 0.4.1-1: v4l2loopback kernel module failed to build

Bug #1431909 reported by Poterie Bruno on 2015-03-13

This bug report is a duplicate of: Bug #1190968: v4l2loopback-dkms fails to build [‘struct v4l2_buffer’ has no member named ‘input’]. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	v4l2loopback (Ubuntu)	New	Undecided	Unassigned

Bug Description

release : Ubuntu 12.04.5 LTS

package : v4l2loopback-dkms:
  Installé : 0.4.1-1
  Candidat : 0.4.1-1
Table de version :
*** 0.4.1-1 0
        500 http://fr.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
        100 /var/lib/dpkg/status

pop-up when launching system

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: v4l2loopback-dkms 0.4.1-1
ProcVersionSignature: Ubuntu 3.13.0-46.79~precise1-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
DKMSKernelVersion: 3.13.0-46-generic
Date: Fri Mar 13 13:53:59 2015
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 0.4.1-1
SourcePackage: v4l2loopback
Title: v4l2loopback-dkms 0.4.1-1: v4l2loopback kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Poterie Bruno (bruno-poterie) wrote on 2015-03-13:

DKMSBuildLog.txt Edit (1.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (829 bytes, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (1.8 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2015-03-13

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2016-05-17:

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 1190968, 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.