virtual camera not starting

digijay

New Member
First of all I'd like to mention how much I appreciate that OBS has such a strong developer and user community. Thanks a lot to all the people contributing to this project. I've been using OBS for about two years now, mostly for streaming on youtube, which always worked well. Unfortunately, now I'm facing some problems:
  • I just tried for the first time to start a recording, but that made OBS crash at once, resulting in these log entries:
    Code:
    Sep 21 23:16:24 denkbrett kernel: [  911.430085] show_signal_msg: 2 callbacks suppressed
    Sep 21 23:16:24 denkbrett kernel: [  911.430088] obs[50872]: segfault at 100000019 ip 0000000100000019 sp 00007fffe681c6f8 error 14 in obs[55ab76a51000+61000]
    Sep 21 23:16:24 denkbrett kernel: [  911.430102] Code: Unable to access opcode bytes at RIP 0xffffffef.
    Sep 21 23:16:25 denkbrett kernel: [ 912.768706] uvcvideo 2-2:1.1: Failed to resubmit video URB (-1).
  • I found many suggestions to solve the problem and changed the "type" in settings -> output -> recording to "Custom Output Ffmpeg" instead of "Standard" (there are no other options available)
  • That seemed to do the trick, recording worked now. But the virtual camera (which worked perfectly just before I made the change) didn't start anymore.
  • I changed the setting back, but the virtual cam still does not work, I only get these log entries:
    Code:
    23:48:39.756: Settings changed (outputs)
    23:48:39.756: ------------------------------------------------
    23:48:44.064: Failed to start virtual camera
    23:48:44.920: Failed to start virtual camera
    23:48:45.088: Failed to start virtual camera
    23:49:22.675: Settings changed (outputs)
    23:49:22.675: ------------------------------------------------
    23:49:26.579: Failed to start virtual camera
    Recording neither works anymore.
  • I tried to run (although I think that this is not needed anymore)
    Code:
    modprobe v4l2loopback
    but to no avail.
I'm on OBS 27.2.4 (64 bit) on a freshly dist-upgraded Ubuntu 22.04.1 LTS (jammy). Does anybody have an idea what could go wrong here?
 
Top