** 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
+ different event ID from the one has been used by v4l2-relayd is chosen
+ to avoid interference of users for other purposes. This, however,
+ introduced backward compatibility issue for v4l2-relayd, which should
+ receive similar fix (also with compatibility to different v4l2loopback
+ versions) as possible.
+
Upstream: https://github.com/umlaeute/v4l2loopback/releases/tag/v0.13.2
Debian Trixie: https://packages.debian.org/trixie/v4l2loopback-dkms
** Also affects: v4l2loopback (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: v4l2-relayd (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: v4l2loopback (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: v4l2-relayd (Ubuntu Oracular)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078947
Title:
Import new upstream 0.13.2 release
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/v4l2-relayd/+bug/2078947/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
