-
Notifications
You must be signed in to change notification settings - Fork 84
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
Panic at expect "udev strings should always be utf8" #166
Comments
RUST_BACKTRACE=full with debug instead of release build could be useful. |
Also if you can, maybe include some debug printed output of the value that fails to convert / some info about the specific hid device, which makes it fail. |
I found the culprit! It wasn't a physical device, it was a virtual UHID device. I turned of the service that was adding it and probe-rs works now. As for the value that fails to convert, it appears to just be random bytes that change every time I restart the UHID service. One Here's the full backtrace in case you need it: Backtrace
Thanks for taking the time. Have a nice weekend! |
Can you provide me with the details on the uhid service? If possible I‘d like to try reproduce the issue myself and see if it’s a bug in our code. Random bytes could be a read from uninit memory. |
Sure, it's this one: https://github.com/tillitis/tkey-fido Should be enough to build and run it. |
Can confirm. The same happens with tpm-fido (https://github.com/psanford/tpm-fido) |
Hello! I'm not completely sure, but seems I have some strange device plugged in that breaks the assumption that udev strings must be utf8. I'm using probe-rs, which becomes unusable because of this.
Here's the backtrace:
Can provide more details if needed :)
The text was updated successfully, but these errors were encountered: