Bug 10147 - plugging in ACR38U device in USB port crashes pcscd service
Summary: plugging in ACR38U device in USB port crashes pcscd service
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Sander Lepik
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-18 22:01 CEST by Bert Aerts
Modified: 2013-05-26 10:02 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Bert Aerts 2013-05-18 22:01:41 CEST
Description of problem:

(Mageia 3 RC x86_64 plus all updates)

Plug in ACR38U USB (Belgian) identity card reader, makes pcscd service crash:

dmesg
[18041.844607] usb 1-1: new full-speed USB device number 12 using xhci_hcd
[18041.859146] usb 1-1: New USB device found, idVendor=072f, idProduct=9000
[18041.859152] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[18041.859155] usb 1-1: Product: ACR38 USB Reader         
[18041.859158] usb 1-1: Manufacturer: ACS      
[18041.885018] pcscd[13728]: segfault at 4 ip 00007fef7dca4520 sp 00007fef7dbec8c0 error 6 in libc-2.17.so[7fef7dbef000+1a9000]

Service can not be started again, due to segmentation fault.
When device is plugged out, service pcscd can be started successfully.

Following is installed:

[bert@Dell7720Mageia3 eid-viewer-4.0.4]$ rpm -aq | grep acr38
lib64acr38u0-1.7.10-4.mga3
lib64acr38u-devel-1.7.10-4.mga3
acr38u-1.7.10-4.mga3

[bert@Dell7720Mageia3 eid-viewer-4.0.4]$ rpm -aq | grep pcs
lib64pcsclite-devel-1.8.7-3.mga3
lib64pcscspy0-1.8.7-3.mga3
pcsc-lite-1.8.7-3.mga3
lib64pcsclite1-1.8.7-3.mga3

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Bert Aerts 2013-05-18 22:17:54 CEST
Same experiment in Mageia 2 x86_64 (with all updates) works perfectly well !
Comment 2 Sander Lepik 2013-05-20 15:43:06 CEST
What happens if you remove acr38 related packages? Will it crash then too or not? Just to test if the problem is in pcsc-lite or in acr38 driver..

Keywords: (none) => NEEDINFO
CC: (none) => sander.lepik

Comment 3 Bert Aerts 2013-05-20 16:16:11 CEST
I removed acr38u packages:
lib64acr38u0-1.7.10-4.mga3
lib64acr38u-devel-1.7.10-4.mga3
acr38u-1.7.10-4.mga3

dmesg now reports
[24779.196415] usb 3-2: new full-speed USB device number 6 using xhci_hcd
[24779.210884] usb 3-2: New USB device found, idVendor=072f, idProduct=9000
[24779.210889] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[24779.210893] usb 3-2: Product: ACR38 USB Reader         
[24779.210895] usb 3-2: Manufacturer: ACS      

pcscd service can be stopped and started without problems.

I think that does not prove that acr38u creates the crash of pcscd service, as now nothing will happen with the device because driver is not present.
Comment 4 Sander Lepik 2013-05-20 18:11:38 CEST
I created a new package: https://www.dropbox.com/s/2zy2wrkahdx5jt9/acsccid-1.0.4-1.mga3.x86_64.rpm - If you install that one and restart pcscd would that change anything? Don't install acr38u back, just the new driver.
Comment 5 Bert Aerts 2013-05-20 20:04:15 CEST
!!! GREAT !!!

This alternative driver for ACR38U just works perfectly!

Please add this package to the Mageia 3 distribution.
And put a note in the Release Notes about it.
Comment 6 Bert Aerts 2013-05-20 20:05:03 CEST
Thank you very much, Sander !
Comment 7 Sander Lepik 2013-05-20 20:10:06 CEST
I'll submit it to Cauldron if Cauldron opens again but I'm afraid there is nothing I can do about Mageia 3 as we can't submit new packages into stable release.

Keywords: NEEDINFO => (none)
Assignee: bugsquad => sander.lepik

Comment 8 Sander Lepik 2013-05-26 10:02:00 CEST
This is now pushed into Cauldron. I'll close this bug. If we are gonna have backports for Mageia 3 I'll backport it for Mageia 3 too. If not then we just have to deal with it.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.