Skip to content
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

SCL011 reader stopped working in 2.2.1 #56

Open
fungs opened this issue Sep 27, 2024 · 3 comments
Open

SCL011 reader stopped working in 2.2.1 #56

fungs opened this issue Sep 27, 2024 · 3 comments

Comments

@fungs
Copy link

fungs commented Sep 27, 2024

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

@misery
Copy link
Collaborator

misery commented Sep 27, 2024

Do you have this problem? This cannot be fixed by flatpak or AusweisApp.
LudovicRousseau/PCSC#199

@fungs
Copy link
Author

fungs commented Sep 27, 2024

@misery that's probably it.

I assume that, by upgrading the system PCSC server version, the issue can be fixed then: https://ludovicrousseau.blogspot.com/2022/02/accessing-smart-cards-from-inside.html

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.

Seems like #53 is the reverse case.

According to the authors, PCSC is not made for use in Flatpak (otherwise I would consider this behavior a clear bug).

Anyway, one solution is to downgrade the flatpak and mask it to prevent updates.

@Erick555
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants