** Description changed: [SRU Justification : v4l2-relayd] [ Impact ] In the official v4l2loopback: 1. v0.12 or lower: - no client usage v4l2 event support 2. v0.13 or newer: - client usage v4l2 event set to (V4L2_EVENT_PRIVATE_START + 0x08E00000 + 1) In Ubuntu v4l2loopback-dkms: 1. version 0.12.x (Noble/Oracular/Plucky): - client usage v4l2 event set to (V4L2_EVENT_PRIVATE_START + 1) 1. version 0.13.x (Oracular/Plucky): - client usage v4l2 event set to (V4L2_EVENT_PRIVATE_START + 0x08E00000 + 1) - with compatibility patch 2. version 0.15.0-0ubuntu1 (Questing): - client usage v4l2 event set to (V4L2_EVENT_PRIVATE_START + 0x08E00000 + 1) - with compatibility patch v4l2-relayd should switch to the official event id in Questing, Plucky and Oracular. Noble has no compatibility problem. [ Test Plan ] 1. Prepare an Intel MIPI camera platform that already working at the target series, 2. Ensure the v4l2loopback module is of the target series by installing `v4l2loopback-dkms` 3. Install v4l2-relayd from -proposed pocket. 4. `sudo systemctl daemon-reload` 5. `sudo systemctl restart v4l2-relayd` 6. Browse to webpage http://webcamtests.com and see if webcam is still working. [ Where problems could occur ] Starting from v4l2-relayd v0.1.4, additional device access restrictions were added to systemd unit file, and this may introduce unexpected failures if somehow the IPU drivers then assumes further accesses to other devices. For security hardening, that's justified. [ Other Info ] While systemd-dev was separated from systemd itself, also migrate Build- - Deps from systemd to systemd-dev. + Deps from systemd to systemd-dev. While the configure script + automatically detects the availability of systemd pkg-config + definitions, the separation of systemd-dev caused systemd service files + no longer installed if rebuilt again using the same source package on + Noble. While pkg-config is obsoleted in Oracular and above in favor of pkgconf, also updated Build-Deps for that. Nominate for Questing and optionally Plucky, Oracular. ========== original bug report =========== 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. While Ubuntu ships prebuilt v4l2loopback kernel module in linux- modules{,-extra} and generic kernel may become hwe kernel of a previous LTS release, it makes such version bumps tied to series as well. The plan is: 1. to support both event IDs in v4l2loopback/oracular, 2. while v4l2loopback/oracular is compiled into kernels linux/oracular and linux-oem-6.11/noble, v4l2-relayd/noble should be better adopt the same fix to make sure it will continue to be compatible with latter v4l2loopback from linux-modules{,-extra}. 3. all the kernels in jammy remains unaffected, and so is v4l2-relayd. Upstream: https://github.com/umlaeute/v4l2loopback/releases/tag/v0.13.2 Debian Trixie: https://packages.debian.org/trixie/v4l2loopback-dkms
-- 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: [SRU] v4l2loopback: 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
