No Yubikey NEO found - in ubuntu 14.04

[kmpm]

It seems as if the application can not find the device.
Each time I click "Show Code" a message box with a warning about no Yubikey is shown.

Output in console window

'NoneType' object has no attribute '_cmd_ok'
'Failure to establish context: Service not available.'

Output from lsusb

$ sudo lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 044e:3017 Alps Electric Co., Ltd BCM2046 Bluetooth Device
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 004: ID 1050:0110 Yubico.com 
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 05ca:183a Ricoh Co., Ltd Visual Communication Camera VGP-VCC7 [R5U870]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[kmpm]

Actually it's the same in another computer running Windows 8.1 as well.

[jyundt]

Same thing in Fedora 19 running yubioath-desktop-0.1.0:

Failed to load symbol for: SCardCancelTransaction, /lib64/libpcsclite.so.1: undefined symbol: SCardCancelTransaction!
'NoneType' object has no attribute '_cmd_ok'
'Failure to establish context: Service not available.'

Output from lsusb:

Bus 002 Device 009: ID 1050:0111 Yubico.com Yubikey NEO OTP+CCID

[TomAtYubico]

kmpm, looks more like your NEO is not in mode 82 or your Yubioath applet is not correctly installed.
Please, download the Yubico NEO manager and configure your new for composite mode touch eject and install the yubioath applet.

[kmpm]

The applet works perfectly in yubioath for android and I really don't want to reinstall the keys.
But I will have a look.

[TomAtYubico]

If it works on Android, then it is correctly installed.

• Does your computer detects the NEO correctly?
• Is the NEO listed in the Info.plist file (on Linux) ?

Please use the Yubikey NEO manager on Windows to check / configure the Yubikey NEO and try again (use different usb ports if necessary or different computers)

[jyundt]

The applet works perfectly in yubioath for android

FWIW, my NEO also works fine with the Android app, this is the first time I've tried the desktop (python) client.

Please use the Yubikey NEO manager on Windows to check / configure the Yubikey NEO and try again

Are binaries for the yubikey NEO manager available on Linux? Or are there instructions for building on Linux?

[kmpm]

• How do I check that the computer detects the NEO? When doing a quick press it generates the otp as it should and long press generates my static password.
• Where should this Info.plist file be located?

[kmpm]

Got it to work in windows now. Had to change connection mode from the default HID to HID+CCID (with touch eject ) ie. mode 82.
I did the change using the NEO manager.
This should perhaps be noted in the README.

Have yet to test in Linux though..

[jervine]

I saw the same error messages with Fedora 20, and traced it to not having the pcsc daemon started. You might want to check that. Unfortunately, the yubico authenticator system tray icon disappears for me after showing the codes once (the applet is still running though ...). Fedora 20 XFCE4 desktop.

[jyundt]

Success!

I was able to get this to work after installing (and starting) the pcsc daemon on Fedora 19.

[jervine]

jyundt - does the systray icon stay present in your systray after showing the codes? What desktop environment are you using on Fedora 19?

[jyundt]

Yes, it'll stay in the systray after showing a code. However, if it
"minimizes" the icon gets really small.

Fedora 19 / Gnome 3.

On Fri, May 2, 2014 at 7:40 PM, Jonny Ervine notifications@github.comwrote:

jyundt - does the systray icon stay present in your systray after showing
the codes? What desktop environment are you using on Fedora 19?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-42089394
.

[jervine]

Tested with KDE on Fedora 20, and the icon in the systray works as expected. When the codes are displayed the icon remains where it should be (I guess this makes sense as the application is using the python qt bindings).

It seems a separate bug report for this might be necessary.

[kmpm]

It works in Ubuntu 14.04 as expected.
No issues with systray icons.
What was needed was to install pcscd and set mode 82 on the NEO.
Please make a note of this in README or similar

[jas4711]

Documentation improvements seems fine, but I'm wondering if it isn't possible to distinguish between 1) no yubikey inserted, and 2) no pcscd started? If so, maybe the error message could be different, which makes people find the right solution quicker.

[kmpm]

A better error message would be nice. +1