Page MenuHomeSolus

pcscd not wanting to do USB, says drivers missing
Open, NormalPublic

Description

Like we talked on IRC...

Log:

$ sudo pcscd -df
Password: 
00000000 pcscdaemon.c:345:main() pcscd set to foreground with debug send to stdout
00000094 configfile.l:361:DBGetReaderList() Parsing conf file: /etc/reader.conf.d
00000012 pcscdaemon.c:658:main() pcsc-lite 1.8.22 daemon ready.
00000064 hotplug_libudev.c:122:HPReadBundleValues() Cannot open PC/SC drivers directory: /usr/lib64/pcsc/drivers
00000007 hotplug_libudev.c:123:HPReadBundleValues() Disabling USB support for pcscd.
00000006 hotplug_libudev.c:729:HPRegisterForHotplugEvents() No bundle files in pcsc drivers directory: /usr/lib64/pcsc/drivers
00000019 hotplug_libudev.c:730:HPRegisterForHotplugEvents() Disabling USB support for pcscd

No idea what's going on but do use me for debugging if necessary, please.

Event Timeline

Herald removed kyrios123 as the assignee of this task. · View Herald TranscriptNov 21 2017, 3:19 PM

this one is for me !

joebonrichie triaged this task as Normal priority.Nov 21 2017, 3:27 PM

@sixtyfive : you get this error because you haven't installed the drivers (e.g: ccid or acsccid depending on your reader).

Thank you! It's starting up fine now. Would it be possible to make both of these dependencies to 'pcsc-lite'? (I've installed both as I wasn't sure which one I needed and they don't seem to conflict).

For the dependencies, I don't know because it would mean that some useless drivers would be installed (e.g: people who need ccid may not want to have acsccid and vice-versa). I'll let the Solus experts advise on this and follow their recommendation.

joebonrichie added a subscriber: joebonrichie.EditedNov 21 2017, 7:02 PM

I mean, we have nvidia drivers installed by default. How big are the package sizes of ccid and acsccid?

Installed, 150KB and 146KB respectively.

I mean, we have nvidia drivers installed by default

No we don't - we have xorg nouveau driver installed.

Which noone having an integrated GPU only uses, his point prolly?

Derp, yes ikey is right *smack head*. Anyway @kyrios123 I don't see a problem with adding both acsccid and ccid as rundeps as they are super small and don't rely on anything.

kyrios123 added a comment.EditedNov 22 2017, 8:05 AM

Or we could do the other way around: define pcsc-lite as a dependency of ccid and acsccid (this would make more sense since pcsc-lite-devel is a build dependency of these packages)

As a user, it goes like this:

"My online banking is Jameica"

"Jameica says it needs PCSC to connect to my card reader"

"eopkg sr pcsc"

"Oh cool, there's 'pcsc-lite'"

"eopkg it pcsc-lite"

So, not sure about going the other way around...

JoshStrobl moved this task from Backlog to Package Fixes on the Software board.Nov 24 2017, 6:17 PM

Or we could do the other way around: define pcsc-lite as a dependency of ccid and acsccid (this would make more sense since pcsc-lite-devel is a build dependency of these packages)

Just noticed I claimed this task then nothing was done since people have different view on what should be done. I still believe that the proposal I made is the right way to set the dependencies. And since it is foreseen to have one day hotplug driver installation, when the user will plug a card reader, the ldm will install the appropriate driver and the driver will request pcsc-lite and the system will be ready.

If we proceed the other way around, in addition to the ugly cross dependencies, the user will plug the card reader, ldm will install the correct driver then the user will have to manually install pcsc-lite (which is dumb imo), and pcsc-lite will also install an unnecessary driver.

Guys & girls, any thoughts about this ? What shall we do ?

First thought that comes to mind: atm there's no ldm yet. So make the driver a dependency of the software now and then swap it when hotplug driver installation has arrived, on which, if I understand you correctly, there's no eta anyways.