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

Seg Fault on Linux #491

Closed
m0rr1gan opened this issue Nov 15, 2019 · 9 comments · Fixed by #493
Closed

Seg Fault on Linux #491

m0rr1gan opened this issue Nov 15, 2019 · 9 comments · Fixed by #493
Labels

Comments

@m0rr1gan
Copy link

  • Yubico Authenticator version: 5.0.1
  • Operating system and version: Arch Linux 5.3.11
  • YubiKey model and version: YubiKey 5 NFC 5.1.1
  • Bug description summary: yubioath-desktop does not register that a yubikey is plugged in and subsequently segfaults when closed

Steps to reproduce

  1. Start yubioath-desktop
  2. it does not register that a yubikey is plugged in
  3. closing, it segfaults and generates a core dump

Expected result

Start yubioath-desktop, it takes a second to register that a yubikey is plugged in, then displays OATH credentials.

Actual results

When I start yubioath-desktop, no yubikeys show up even though they are registered in yubikey-manager-qt and ykman cli. Upon closing yubioath-desktop, a segfault is hit.

Other info

coredump: http://ix.io/21PC
runtime output: http://ix.io/21PD

This behavior was confirmed by another Arch user in IRC.

@m0rr1gan m0rr1gan changed the title Qt5 v5.13.2 causing Seg Fault on Linux Seg Fault on Linux Nov 15, 2019
@gbcox
Copy link

gbcox commented Nov 15, 2019

Not seeing this issue on Fedora 31.

Device type: YubiKey 5 NFC
Firmware version: 5.1.2
Form factor: Keychain (USB-A)
Enabled USB interfaces: OTP+FIDO+CCID
NFC interface is enabled.
Yubico Authenticator 5.0.1

Previously experienced issue that seemed to be #488, but since upgraded to current master of yubikey-manager git 1f22620 no longer experiencing that issue.

@linxon
Copy link

linxon commented Nov 16, 2019

runtime output: http://ix.io/21PD

"PyOtherSide error: Traceback (most recent call last):\n\n File "", line 1, in \n\nNameError: name 'yubikey' is not defined\n"
Unhandled PyOtherSide error: Function not found: 'yubikey.init' (Traceback (most recent call last):

you can temporarily downgrade yubikey-manager to 2.1.1

@Mitch9378
Copy link

Mitch9378 commented Nov 18, 2019

I am also experiencing this issue with yubikey-manager 3.1.0-2 on Arch Linux.

@gbcox it seems Fedora 31 is using a slightly older version:

https://apps.fedoraproject.org/packages/yubikey-manager

3.0.0-6

When you saying you are not experiencing this issue on Fedora 31 are you talking about with the Fedora 31 packaged version as well or just with the most recent build from master as you mentioned?

Just want to be sure because it may help narrow down when this was introduced.

I will note that anyone looking for a potential workaround can use the AppImage in the meantime:

https://developers.yubico.com/yubioath-desktop/Releases/yubioath-desktop-5.0.1-linux.AppImage

yubikey-manager 3.1.0-2 on Arch using the ykman cli directly does work as well

@gbcox
Copy link

gbcox commented Nov 18, 2019

Sorry, I ran some tests and the problem is with yubioath-desktop, not yubikey-manager. The problem occurs with: yubioath-desktop-5.0.0-2.git121efe3.fc31.x86_64
segfault at 7f094c7cfb60 ip 00007f095dcb41cb sp 00007ffcdeeb3bd0 error 7 in libQt5Quick.so.5.12.5[7f095db7c000+2d0000]

The problem doesn't occur with: yubioath-desktop-5.0.1-2.gitc58db92.fc31.x86_64

The rpms mentioned are the Fedora packaged versions.

@Mitch9378
Copy link

Mitch9378 commented Nov 22, 2019

@disp4287

you can use the AppImage as a workaround:

https://developers.yubico.com/yubioath-desktop/Releases/yubioath-desktop-5.0.1-linux.AppImage

I confirmed it is working.

or the ykman cli directly does work as well:

ykman oath code --help 
Usage: ykman oath code [OPTIONS] [QUERY]

  Generate codes.

  Generate codes from credentials stored on your YubiKey. Provide a query string to match one or more specific
  credentials. Touch and HOTP credentials require a single match to be triggered.

Options:
  -H, --show-hidden  Include hidden credentials.
  -s, --single       Ensure only a single match, and output only the code.
  -h, --help         Show this message and exit.

@emlun
Copy link
Member

emlun commented Nov 26, 2019

Confirmed. This seems to be because Python 3.8 broke compatibility with this line of code. We'll see what we can do.

@emlun emlun added the bug label Nov 26, 2019
@emlun
Copy link
Member

emlun commented Nov 26, 2019

Confirmed also that downgrading to Python 3.7 works. So, currently available workarounds are:

@Maryse47
Copy link

Downgrading python on Arch Linux will break all other python packages so it shouldn't count as a workaround.

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

Successfully merging a pull request may close this issue.

7 participants
@emlun @gbcox @Mitch9378 @linxon @Maryse47 @m0rr1gan and others