bnordgren
commented
3 years ago Aha!
This is how OBS determines whether the v4l2loopback module is loaded:
static bool v4l2loopback_installed()
{
bool loaded = false;
int ret = system("modinfo v4l2loopback >/dev/null 2>&1");
if (ret == 0)
loaded = true;
return loaded;
}This detection method fails inside the flatpak not because the kernel module is missing, but because there's no modinfo command inside the flatpak. Any chance you could coordinate with OBS to determine whether modinfo should be added to the flatpak or whether the test should be changed to something like grep v4l2loopback /proc/modules? (i.e. What implications does the latter solution have for which versions of the linux kernel are supported?)
eszlari
anthr76
GeorgesStavracas
On fedora silverblue 33 (basecommit 56c8ba8529da528d68252247fbfa0c0c4ec2361f442fa4eda3ee9bd5a94e1ff7)
I compiled v4l2loopback in a toolbox and manually
insmoded it. I now have a /dev/video2.Started a shiny new OBS Studio 26.1.0 from flatpak and there's no "start virtual camera" button. As described on #65, I looked at the currrent logs to find:
Entering the running flatpak and listing the contents of /app/lib/obs-plugins shows that both things it's complaining about are symlinks which did not make it to the flatpak packaging... So that's one thing that needs to be addressed...
Moving on, an indication that the loopback device is functional and available inside the flatpak:
I just don't know what criteria OBS is using to decide that v4l2loopback isn't installed. The v4l2 sink plugin is missing from the flatpak, but that appears to be a separate issue, as the log file doesn't emit that error until well after it complains that loopback support is missing.
By the way, you can probably close #65 as moot now, and #91 has a rather hypothetical "probably won't work until the advent of this pending PipeWire technology", which seems a little wrong given that #65 got it to work manually...somehow...