FS#76325 - [yubioath-desktop] breaks after yubikey-manager 5.0 update
Attached to Project:
Community Packages
Opened by LEVAI Daniel (daniell) - Friday, 28 October 2022, 08:55 GMT
Last edited by Toolybird (Toolybird) - Friday, 04 November 2022, 20:25 GMT
Opened by LEVAI Daniel (daniell) - Friday, 28 October 2022, 08:55 GMT
Last edited by Toolybird (Toolybird) - Friday, 04 November 2022, 20:25 GMT
|
Details
Description:
After yubikey-manager update 4.0.9-1 -> 5.0.0-1 yubioath-desktop breaks: $ yubioath-desktop Got library name: "/usr/lib/qt/qml/io/thp/pyotherside/libpyothersideplugin.so" qrc:/qml/main.qml:361:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 66. Use 'sequences: [ <key> ]' to bind to all of them. qrc:/qml/main.qml:353:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 4. Use 'sequences: [ <key> ]' to bind to all of them. qrc:/qml/main.qml:297:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 9. Use 'sequences: [ <key> ]' to bind to all of them. Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. "PyOtherSide error: Traceback (most recent call last):\n\n File \"qrc:///py/yubikey.py\", line 23, in <module>\n from ykman.device import scan_devices, list_all_devices, connect_to_device, get_name, read_info\n\nImportError: cannot import name 'connect_to_device' from 'ykman.device' (/usr/lib/python3.10/site-packages/ykman/device.py)\n" Unhandled PyOtherSide error: Cannot import module: yubikey (Traceback (most recent call last): File "qrc:///py/yubikey.py", line 23, in <module> from ykman.device import scan_devices, list_all_devices, connect_to_device, get_name, read_info ImportError: cannot import name 'connect_to_device' from 'ykman.device' (/usr/lib/python3.10/site-packages/ykman/device.py) ) "PyOtherSide error: Traceback (most recent call last):\n\n File \"<string>\", line 1, in <module>\n\nNameError: name 'yubikey' is not defined\n" Unhandled PyOtherSide error: Function not found: 'yubikey.init' (Traceback (most recent call last): File "<string>", line 1, in <module> NameError: name 'yubikey' is not defined ) "PyOtherSide error: Traceback (most recent call last):\n\n File \"<string>\", line 1, in <module>\n\nNameError: name 'yubikey' is not defined\n" Unhandled PyOtherSide error: Function not found: 'yubikey.controller.check_descriptors' (Traceback (most recent call last): File "<string>", line 1, in <module> NameError: name 'yubikey' is not defined ) "PyOtherSide error: Traceback (most recent call last):\n\n File \"<string>\", line 1, in <module>\n\nNameError: name 'yubikey' is not defined\n" Unhandled PyOtherSide error: Function not found: 'yubikey.controller.is_win_non_admin' (Traceback (most recent call last): File "<string>", line 1, in <module> NameError: name 'yubikey' is not defined ) qml: TypeError: Cannot read property 'success' of undefined undefined qml: TypeError: Cannot read property 'winNonAdmin' of undefined undefined I haven't spent much time digging into it but seems the python modules/sdk may have changed. Additional info: * package version(s) yubikey-manager 5.0.0-1 yubioath-desktop 5.1.0-3 * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: Just start yubioath-desktop with updated yubikey-manager. |
This task depends upon
Closed by Toolybird (Toolybird)
Friday, 04 November 2022, 20:25 GMT
Reason for closing: Fixed
Additional comments about closing: yubikey-manager 1:4.0.9-1
Friday, 04 November 2022, 20:25 GMT
Reason for closing: Fixed
Additional comments about closing: yubikey-manager 1:4.0.9-1
yubikey-manager update to 5.x also broke yubikey-manager-qt:
FS#76323#> sudo pacman -U /var/cache/pacman/pkg/yubikey-manager-4.0.8-1-any.pkg.tar.zst
if you don't have it in cache, get latest yubikey-manager-4 from here: https://archive.archlinux.org/packages/y/yubikey-manager/yubikey-manager-4.0.9-1-any.pkg.tar.zst
"This is a problem with the Arch Linux package, which is not maintained or supported by Yubico. Until they resolve the issue I suggest you use the AppImage provided at https://developers.yubico.com/yubioath-desktop/Releases/. Downgrading to ykman 4 would also be a viable option.
All packages of Yubico Authenticator provided by Yubico have a compatible version of ykman included, and our recommendation is for third party packages to do the same. If this is against packaging guidelines they should at least be limiting dependencies within compatible versions according to Semantic Versioning."
>Another thing is lack of testing before pushing update.
I tested `ykman` before publishing. I can commit to pushing this to `[community-testing]` instead of directly to `[community]` is anyone is actually committing to testing the yubico related packages.
Regardless, I'll take a quick stab at porting the python script to yubikey-manager 5.x before downgrading the package.
AFAIK major updates elsewhere (i.e. openssl or llvm) are put on hold in order to ensure they are safe to land in the repos and I believe major updates of yubikey-manager should be treated the same especially when there are just two packages to test.
I don't want to blame anyone and I understand business of maintainers yet I think there is room for improvement for the future in case of yubikey-manager major upgrades.
I don't use yubikey-manager-qt and didn't think much of it.
>AFAIK major updates elsewhere (i.e. openssl or llvm) are put on hold in order to ensure they are safe to land in the repos and I believe major updates of yubikey-manager should be treated the same especially when there are just two packages to test.
openssl and llvm will break entire ecosystems, and a bad update to openssl is going to break pacman.
This update has effectively just broken two GUI clients and the CLI tooling works perfectly fine. Please don't make such comparisons.
I made this comparison since you claimed llvm update is blocked on one incompatible package i the repos: https://old.reddit.com/r/archlinux/comments/yc68pp/what_happened_to_llvm_15/itli2r2/
Future yubikey-manger updates should be blocked in similar manner. I think everything was said on this topic.
I use this package both privately and for business. Without further consultation with my employer, it is quite reasonable to contribute my work time to test this application, as quite a few employees use this app. If you are interested please let me know how we would like to communicate the testing of a new version. I would be honored to support you and thank you for the work.
Harm