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

Failed to open smart card connection #90

Open
MrRinkana opened this issue Aug 12, 2024 · 17 comments
Open

Failed to open smart card connection #90

MrRinkana opened this issue Aug 12, 2024 · 17 comments

Comments

@MrRinkana
Copy link

I'm not sure what changed but after updating my tumbleweed system today, I can no longer access my TOTP from yubikey authenticator:

Error is: "Failed to open smart card connection - Make sure pcscd is installed and running."

systemctl status pcscd returns: "active (running)"
Installed packages are:

 S  | Name               | Summary                                                                    | Type
---+--------------------+----------------------------------------------------------------------------+--------
i  | libpcsclite1       | PC/SC Smart Card Library                                                   | package
i  | libpcsclite1-32bit | PC/SC Smart Card Library                                                   | package
i  | pcsc-ccid          | PCSC Driver for CCID Based Smart Card Readers and GemPC Twin Serial Reader | package
i  | pcsc-lite          | PC/SC Smart Cards Library                                                  | package

App is running as flatpak, system is opensuse tumbleweed version 20240810

I can check my passkeys trough the app, the home tab seems normal, I can see if the slots are configured.
TOTP and certificates do not work (same error)

@Erick555
Copy link
Contributor

It's possible that opensuse tumbleweed updates pcsclite to 2.3.0 and you hit LudovicRousseau/PCSC#199

You may check with pcscd --version

@MrRinkana
Copy link
Author

This seems indeed to be the case, my pcsc version is 2.3.0.

I assume the flatpack app needs to update its bindings then?

Downgrading one package is not really a thing in tumbleweed as its a rolling release, and as the linked issue mentions wouldn't there be a risk other things break in the system instead?

@Erick555
Copy link
Contributor

The problem with updating flatpak is that it will break non-rolling suse flavors alongside debian, ubuntu and everyone who didn't update to 2.3.0 yet. This is ugly choice for flatpak maintainer.

If you know how to downgrade one package on your system and feel comfortably with it then it's easiest workaround for now and buys some time.

@MrRinkana
Copy link
Author

So there is no way for a flatpak to specify minimum version of a package? Such that an update would be blocked until the distro provides 2.3.0?

I understand that it might be a problem for frequently updated flatpaks, but this one (yubi aunth) is rather stable, maybe it would be possible?

@Erick555
Copy link
Contributor

No, it's not possible for flatpak.

@MrRinkana
Copy link
Author

That's a bummer.. Alright then i assume this issue should be closed as "can't fix", feel free to reopen if it's preferred to keep it as waiting on upstream!

@MrRinkana MrRinkana closed this as not planned Won't fix, can't repro, duplicate, stale Aug 15, 2024
@Erick555
Copy link
Contributor

I think it's better to gave it opened for visibility for other users.

@hafeoz
Copy link

hafeoz commented Aug 17, 2024

So I've created a PR #91 that bumps the pcsc-lite version so that flathubbot can create a test build for it. My understanding is that anyone encountering this issue can use the test build instead:

flatpak install https://dl.flathub.org/build-repo/123756/com.yubico.yubioath.flatpakref

@Fei1Yang
Copy link
Contributor

@Erick555 Can you please merge this PR to the beta branch alongside with all the commits it currently lacking from the master branch, so users with pcsc 2.3 can install it from the flathub-beta repo instead of a flatpakref, therefore retaining auto update functionality?

@Erick555
Copy link
Contributor

@Fei1Yang I'm not maintainer of this app - @Lunarequest is.

@MrRinkana MrRinkana reopened this Aug 21, 2024
@MrRinkana
Copy link
Author

Beta build with the version bump seems like the smoothest transition, i like that idea! Reopening both for visibility and since there is a feasible solution on the horizon in this repo

@Fei1Yang
Copy link
Contributor

Fei1Yang commented Aug 21, 2024

Beta build with the version bump seems like the smoothest transition, i like that idea! Reopening both for visibility and since there is a feasible solution on the horizon in this repo

There is no such thing as "version bump" in flatpak ecosystem, however it also won't be very smooth, flathub-beta is another repository the user needed to add. but it will be better than a flatpakref for sure.

@suntorytimed
Copy link

suntorytimed commented Aug 22, 2024

Having the change in flathub-beta would be great. Right now it's sitting on 6.0.0 anyways. Unfortunately the flatpakref doesn't seem to be avaiable anymore.

Probably best to just force push https://github.com/hafeoz/com.yubico.yubioath/tree/master onto the beta branch. That's at least what I would do.

@Erick555
Copy link
Contributor

flathub doesn't allow force-push to release branches

@Erick555
Copy link
Contributor

beta now supports pcsclite 2.3.0 and above. stable supports below 2.3.0

@edgan
Copy link

edgan commented Oct 15, 2024

Others might be interested in actual instructions of how to build or install the beta.

#101

@bentolor
Copy link

After upgrading from Ubuntu 24.04 noble to Ubuntu 24.10 oracular, I face the same issue.
Writing just for documentation:

The error

 Failed to open smart card connection. Make sure pcscd is installed and running.

The fix/workaround

As mentioned above: Install the beta version.

flatpak uninstall com.yubico.yubioath
flatpak remote-add --user --if-not-exists flathub-beta https://flathub.org/beta-repo/flathub-beta.flatpakrepo
flatpak install flathub-beta com.yubico.yubioath

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

7 participants