You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgrading from 2.2.0 to 2.2.1, it stopped detecting my reader SCM Microsystems SCL011.
This may be an upstream bug, but https://github.com/Governikus/AusweisApp/ does not have an issue tracker and there is no official Linux non-flatpak build to validate against.
It may also be related to the upgrade of pcsc-lite from 2.1.0 to 2.3.0: 9a1a37c
Note: The reader was officially distributed as a starter pack when the electronic ID was introduced. But in version 2.2.0 there appears a notice that it is not officially supported (wtf) and that it might not work properly. However, it works like a charm until 2.2.0
The text was updated successfully, but these errors were encountered:
While the Flatpak version cannot fix the issue itself, it could just stick to the older version of the pscs-lite and upgrade later. Given that the new version 2.3.0 was released about two months ago, we can expect that it is not contained in any major stable Linux distribution, yet. So many users will run into that issue.
Something that flatpak can do is having one pcsc version in main flathub and other in flathub-beta repo then instruct users which version the should install. See example
Upgrading from 2.2.0 to 2.2.1, it stopped detecting my reader SCM Microsystems SCL011.
This may be an upstream bug, but https://github.com/Governikus/AusweisApp/ does not have an issue tracker and there is no official Linux non-flatpak build to validate against.
It may also be related to the upgrade of pcsc-lite from 2.1.0 to 2.3.0: 9a1a37c
Note: The reader was officially distributed as a starter pack when the electronic ID was introduced. But in version 2.2.0 there appears a notice that it is not officially supported (wtf) and that it might not work properly. However, it works like a charm until 2.2.0
The text was updated successfully, but these errors were encountered: