-
Notifications
You must be signed in to change notification settings - Fork 26
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
nitropy nk3 update to 1.3.0-rc.1 updates but ends with "Critical error" #208
Comments
Thanks for the report. The first boot after the update took a bit longer than usual because of a change to the external flash, so the update command timed out while waiting for the booted device. We’ve increased the timeout in recent pynitrokey versions and will increase it even more in the next pynitrokey release to avoid this issue. Your pynitrokey version 0.4.25 is pretty old. Please make sure to use the latest pynitrokey version when installing firmware updates to avoid compatibility problems. Regarding the permission errors, this is common behavior and no cause for concern. pynitroey tries to open all hidraw devices to find Nitrokeys, and some of the devices are not available for a regular user. |
Much obliged, thank you. Yeah, I saw advice to "update pynitrokey to v0.34.0 or newer." I ran |
Hm, that should install v0.34.0. Can you share the output of the following commands?
|
(basically Debian testing)
These commands throw the PEP 668 warning, as Debian now enforces PEP 668. However, running the venv version of pip3, I got this:
on both commands |
Ah, I see. So the reason is that one of our dependencies is unfortunately not available for Python 3.11: Nitrokey/pynitrokey#330 We want to fork that dependency to fix this but this is not implemented yet. I will bring it up again so that we maybe increase the priority for this fix. |
You poor people. You're one of a precious few open source projects that's responsive, courteous and helpful to your users, and you still have to deal with this nonsense. No worries. I hope the experience report was helpful and, at least, deters others from making the same ones. Nevertheless, your dedication and professionalism is appreciated and makes me feel far better about giving you my money :-) |
@bordenc we are trying to fix this nonsense with: Nitrokey/pynitrokey#346 ... this should hopefully enable python 3.11 support |
Can I help at all with the (Windows) testing? I'm happy to mess around with my NK on my own time, but I'm happy to volunteer some testing manpower if I'm directed on what to do. |
@bordenc Thank you for that offer! Can you try to install the suggested patch? Most interesting would be the behavior with Python 3.11, but Windows would also be useful.
Ideally, you could also test Afterwards you can uninstall the patched version with:
|
@robin-nitrokey Works for me under Linux Fedora 37 with:
|
On Debian Bookworm (fully updated):
Using the LPC55 because I'm on the USB-C. Windows attempt will be in another post. |
@bordenc Thanks for testing! Sorry, I forgot to mention that. We also changed the update process so you no longer have to manually download the firmware. You can just run:
|
Some day, I'll find a problem that you aren't already two steps ahead on. Revised command works perfectly on Linux. Windows 10 PowerShell output:
Using Python 3.9 because that's what ships with Visual Studio. I can upgrade to 3.11 if that's specifically what you need. I hope that's useful. |
hey @bordenc , would you like to join our beta-testers? We would be happy to have a Windows user in this group. If you would like to join, please create an account at https://support.nitrokey.com/ and send me a PM there (same nick). |
@daringer signed up under username |
Looks like you have reached to the solution. Closing as fixed. Please reopen otherwise. |
Ran
nitropy nk3 update firmware-nk3xn-lpc55-v1.3.0-rc.1.sb2
and got this output:(Hopefully sanitised) /tmp/user/1000/nitropy.log attached.
A couple observations about the log:
In a minor panic, I re-ran
nitropy nk3 update firmware-nk3xn-lpc55-v1.3.0-rc.1.sb2
and got this output:So it appears, thankfully, that nothing broke. Also ran
nitropy nk3 test
and got 3/3.The text was updated successfully, but these errors were encountered: