Description of problem: v4l2loopback crashes under kernel ≥ 6.18 (https://github.com/v4l2loopback/v4l2loopback/issues/653). It is a known problem solved by this commit: https://github.com/v4l2loopback/v4l2loopback/commit/6b33fe1f682881eb268ab9fc85f231acc5564ac8 and release 0.15.3 includes this fix. So Mageia’s v4l2loopback should be updated to this version. Version-Release number of selected component (if applicable): 0.15.2-1 How reproducible: always Steps to Reproduce: 1. use kernel ≥ 6.18 (6.18.4 for instance) 2. install dkms-v4l2loopback 3. get kernel oopses
Thank you for the report, especially the research & the fix. Marc looks after this package, so assigning to you.
Status comment: (none) => Fixed in release 0.15.3Assignee: bugsquad => mageia
must have overseen the update. A new version is now building.
Update received, installed, and checked working. Thanks.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
That was fast :)
I guess that because Bug 34962 - Backport kernel 6.18, also Mageia 9 need this update.
Resolution: FIXED => (none)CC: (none) => friFlags: (none) => affects_mga9?Status: RESOLVED => REOPENED
Component: RPM Packages => BackportsWhiteboard: (none) => mga9too
I think it is best that it arrives like a normal update even if it is for backport kernel. Like we already did for: Bug 34961 - Update request: nvidia470 Bug 34963 - Update dkms-vhba ,libmirage & cdemu-daemon for kernel 6.18 backport This will make it easier for our users (and us to guide them)
Component: Backports => RPM Packages
Thank you Marc, I see already! v4l2loopback-0.15.3-1.mga9 in both core_updates_testing, and backports_testing. Packages can be removed from backports_testing Who can test? And we need an advisory.
Flags: affects_mga9? => (none)Blocks: (none) => 34962CC: (none) => j.alberto.vcWhiteboard: mga9too => MGA9TOOAssignee: mageia => qa-bugs
I'll write one this evening
CC: (none) => mageia
Updated v4l2loopback to support newer kernels: Backported kernel 6.18 requires an updated version (mga#34962). Additionally some bugs and issues have been fixed. RPMS in core/updates_testing: v4l2loopback-0.15.3-1.mga9 dkms-v4l2loopback-0.15.3-1.mga9 SRPM: v4l2loopback-0.15.3-1.mga9.src.rpm
CC: j.alberto.vc => (none)
Problem??? Linux mach3.hviaene.thuis 6.18.4-desktop-3.stabletesting.mga9 #1 SMP PREEMPT_DYNAMIC Sun Jan 11 22:07:05 UTC 2026 x86_64 GNU/Linux But when I select the dkms-v4l2loopback, it wants to draw in kernel-desktop-devel-6.6.116.
CC: (none) => herman.viaene
(In reply to Herman Viaene from comment #10) > when I select the dkms-v4l2loopback, it wants to draw in > kernel-desktop-devel-6.6.116. I believe that is a problem in our tools, not this package. See Bug 34973 - Wrong selection of kernel-devel packages, running kernel 6.18
MGA9-64 desktop Plasma Wayland on Compaq H000SB No installation issues. ]$ uname -a Linux mach3.hviaene.thuis 6.18.4-desktop-3.stabletesting.mga9 #1 SMP PREEMPT_DYNAMIC Sun Jan 11 22:07:05 UTC 2026 x86_64 GNU/Linux $ v4l2loopback-ctl list unable to open control device '/dev/v4l2loopback': No such file or directory No complaints seen from kernel From https://wiki.archlinux.org/title/V4l2loopback=: # modprobe v4l2loopback video_nr=9 card_label=Video-Loopback exclusive_caps=1 # v4l2loopback-ctl list OUTPUT CAPTURE NAME /dev/video9 /dev/video9 Video-Loopback Looks good to me
Whiteboard: MGA9TOO => MGA9TOO MGA9-64-OK
Cauldron fixed by Comment 3, changing this to an MGA9 bug. Validating.
CC: (none) => andrewsfarm, sysadmin-bugsWhiteboard: MGA9TOO MGA9-64-OK => MGA9-64-OKVersion: Cauldron => 9Keywords: (none) => validated_update
Keywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2026-0006.html
Resolution: (none) => FIXEDStatus: REOPENED => RESOLVED