Bug#825672: Issues with libacr38 and gpg

2016-06-17 Thread Laurent Bigonville
Le 17/06/16 à 21:10, Oliver Winker a écrit : Hi, Indeed, works quite ok so far. Sometimes I need to reinsert the card 2 or 3 times, but pcsc_scan always sees it each time. So might be related to the gpg stack. So for me libacsccid1 looks good as replacement for libacr38. Thanks for the info! :)

Bug#825672: Issues with libacr38 and gpg

2016-06-17 Thread Oliver Winker
Hi, Indeed, works quite ok so far. Sometimes I need to reinsert the card 2 or 3 times, but pcsc_scan always sees it each time. So might be related to the gpg stack. So for me libacsccid1 looks good as replacement for libacr38. Thanks for the info! :) BR, Oliver On Wednesday 15 June 2016 09:

Bug#825672: Issues with libacr38 and gpg

2016-06-15 Thread Giovanni Mascellani
Hi. Il 15/06/2016 09:45, Laurent Bigonville ha scritto: > Hi, > > Apparently you both have some issues with the last upload of libacr38 > and gpg. > > I don't think that upstream is really maintaining this driver anymore, > however it seems they are maintaining (and even in debian!) libacsccid1

Bug#825672: Issues with libacr38 and gpg

2016-06-15 Thread Laurent Bigonville
Hi, Apparently you both have some issues with the last upload of libacr38 and gpg. I don't think that upstream is really maintaining this driver anymore, however it seems they are maintaining (and even in debian!) libacsccid1 instead. Could you please give a try to this other driver and se