usbdevice.open fails with "Access Denied" |
|||||
Issue description
Chrome Version: 57.0.2987.146
OS Version: 9202.64.0
Running:
let device = await navigator.usb.requestDevice({filters: []});
await device.open();
Results in:
=> Uncaught (in promise) DOMException: Access denied.
chrome://device-log contains the following for each 'open()' attempt:
Permission broker failed to open the device: org.freedesktop.DBus.Error.Failed: permission_broker/permission_denied:Permission to open '/dev/bus/usb/001/065' denied
and when the device is plugged in:
USB device added: path=/dev/bus/usb/001/065 vendor=5824 "Teensyduino", product=1159 "Serial/Keyboard/Mouse/Joystick", serial="562820", guid=308614ac-2f41-4bf2-a4c1-5a66a33b3ffe
,
May 12 2017
In that case should the device be hidden from the device picker dialog? side q: Are there plans to make such devices available as they are in the chrome.hid API?
,
May 12 2017
We have a choice between two confusing behaviors: * Acknowledge that the device has been connected but raise an error when the page tries to open the device. * Do not acknowledge that the device has been connected at all. I think the latter is more confusing as it makes the user believe the Chrome (or their computer) is not working at all while the former at least provides an error that points towards the cause of the problem. (Adding Linux because missing udev rules cause the same failure.)
,
May 12 2017
side a: There are no plans to do this as part of the WebUSB API. The replacement for chrome.hid would be a WebHID API.
,
Jul 17 2017
,
Apr 23 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by reillyg@chromium.org
, May 11 2017