New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 737653 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: 2017-10-11
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

device.open() fails with error "NotFoundError: Device unavailable." when device has Serial Number

Reported by sczar...@informationmediary.com, Jun 28 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. enable flag here: "chrome://flags/#enable-experimental-web-platform-features"
2. click the "CONNECT" button.
3. select device and connect.

What is the expected behavior?
The "Device requested" message is displayed and in the "site information" the device selected is listed.

What went wrong?
The error message "NotFoundError: Device unavailable." is displayed.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 10.0
Flash Version: 

The USB device I am using is a custom device with firmware made to be used with WebUSB, I am able to connect the the device and get the Landing Page no problem, the device has vendorId, productId, classCode, subclassCode, protocolCode and Serial Number. 

Everything works as intended if the firmware dose not have a Serial Number, the problem only happens when a Serial Number is added to the firmware.
 
test_case.html
1.7 KB View Download
Labels: -Hotlist-Interop Needs-Feedback
Please follow these steps to collect more debugging information:

1. Open chrome://device-log.
2. Make sure Error, User, Event, Debug and USB are checked.
3. Attach the contents of the log to this bug.

USB User[14:36:14] USB device added: vendor=8697 "", product=4099 "CertiScan(R) Desktop USB RFID Reader", serial="IMCDTR200000", guid=e82d0b1a-2d72-4e1f-b073-9a4691323d9b
USB Event[14:36:14] Failed to open device: Operation not supported or unimplemented on this platform
USB Event[14:36:14] Failed to open device: Access denied (insufficient permissions)
USB Event[14:36:14] Failed to open device: Operation not supported or unimplemented on this platform
USB Event[14:36:14] Failed to open device: Entity not found
USB Event[14:36:14] Failed to open device: Operation not supported or unimplemented on this platform
USB User[14:36:14] USB device added: vendor=4172 "", product=33345 "", serial="", guid=e1bb74d4-890b-4452-b22e-2ed7482e7bd1
USB Event[14:36:14] Failed to get active configuration: Entity not found
USB Event[14:36:14] Failed to get config descriptor: Entity not found
USB User[14:36:14] USB device added: vendor=32902 "", product=7206 "", serial="", guid=4254a041-061f-4377-99cf-c4956540a3d9
USB Event[14:36:14] Failed to get active configuration: Entity not found
USB Event[14:36:14] Failed to get config descriptor: Entity not found
USB User[14:36:14] USB device added: vendor=32902 "", product=7213 "", serial="", guid=cc4e6d45-3c01-4590-97d6-8b13352b54ba
USB Event[14:36:14] Failed to get active configuration: Entity not found
USB Event[14:36:14] Failed to get config descriptor: Entity not found
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 28 2017

Cc: reillyg@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "reillyg@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
as well when I unplug the USB device and plug it back in i get the following added:

USB Debug[14:40:40] Driver for \\?\usb#vid_21f9&pid_1003#imcdtr200000#{dee824ef-729b-4a0e-9c14-b7117d33a817} is WINUSB.
USB Debug[14:40:40] Driver for \\?\usb#vid_21f9&pid_1003#imcdtr200000#{258a1020-4edf-4e8a-a913-a1028af9c265} is WINUSB.
USB User[14:40:40] USB device added: vendor=8697 "", product=4099 "CertiScan(R) Desktop USB RFID Reader", serial="IMCDTR200000", guid=3ae9525f-4d0c-4e29-9cc1-dd016b1800e4
USB Debug[14:40:40] Driver for \\?\usb#vid_21f9&pid_1003#imcdtr200000#{a5dcbf10-6530-11d2-901f-00c04fb951ed} is WINUSB.
USB User[14:40:39] USB device removed: guid=e82d0b1a-2d72-4e1f-b073-9a4691323d9b
Labels: Needs-Triage-M59
Cc: pbomm...@chromium.org hdodda@chromium.org
Labels: TE-NeedsTriageFromMTV
@MTV Team-- Requesting MTV team to look into this , as this issue requires USB connected to triage .

Thanks!
Labels: Needs-Feedback
Please try again with Chrome 62.0.3172.0 or later. I have improved the logging of device.open() failures.

Comment 8 by scheib@chromium.org, Sep 13 2017

NextAction: 2017-10-11
Status: Available (was: Unconfirmed)
The NextAction date has arrived: 2017-10-11
Status: WontFix (was: Available)
No update from the issue reporter. Closing as WontFix unless we get more information.

Sign in to add a comment