ShayBox / Mon2Cam

Workaround for multi-monitor Discord screensharing
MIT License
337 stars 33 forks source link

Error when running #60

Closed SmokingWalrus closed 3 years ago

SmokingWalrus commented 3 years ago

Running on: Arch Linux [KDE Plasma Desktop Enviroment] after facing the issue i installed the linux headers but with no luck


  framerate: 60,
  device: 50,
  resolution: "",
  ffmpeg: [],
  border: false,
  sound: false,
  wayland: false,
  loggerOptions: { verbose: true },
  execOptions: { verbose: true, output: 3 }
}
DEBUG Checking if V4L2 device exists
DEBUG V4L2 device not found with id 50, creating it

Exec Context: b80876d1-dbae-49ac-93ac-e00857ea7fa4
    Exec Options:  { verbose: true, output: 3 }
    Exec Command: sudo modprobe -r v4l2loopback
    Exec Command Splits:  [sudo,modprobe,-r,v4l2loopback]
    Exec Result:  { code: 1, success: false },
 output: "modprobe: FATAL: Module v4l2loopback is in use."
Exec Context: b80876d1-dbae-49ac-93ac-e00857ea7fa4

Exec Context: e0fecbda-d8aa-4e46-b859-2a433734a21b
    Exec Options:  { verbose: true, output: 3 }
    Exec Command: sudo modprobe v4l2loopback video_nr=50 card_label="Mon2Cam"
    Exec Command Splits:  [sudo,modprobe,v4l2loopback,video_nr=50,card_label="Mon2Cam"]
    Exec Result:  { code: 0, success: true },
 output: ""
Exec Context: e0fecbda-d8aa-4e46-b859-2a433734a21b

DEBUG Exiting
DEBUG V4L2 device created with id 50
PANIC Failed to create V4L2 device with id 50```
ShayBox commented 3 years ago

Something else is using v4l2loopback on your system, you'll have to close whatever that is so it can unload and load the kernel module

Probably Droidcam or something similar

PalanixYT commented 3 years ago

have you updated your kernel headers?