This bug was fixed in the package v4l2loopback - 0.13.2-1ubuntu1
---
v4l2loopback (0.13.2-1ubuntu1) oracular; urgency=medium
* Merge from Debian (LP: #2078947), remaining changes:
- v4l2loopback: backward compatibility for v4l2-relayd
-- You-Sheng Yang Mon, 02 Sep 2024
18:26
Attach debdiff for v4l2loopback/oracular. While this is an upstream
version bump, the source tarball along with other generated files have
been uploaded to https://launchpad.net/~vicamo/+archive/ubuntu/sru as
well.
Need sponsors.
** Patch added: "v4l2loopback_0.13.2-1ubuntu1.oracular.debdiff"
** Changed in: v4l2loopback (Ubuntu Noble)
Status: Triaged => Won't Fix
** Changed in: v4l2loopback (Ubuntu Noble)
Importance: High => Undecided
** Changed in: v4l2loopback (Ubuntu Noble)
Assignee: You-Sheng Yang (vicamo) => (unassigned)
** Changed in: v4l2loopback (Ubuntu Oracula
** Description changed:
The v4l2loopback has released v0.13.0 on March 20, 2024, and the latest
v0.13.2 in May. Debian has v0.13.2 as well.
Starting from v4l2loopback v0.13.0, the client usage event has been
upstreamed as part of the official v4l2loopback owning events, and a
differen
** Description changed:
The v4l2loopback has released v0.13.0 on March 20, 2024, and the latest
v0.13.2 in May. Debian has v0.13.2 as well.
+ Starting from v4l2loopback v0.13.0, the client usage event has been
+ upstreamed as part of the official v4l2loopback owning events, and a
+ differen
