Le 22/01/2016 15:18, eric2.vale...@orange.com a écrit :
On 01/22/2016 03:06 PM, Ludovic Rousseau wrote:
Le 22/01/2016 13:11, eric2.vale...@orange.com a écrit :
On 01/20/2016 03:07 PM, Ludovic Rousseau wrote:
It does not look like the problem is the Broadcom reader.
Can you generate a log as documented in
https://pcsclite.alioth.debian.org/pcsclite.html#support ?
Start the log and then connect your problematic mass-storage USB key.
Thanks
Here is the requested log file. Note that I'm not sure the trace will help:
1) As soon as I launch it, I have continuous traces but process does not
even appaers in the top first twenty line,
You have 1 (or 2) application that is continuously (every 200 ms) asking PC/SC
for card status. That is a very bad PC/SC behaviour.
You should try to identify the bogus application and fix it.
I guess I have installed a binary blob packages given my a key manufacturer :-(
SACSrv il you kinow wht it is... Will kill it and retry
You can identify a process using PC/SC using:
$ sudo fuser /usr/lib/x86_64-linux-gnu/libpcsclite.so.1
Maybe a problem in libusb.
What version of libusb are you using?
Run pcscd as:
$ sudo LIBUSB_DEBUG=99 /usr/sbin/pcscd -dfa
Bye
--
Dr. Ludovic Rousseau
