On Mon, Dec 26, 2022 at 03:07:29PM +0300, Maksim Rodin wrote: > 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.
Sadly it still doesn't work on my side with just 'chrome' or 'ENABLE_WASM=1 chrome' on the command line. > > /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 agree. The only reason why I did this is because this line is found in /etc/firefox-esr/unveil.main. > 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 ;-) I am grateful for your help. I am beginning to think that this issue may not be related to iridium or chromium because other browsers on my system fail to access the webcam, such as qutebrowser or otter-browser, while firefox always succeeds. There must be a common link between those browsers. Could this come from some package that would be required? But which one?
