What if you just run chromium without all this and try webcammictest?
>ENABLE_WASM=1 chrome --incognito --user-data-dir=/tmp/chrome

> /dev/video0 rw
> added in both /etc/chromium/unveil.main and
> /etc/chromium/unveil.utility_video

At least webcammictest works for me without any magic or config editing.

> /dev/video0 rw
> added in both /etc/chromium/unveil.main and
> /etc/chromium/unveil.utility_video
I think you do not need it in /etc/chromium/unveil.main and
/etc/chromium/unveil.utility_video: there is already "/dev/video rw" in there 
and that should be enough
because /dev/video is a soft link to /dev/video0

I found the following in my shell history when I last tried (with success!) to
run jitsi test call:
AUDIOPLAYDEVICE=snd/0 AUDIORECDEVICE=snd/1 ENABLE_WASM=yes chrome
I repeated this command right now and could successfully connect to
jitsi test meeting. It showed my ugly face from my webcam and told me that my 
mic seems
to work fine ;-)


On Mon Dec 26 11:49:24 2022, Robert Alessi wrote:
> On Mon, Dec 26, 2022 at 12:03:46PM +0300, Maksim Rodin wrote:
> > Could you once again test your webcam on https://webcammictest.com/ ?
> > I use Chromium for Microsoft Teams video and audio calls.
> > IIRC, the only thing I had to do, was `doas chown myuser /dev/video0`
> > Are you sure that after setting up /etc/fbtab you (and not root) are the 
> > owner of your /dev/video0 device?
> 
> I just did once again like so:
> 
> ENABLE_WASM=1 chrome --incognito --user-data-dir=/tmp/chrome
> 
> with of course:
> 
> /dev/video0 rw
> 
> added in both /etc/chromium/unveil.main and
> /etc/chromium/unveil.utility_video
> 
> and ls -lh /dev/video* gives me this:
> 
> lrwxr-xr-x  1 root    wheel          6 Nov 20 17:24 /dev/video -> video0
> crw-------  1 robert  robert   44,   0 Nov 20 17:24 /dev/video0
> crw-------  1 root    wheel    44,   1 Nov 20 17:24 /dev/video1
> 
> where robert is my username.
> 
> Nevertheless, access to the camera is still denied and the console
> returns the same message over and over:
> 
> uvideo0: could not SET probe request: STALLED
> 
> Needless to mention that firefox-esr works.
> 
> I must say that the fact it works on your side gives me hope, thank
> you!  I must keep looking into this.
> 
> большое спасибо,
> 
> -- R.
> 

-- 
С уважением,
Родин Максим

Reply via email to