-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accessing USB device from an App make chromium to crash #101
Comments
For the records, I've tried to build the FreeBSD port with the DEBUG flag to try to get a stacktrace, but it fails to compile with the following error:
|
Support for USB U2F devices was added in r455495. |
It doesn't crash anymore, but also it doesn't seem to recognize any plugged-in device, even after changing the /dev/uhid* and /dev/usb/* permissions. |
Do you have Please see PR196754 for further details. |
As far as I can see that port simply installs a set of devd rules to change the device permissions, the same thing I did. The chromium patches are expected to add support for any HID device or just for U2F ones? |
The chromium patches add support for both types of devices. It should work (not tested), but you have to add the UDEV rules. https://github.com/trezor/trezor-common/blob/master/udev/51-trezor.rules |
The UDEV rules are just the Linux equivalent of the FreeBSD devd rules to change permissions. |
Yes of course, we use devd rules. Your best bet is to ask @gonzoua. In fact, he added support for USB U2F devices. |
I'm trying to use Chrome extensions that interact with USB devices, like Trezor or Ledger wallets, but chrome crashes as soon as they try to connect.
You can easily reproduce the issue by simply installing the extension at https://wallet.trezor.io (no need to have any device)
The text was updated successfully, but these errors were encountered: