OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
wayland-compat low common DISPUTE

OBS virtual camera missing, or Zoom/Meet/Teams never lists it

omarchyarchendeavouroscachyosmanjarohyprlanddesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Re-checked on this Omarchy 4.0.2-1 workstation (obs-studio 32.2.2-1, kernel 7.1.9-arch1-2, linux-headers 7.1.9.arch1-2, dkms 3.4.3-2, v4l-utils 1.32.0-2) and against upstream. The core claim holds and OBS 32 has NOT replaced v4l2loopback: strings /usr/lib/obs-plugins/linux-v4l2.so still carries modinfo v4l2loopback, v4l2loopback not installed, virtual camera not registered and the literal autoload line pkexec modprobe v4l2loopback exclusive_caps=1 card_label='OBS Virtual Camera' && sleep 0.5, while linux-pipewire.so is an input path only (pipewire-camera-source, org.freedesktop.portal.Camera), so the PipeWire work in OBS is capture, not virtual camera output. Arch still lists v4l2loopback-dkms: virtual camera support as an obs-studio optdepend (package JSON fetched today). exclusive_caps=1 is still required: upstream v4l2loopback.c line 166 defines V4L2LOOPBACK_DEFAULT_EXCLUSIVECAPS 0, so the default has not flipped, and the ArchWiki V4l2loopback page fetched today gives the same modprobe line and the same try-it-both-ways tip the record ends on. Four corrections. First, the fix used sudo pacman -S with no Omarchy branch. I confirmed by reading /usr/share/omarchy/bin/omarchy-update-pacman-guard that the guard fires only when both a sync flag and a sysupgrade flag are present, so a plain install is not blocked, and added the native omarchy pkg add form, which /usr/share/omarchy/bin/omarchy-pkg-add implements as pacman -S --noconfirm --needed. Second, the record hardcodes /dev/video9 in step 5 and in verify, but OBS's own autoload passes no video_nr, so a reader who lets OBS load the module gets a different node and concludes the fix failed. Third, v4l2loopback-utils 0.15.4-2 exists in extra and provides v4l2loopback-ctl for dynamic add and delete, which the record never mentions. Fourth, the danger said the DKMS build "fails silently during the pacman transaction", which is right in effect but not in mechanism, so I named the actual hooks and the Omarchy specific reason it is easy to miss. The cited Arch package URL used the x86_64 path, but the package is any on both v4l2loopback-dkms and v4l2loopback-utils, so the old URL only 301 redirects while https://archlinux.org/packages/extra/any/v4l2loopback-dkms/ returns 200. Replaced it. Kept symptom, severity low and frequency common. NOT exercised: v4l2loopback-dkms is not installed here and there is no /dev/video* on this machine, so no module was built, loaded or probed, and no camera enumeration was tested in any browser or conferencing client. Installing and loading a kernel module is outside what an audit may do on the operator's workstation.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

v4l2loopback is DKMS built, so it has to be recompiled for every new kernel. The rebuild is driven by the pacman hooks 70-dkms-upgrade.hook and 70-dkms-install.hook, which call /usr/share/libalpm/scripts/dkms. That script prints a warning line and returns, it does not abort the transaction, so a failed build does not fail the upgrade. On Omarchy the risk is worse than on plain Arch because omarchy update funnels the whole pacman run through an update transcript, so one warning line is easy to miss, and the only visible symptom afterwards is that OBS's Start Virtual Camera button has quietly disappeared. If linux-headers is not upgraded alongside linux, the build has nothing to compile against. After any kernel upgrade run sudo dkms status and, if needed, sudo dkms autoinstall then reboot. Do not modprobe -r while OBS or a call is holding the device: the removal will fail or wedge the app.

Symptom

OBS has no "Start Virtual Camera" button, or it starts without error but Zoom, Google Meet, Teams and Discord never show "OBS Virtual Camera" in the camera dropdown, only my real webcam. ls /dev/video* shows only the webcam devices.

Cause

OBS's virtual camera on Linux writes into a v4l2loopback device, which is an out-of-tree kernel module that must be built and loaded. Without it there is no device node and OBS hides the button. When the module is loaded without exclusive_caps=1 the device advertises both OUTPUT and CAPTURE capabilities at once. Chromium-based clients (Meet, Teams, Zoom, Discord, Slack) refuse to enumerate such a device, so it exists but is invisible to exactly the apps you want it in.

Fix

  1. Install the module sources and the headers for the kernel you are actually running:

uname -r
pacman -Q linux linux-headers      # these two versions must match

On Omarchy 4 use the wrapper, which is pacman -S --noconfirm --needed underneath:


omarchy pkg add v4l2loopback-dkms linux-headers v4l2loopback-utils

On plain Arch:


sudo pacman -S --needed v4l2loopback-dkms linux-headers v4l2loopback-utils

Use linux-lts-headers, linux-zen-headers or linux-cachyos-headers instead if you run that kernel. This is an install, not a system upgrade, so Omarchy's ALPM guard does not block it: /usr/share/omarchy/bin/omarchy-update-pacman-guard aborts only when the pacman command line carries both a sync flag and a sysupgrade flag. v4l2loopback-utils is optional and gives you v4l2loopback-ctl.

  1. Load it with the options that make it usable:

sudo modprobe -r v4l2loopback
sudo modprobe v4l2loopback video_nr=9 card_label="OBS Virtual Camera" exclusive_caps=1
v4l2-ctl --list-devices

exclusive_caps=1 is still needed on v4l2loopback 0.15.4. Upstream's default is 0 (V4L2LOOPBACK_DEFAULT_EXCLUSIVECAPS in v4l2loopback.c), so a device loaded with no options advertises OUTPUT and CAPTURE together and the Chromium based clients will not list it.

  1. Make it survive a reboot:

echo v4l2loopback | sudo tee /etc/modules-load.d/v4l2loopback.conf
printf 'options v4l2loopback video_nr=9 card_label="OBS Virtual Camera" exclusive_caps=1\n' \
  | sudo tee /etc/modprobe.d/v4l2loopback.conf

Do this before relying on the device number. OBS can load the module itself, but its own command passes no video_nr. In obs-studio 32.2.2 the string compiled into /usr/lib/obs-plugins/linux-v4l2.so is:


pkexec modprobe v4l2loopback exclusive_caps=1 card_label='OBS Virtual Camera' && sleep 0.5

So if OBS loads it, the device lands on the first free number rather than on /dev/video9.

  1. In OBS: **Start Virtual Camera** (bottom right). The same plugin gates the button on modinfo v4l2loopback succeeding and logs v4l2loopback not installed, virtual camera not registered when it does not, which is why a failed DKMS build makes the button vanish rather than error.
  1. Test the device before blaming the conferencing app. It only advertises CAPTURE once something is feeding it:

ffplay /dev/video9

Browser check: open <https://webcamtests.com/> and pick the OBS device.

If the app still does not list it, flip exclusive_caps. The ArchWiki says to try it both ways:


sudo modprobe -r v4l2loopback
sudo modprobe v4l2loopback video_nr=9 card_label="OBS Virtual Camera"

You can also add and delete devices without reloading the module using v4l2loopback-ctl add and v4l2loopback-ctl delete from v4l2loopback-utils, but note upstream's warning that module options may be ignored for a dynamically added device and must be given explicitly.

Verify

v4l2-ctl --list-devices (from v4l-utils) lists "OBS Virtual Camera". It is at /dev/video9 only if you loaded the module yourself with video_nr=9 or wrote /etc/modprobe.d/v4l2loopback.conf, because OBS's own autoload passes no video_nr and takes the first free number. With OBS's virtual camera running, ffplay /dev/videoN shows the OBS program feed and the device appears in the browser's camera picker. Check the module actually built for the running kernel with:


uname -r
dkms status
modinfo v4l2loopback | head -3

Sources

obs-virtual-camera-not-listed-v4l2loopback