[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer

2020-11-09 Thread Russell Neches
Confirmed that with v4l2loopback-dkms 0.12.3-1ubuntu0.1, configured devices are not correctly advertised. This breaks Zoom, Cheese, etc. Compiling v4l2loopback from upstream source works correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer

2020-11-03 Thread Stefan Bader
Right now, the only app that appears to work with the new module is Chromium. Which was where I was testing because that seemed more demanding. Will be working on the regression on bug 1901491. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer

2020-11-02 Thread emptythevoid
Can confirm, this change prevents Zoom from listing my v4l2lsink from OBS. I had to downgrade to the "base" package so that my co-workers can continue to see my stupid effects and overlays. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer

2020-11-02 Thread Stefan Bader
No, looking quickly at the code that should be set in the capabilities returned by the query capabilities call. But not in the static device_caps. And if that is added back, one cannot drop that flag for exclusive_caps functionality without triggering repeated kernel warnings. -- You received

[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer

2020-11-02 Thread Stefan Bader
Would loading the new module with exclusive_caps=1 work as a quick work- around. I guess I missed adding the caps explicitly in the query function. So that relies on thing being set as device caps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer

2020-11-02 Thread Raphaël
The last fix also broke v4l2loopback for me. Most applications seem to check the V4L2_CAP_VIDEO_CAPTURE flag (eg Firefox: https://hg.mozilla.org/releases/mozilla- release/file/aac9479c6a32ce3b95556da24f3b00c00e145506/media/webrtc/trunk/webrtc/modules/video_capture/linux/device_info_linux.cc#l386),

[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer

2020-10-31 Thread bx
This fix has rendered v4l2loopback obsolete. Indeed, the device is no longer detected by any applications (e.g. VLC, Firefox, etc.). I had to revert to the previous version to be able to use it again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer

2020-10-29 Thread Launchpad Bug Tracker
This bug was fixed in the package v4l2loopback - 0.12.3-1ubuntu0.1 --- v4l2loopback (0.12.3-1ubuntu0.1) focal; urgency=medium * Fix kernel warnings triggered by vidioc_querycap (LP: #1899633). -- Stefan Bader Tue, 13 Oct 2020 15:07:55 +0200 ** Changed in: v4l2loopback (Ubuntu

[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer

2020-10-21 Thread Stefan Bader
$ dpkg -l|grep v4l2loop ii v4l2loopback-dkms 0.12.3-1ubuntu0.1 all Source for the v4l2loopback driver (DKMS) ii v4l2loopback-utils 0.12.3-1ubuntu0.1 all Commandline utilities for

[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer

2020-10-20 Thread Brian Murray
Hello Stefan, or anyone else affected, Accepted v4l2loopback into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/v4l2loopback/0.12.3-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer

2020-10-19 Thread Christian Ehrhardt 
Thanks for the updated debdiff as requested, LGTM now. Some minor cleanup 0.12.3-1ubuntu1 -> 0.12.3-1ubuntu0.1 Further I think we should add DKMS rebuild with the Focal kernel as test-step explicitly (it will be done on install of the upgrade anyway, but to be formally correct) ** Description

[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer

2020-10-19 Thread Christian Ehrhardt 
FYI: I was on the receiving end of a video call using this updated driver - I can confirm it works. Reviewed, made some minor fixups (version as mentioned), extended the SRU template n the description and sponsored into Focal-proposed -- You received this bug notification because you are a

[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer

2020-10-19 Thread Stefan Bader
The kernel check was added in [1] v5.4-rc1 by: Author: Hans Verkuil Date: Tue Jul 23 04:21:25 2019 -0400 media: v4l2-dev/ioctl: require non-zero device_caps, verify sane querycap results Now that all V4L2 drivers set device_caps in struct video_device, we can add a check for

[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer

2020-10-13 Thread Stefan Bader
Test build uploaded to: https://launchpad.net/~smb/+archive/ubuntu/focal/+packages The attached debdiff contains the proposed adjustments to the DKMS package. ** Patch added: "focal-proposed-fix.debdiff"

[Bug 1899633] Re: Repeated kernel warnings/stacktraces with kernel 5.4 and newer

2020-10-13 Thread Stefan Bader
The 20.10 version (0.12.5-1) was reworked considerably and I was told by someone else that it would not exhibit those warnings. ** Changed in: v4l2loopback (Ubuntu) Status: In Progress => Fix Released ** Changed in: v4l2loopback (Ubuntu) Assignee: Stefan Bader (smb) => (unassigned)