Per inspection result from above comment, the behavior is actually a bug in the upstream v4l2loopback source, function v4l2_loopback_write:
/* there's at least one writer, so don'stop announcing output capabilities */ dev->ready_for_output = 0; Which set `dev->ready_for_output` to zero without correcting its `dev->type`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946660 Title: Ubuntu port of v4l2loopback doesn't behave the same as official port (v0.12.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1946660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
