Issue metadata
Sign in to add a comment
|
Camera is being blocked even after giving permission to use it |
||||||||||||||||||||||||
Issue descriptionI allow the camera, but it keeps getting blocked. Happens with both the packaged version 55.0.2883.75, and a build from git 27477347836bad10c. Running on Debian testing (Sid). I'm pretty sure it worked a couple weeks ago. I tried completely wiping the user profile too (~/.config/chromium). Steps to reproduce: 1. Open https://webrtc.github.io/samples/src/content/devices/input-output/ 2. It will ask for camera permission - click on Allow. 3. Look at the right side of the location bar - it's showing the camera as blocked. Click on the icon and select "Always allow ..." and Done. Click on icon again - now it shows the camera is allowed, but tells you to reload. 4. Try reloading page - the camera is blocked again. If I look into the permission exceptions for the camera in the media settings, then https://webrtc.github.io:443 is shown as allowed. I am able to use the camera when I run "chromium --use-fake-ui-for-media-stream index.html", where index.html contains something similar to the webrtc demo (also using the MediaDevice API).
,
Feb 27 2017
,
Feb 27 2017
I think the issue may be related to your system not having any microphone and the getUserMedia call requesting both audio and video. Can you try a getUserMedia call with only video, or adding a microphone, just to make sure this is the problem?
,
Feb 27 2017
Hm, I actually do have a microphone, I wonder why Chromium isn't detecting it...
Anyway, I don't think the lack of audio input is the problem, because this is in the source code:
var audioSource = audioInputSelect.value;
var videoSource = videoSelect.value;
var constraints = {
audio: {deviceId: audioSource ? {exact: audioSource} : undefined},
video: {deviceId: videoSource ? {exact: videoSource} : undefined}
};
navigator.mediaDevices.getUserMedia(constraints).
then(gotStream).then(gotDevices).catch(handleError);
The 'audio' field in the constraints should be undefined, if I'm reading it right.
,
Feb 27 2017
,
Feb 28 2017
,
May 20 2017
Sorry for the late reply. I wasn't monitoring this bug since it still has the Needs-Feedback label. In your example, you have an audio entry with an undefined deviceId. You should have audio:false or no audio entry at all. Otherwise you see get problem. The actual bug is probably with the UI. Merging this bug to a bug related to problems with the permissions UI.
,
May 20 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by yini...@chromium.org
, Feb 23 2017