Closed suntorytimed closed 6 years ago
Hi! You need to have libnitrokey
package updated as well. Having Nitrokey App newer than libnitrokey
might result in such behavior. Other way around should work well.
@szszszsz Hi, libnitrokey is installed in version 3.3
I see - this version should work. Another possibility is to have both built using a different versions of the compilers, which could generate a different symbol names/table. Could you give a try our AppImage release?
The AppImage does work. I opened up a bug on openSUSE Open Build Service to fix the package.
Could you link it here in case they would have any suggestions?
Thank you!
After a rebuild with the new Qt libraries it still doesn't work for me. I have tried installing it on a clean VM with Tumbleweed and it works there (same snapshot level of Tumbleweed, same Kernel and same version of the packages). It seems like some kind of configuration or another package collides with the app.
A blind guess - perhaps you are using both packages from mixed sources/repositories on your original system (e.g. libnitrokey from a security updates, nitrokey-app from main system repository) and these happen to use different major compilers' versions. Sadly I do not know openSUSE enough to give other hints. Please let me know, if you would solve this.
All Nitrokey packages are part of the same additional repository and build there. It shouldn't be affected by different compilers. But there were some Qt updates in the last week which could have an influence.
I see. Have you tried reinstalling the libnitrokey package?
Expected behaviour
Nitrokey App is started
Current behaviour
Nitrokey App crashes at start
Steps for reproduction
Start Nitrokey App in terminal or via menu entry
Preconditions
Nitrokey Pro doesn't have to be plugged in to reproduce
Steps
Logs
nitrokey-app: symbol lookup error: nitrokey-app: undefined symbol: _ZN8nitrokey15NitrokeyManager31set_encrypted_volume_read_writeEPKc