Not asked for permission to access camera or mic --> failed to access

[coach1988]

Hello there, first of all thank you so much for all your hard work, we really appreciate it in our company, as jitsi is so easy to use that it got adapted really quick by almost everyone.
After using jitsi primarily via rocketchat, i've started deploying the electron app to allow screen control, as it has been requested many times and i've found out (only by accident, you should really make that a bit more of a obvious thing, it's great) that jitsi can do it, if the the electron version is used.
some users (with webcam, that's a difference between them and working clients) have reported that the program only shows an error that access to the camera and microphone wasn't granted, without being asked for it at all, so no way for them to fix it:

There are no problems when using the browser.
The affected clients are running Windows 10 1909 and version 2.0.2 of the app, windows app privacy settings for camera and microphone have been checked.
The jitsi integration of the rocketchat electron app works though.

Please let me know how/where to gather further information (logs, registry, config edits, etc.) and i will happily try to provide everything as good as i can:)

Thank you very much and keep up this excellent work, you are making a huge difference for admins like me (just take a look at reddit regarding jitsi), especially during these times.

[saghul]

So this only happened to users who did have a webcam?

[coach1988]

@saghul
Yes, as far as i can tell, had some other users without cam testing it without problems.

[saghul]

2.1.0 just got released with a new Electron version, which also updated the builtin Chromium version. Can you please give it a try?

[coach1988]

Already deploying it to the first testers, as i saw the fixes regarding this topic for mac os=)

EDIT: BTW, I'm also telling them to delete the "%appdata%Jitsi Meet" folder before they start the new version, just to be sure.

EDIT2: Not sure how i could have missed that as a linux user, but it seems as if you get some logging when started from the CLI, will deliver asap.

[coach1988]

@saghul OK, personally tested it with the new version on an affected device, same effect. However, I have created a backup of the %appdata% folder afterwards. I didn't see anything in the logs, but maybe there is something else I should look at (cookies, config.json, etc.), I'm just not uploading it as it may contain information about the user, cookies, etc, but if you need something specific, I'll check it/upload it (if it doesn't contain sensitive data).

The cmd output was not really interesting:
11:48:13.063 > Checking for update
11:48:13.586 > Generated new staging user ID: aaafc72f-cb58-5f22-bad5-b6a0d558044d
11:48:16.027 > Update for version 2.1.0 is not available (latest version: 2.1.0, downgrade is disallowed).
11:48:16.032 > checkForUpdatesAndNotify called, downloadPromise is null

[saghul]

Hum. I’ll dust off my windows laptop to give it a try.

[coach1988]

I will play around with our AV system,wouldn't be the first time that creates issues (though I have little hope about that,as the rocketchat app worked without any further configuration changes). I'll keep you updated.

[saghul]

I just tried it on an up to date Windows 10 machine (fresh Jitsi Meet install) and couldn’t reproduce the issue.

[coach1988]

@saghul
OK, I couldn't recreate the issue here with an "emulated" webcam (OBS VirtualCam, https://obsproject.com/forum/resources/obs-virtualcam.949/), but I'll try to get my hands on a real unit that is not a customized admin PC to test it under real conditions. I'll let you know in case I found something.

[coach1988]

@saghul OK, it started working yesterday for one of the affected employees, he unfortunately upgraded to Windows 10 2004 shortly before though, so I can't say if it was the Jitsi update to 2.2.0 or the windows update, but I'll try to get that information from someone else for you, just to get this documented (as it seems to be solved now).

[saghul]

Thanks for sharing! I'm going to tentatively close this then. If the issue reappears, drop a comment and we'll reopen.

[jrie]

I encounter that permissions are not asked for and I cannot set anything from inside the settings as nothing is offered.

In the dropdowns there is only written "Permissions are not granted" ("Berechtigungen nicht erteilt") - and clicking on it does nothing. I would expect that I either can grant the permission or the ability to select the headset I am using.

Once opening jitsi I only encounter the notice "The microphone cannot be accessed due to unknown reasons". Only if I connect a usb camera the "devices" panel in setting updates and I am able to select the camera and the audio output device. Also the headset is detected and labeled correctly and a video of the webcam is shown as preview correctly. But I cannot set a microphone and the "Permissions are not granted" stays for that option.

I am using the latest version 2.2.0 - Debian Sid without a webcam (usually) and a Razer Kraken Ultimate headset connected via USB which has a microphone.

Edit: And the testsound works on the headphones, even there is nothing selected as audio output, even before plugging in the webcam.

[coach1988]

@jrie It sounds a bit different than what i was encountering, as the affected users over here never saw dropdowns to chose from (see screenshot of first post), but it looks like the presence of a webcam has quite an impact on the further logic regarding audio devices.

@saghul Perhaps that could be of interest for you=)