[Touch-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup
This bugreport has had no activity and has eol. Closing. ** Changed in: pcsc-lite (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1366152 Title: System crash when Vasco-card-reader is plugged in at powerup Status in pcsc-lite package in Ubuntu: Won't Fix Bug description: I'm using VASCO Data Security International Digipass 905 SmartCard Reader which is working fine. However if the device is plugged in at power-up, the device isn't handled well. Although the device is in the ilisted usb-devices, pcsc-scan doesn't find the device at all (Which is normal as the green-led is going out after the kernel starts). If one tries to remove the card-reader, a system-crash happens. After that the pcscd-service seems to be halted : pcsc_scan PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau Compiled with PC/SC lite version: 1.8.10 SCardEstablishContext: Service not available. One can recover from this problem by 1. Unplugging the reader 2. Manually starting the service again by sudo service pcscd start 3. Plugging back the reader in (green led stays on, red led goes on when a card is put in) The bug is not related to a 64-bit architecture as it happens also with 32-bit machines. Info about the device Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 905 SmartCard Reader Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1a44 VASCO Data Security International idProduct 0x0001 Digipass 905 SmartCard Reader bcdDevice1.02 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 93 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass11 Chip/SmartCard bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ChipCard Interface Descriptor: bLength54 bDescriptorType33 bcdCCID 1.00 nMaxSlotIndex 0 bVoltageSupport 3 5.0V 3.0V dwProtocols 3 T=0 T=1 dwDefaultClock 3700 dwMaxiumumClock 3700 bNumClockSupported 1 dwDataRate 9946 bps dwMaxDataRate 318280 bps bNumDataRatesSupp. 53 dwMaxIFSD 254 dwSyncProtocols 0007 2-wire 3-wire I2C dwMechanical dwFeatures 000404BE Auto configuration based on ATR Auto activation on insert Auto voltage selection Auto clock change Auto baud rate change Auto PPS made by CCID Auto IFSD exchange Short and extended APDU level exchange dwMaxCCIDMsgLen 272 bClassGetResponseecho bClassEnvelope echo wlcdLayout none bPINSupport 0 bMaxCCIDBusySlots 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk
[Touch-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup
It looks that the program is crashing somewhere on a process-fork Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb7cfcb40 (LWP 9526)] 0xb7d0b442 in ?? () (gdb) bt #0 0xb7d0b442 in ?? () #1 0xb7cfc340 in ?? () #2 0xb7ec24ce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 (gdb) I added a debug-log, with a list of breakpoints. The program is receiving the exception while I'm stepping through the code. So I needed more breakpoints in order to capture the problem. Can you please give a suggestion. ** Attachment added: LogDebugVascoReader.txt https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1366152/+attachment/4203515/+files/LogDebugVascoReader.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1366152 Title: System crash when Vasco-card-reader is plugged in at powerup Status in “pcsc-lite” package in Ubuntu: New Bug description: I'm using VASCO Data Security International Digipass 905 SmartCard Reader which is working fine. However if the device is plugged in at power-up, the device isn't handled well. Although the device is in the ilisted usb-devices, pcsc-scan doesn't find the device at all (Which is normal as the green-led is going out after the kernel starts). If one tries to remove the card-reader, a system-crash happens. After that the pcscd-service seems to be halted : pcsc_scan PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.8.10 SCardEstablishContext: Service not available. One can recover from this problem by 1. Unplugging the reader 2. Manually starting the service again by sudo service pcscd start 3. Plugging back the reader in (green led stays on, red led goes on when a card is put in) The bug is not related to a 64-bit architecture as it happens also with 32-bit machines. Info about the device Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 905 SmartCard Reader Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1a44 VASCO Data Security International idProduct 0x0001 Digipass 905 SmartCard Reader bcdDevice1.02 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 93 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass11 Chip/SmartCard bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ChipCard Interface Descriptor: bLength54 bDescriptorType33 bcdCCID 1.00 nMaxSlotIndex 0 bVoltageSupport 3 5.0V 3.0V dwProtocols 3 T=0 T=1 dwDefaultClock 3700 dwMaxiumumClock 3700 bNumClockSupported 1 dwDataRate 9946 bps dwMaxDataRate 318280 bps bNumDataRatesSupp. 53 dwMaxIFSD 254 dwSyncProtocols 0007 2-wire 3-wire I2C dwMechanical dwFeatures 000404BE Auto configuration based on ATR Auto activation on insert Auto voltage selection Auto clock change Auto baud rate change Auto PPS made by CCID Auto IFSD exchange Short and extended APDU level exchange dwMaxCCIDMsgLen 272 bClassGetResponseecho bClassEnvelope echo wlcdLayout none bPINSupport 0 bMaxCCIDBusySlots 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 32 Endpoint
[Touch-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup
Does the SIGSEGV, Segmentation fault happens inside udev_monitor_receive_device()? In that case can you update libudev? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1366152 Title: System crash when Vasco-card-reader is plugged in at powerup Status in “pcsc-lite” package in Ubuntu: New Bug description: I'm using VASCO Data Security International Digipass 905 SmartCard Reader which is working fine. However if the device is plugged in at power-up, the device isn't handled well. Although the device is in the ilisted usb-devices, pcsc-scan doesn't find the device at all (Which is normal as the green-led is going out after the kernel starts). If one tries to remove the card-reader, a system-crash happens. After that the pcscd-service seems to be halted : pcsc_scan PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.8.10 SCardEstablishContext: Service not available. One can recover from this problem by 1. Unplugging the reader 2. Manually starting the service again by sudo service pcscd start 3. Plugging back the reader in (green led stays on, red led goes on when a card is put in) The bug is not related to a 64-bit architecture as it happens also with 32-bit machines. Info about the device Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 905 SmartCard Reader Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1a44 VASCO Data Security International idProduct 0x0001 Digipass 905 SmartCard Reader bcdDevice1.02 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 93 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass11 Chip/SmartCard bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ChipCard Interface Descriptor: bLength54 bDescriptorType33 bcdCCID 1.00 nMaxSlotIndex 0 bVoltageSupport 3 5.0V 3.0V dwProtocols 3 T=0 T=1 dwDefaultClock 3700 dwMaxiumumClock 3700 bNumClockSupported 1 dwDataRate 9946 bps dwMaxDataRate 318280 bps bNumDataRatesSupp. 53 dwMaxIFSD 254 dwSyncProtocols 0007 2-wire 3-wire I2C dwMechanical dwFeatures 000404BE Auto configuration based on ATR Auto activation on insert Auto voltage selection Auto clock change Auto baud rate change Auto PPS made by CCID Auto IFSD exchange Short and extended APDU level exchange dwMaxCCIDMsgLen 272 bClassGetResponseecho bClassEnvelope echo wlcdLayout none bPINSupport 0 bMaxCCIDBusySlots 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer Type
[Touch-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup
I'm able to build these packages (./configure, make and sudo make install - after installing the missing packages). I know how to debug C/C++-programs, but I have never done this for such a type of application. If you can help me with some commands in order to start the debugging of the build software, I'll find my way in finding the problem. I see that some extra files have been installed in /usr/local, so It looks that everything is ready to analyse the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1366152 Title: System crash when Vasco-card-reader is plugged in at powerup Status in “pcsc-lite” package in Ubuntu: New Bug description: I'm using VASCO Data Security International Digipass 905 SmartCard Reader which is working fine. However if the device is plugged in at power-up, the device isn't handled well. Although the device is in the ilisted usb-devices, pcsc-scan doesn't find the device at all (Which is normal as the green-led is going out after the kernel starts). If one tries to remove the card-reader, a system-crash happens. After that the pcscd-service seems to be halted : pcsc_scan PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.8.10 SCardEstablishContext: Service not available. One can recover from this problem by 1. Unplugging the reader 2. Manually starting the service again by sudo service pcscd start 3. Plugging back the reader in (green led stays on, red led goes on when a card is put in) The bug is not related to a 64-bit architecture as it happens also with 32-bit machines. Info about the device Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 905 SmartCard Reader Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1a44 VASCO Data Security International idProduct 0x0001 Digipass 905 SmartCard Reader bcdDevice1.02 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 93 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass11 Chip/SmartCard bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ChipCard Interface Descriptor: bLength54 bDescriptorType33 bcdCCID 1.00 nMaxSlotIndex 0 bVoltageSupport 3 5.0V 3.0V dwProtocols 3 T=0 T=1 dwDefaultClock 3700 dwMaxiumumClock 3700 bNumClockSupported 1 dwDataRate 9946 bps dwMaxDataRate 318280 bps bNumDataRatesSupp. 53 dwMaxIFSD 254 dwSyncProtocols 0007 2-wire 3-wire I2C dwMechanical dwFeatures 000404BE Auto configuration based on ATR Auto activation on insert Auto voltage selection Auto clock change Auto baud rate change Auto PPS made by CCID Auto IFSD exchange Short and extended APDU level exchange dwMaxCCIDMsgLen 272 bClassGetResponseecho bClassEnvelope echo wlcdLayout none bPINSupport 0 bMaxCCIDBusySlots 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None
[Touch-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup
$ gdb /usr/local/sbin/pcscd (gdb) set args -dfa (gdb) run remove the reader do make pcscd crash (gdb) backtrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1366152 Title: System crash when Vasco-card-reader is plugged in at powerup Status in “pcsc-lite” package in Ubuntu: New Bug description: I'm using VASCO Data Security International Digipass 905 SmartCard Reader which is working fine. However if the device is plugged in at power-up, the device isn't handled well. Although the device is in the ilisted usb-devices, pcsc-scan doesn't find the device at all (Which is normal as the green-led is going out after the kernel starts). If one tries to remove the card-reader, a system-crash happens. After that the pcscd-service seems to be halted : pcsc_scan PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.8.10 SCardEstablishContext: Service not available. One can recover from this problem by 1. Unplugging the reader 2. Manually starting the service again by sudo service pcscd start 3. Plugging back the reader in (green led stays on, red led goes on when a card is put in) The bug is not related to a 64-bit architecture as it happens also with 32-bit machines. Info about the device Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 905 SmartCard Reader Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1a44 VASCO Data Security International idProduct 0x0001 Digipass 905 SmartCard Reader bcdDevice1.02 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 93 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass11 Chip/SmartCard bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ChipCard Interface Descriptor: bLength54 bDescriptorType33 bcdCCID 1.00 nMaxSlotIndex 0 bVoltageSupport 3 5.0V 3.0V dwProtocols 3 T=0 T=1 dwDefaultClock 3700 dwMaxiumumClock 3700 bNumClockSupported 1 dwDataRate 9946 bps dwMaxDataRate 318280 bps bNumDataRatesSupp. 53 dwMaxIFSD 254 dwSyncProtocols 0007 2-wire 3-wire I2C dwMechanical dwFeatures 000404BE Auto configuration based on ATR Auto activation on insert Auto voltage selection Auto clock change Auto baud rate change Auto PPS made by CCID Auto IFSD exchange Short and extended APDU level exchange dwMaxCCIDMsgLen 272 bClassGetResponseecho bClassEnvelope echo wlcdLayout none bPINSupport 0 bMaxCCIDBusySlots 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk
[Touch-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup
And log-file when the reader is ok ** Attachment added: LogCardReaderOK.txt https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1366152/+attachment/4196928/+files/LogCardReaderOK.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1366152 Title: System crash when Vasco-card-reader is plugged in at powerup Status in “pcsc-lite” package in Ubuntu: New Bug description: I'm using VASCO Data Security International Digipass 905 SmartCard Reader which is working fine. However if the device is plugged in at power-up, the device isn't handled well. Although the device is in the ilisted usb-devices, pcsc-scan doesn't find the device at all (Which is normal as the green-led is going out after the kernel starts). If one tries to remove the card-reader, a system-crash happens. After that the pcscd-service seems to be halted : pcsc_scan PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.8.10 SCardEstablishContext: Service not available. One can recover from this problem by 1. Unplugging the reader 2. Manually starting the service again by sudo service pcscd start 3. Plugging back the reader in (green led stays on, red led goes on when a card is put in) The bug is not related to a 64-bit architecture as it happens also with 32-bit machines. Info about the device Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 905 SmartCard Reader Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1a44 VASCO Data Security International idProduct 0x0001 Digipass 905 SmartCard Reader bcdDevice1.02 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 93 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass11 Chip/SmartCard bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ChipCard Interface Descriptor: bLength54 bDescriptorType33 bcdCCID 1.00 nMaxSlotIndex 0 bVoltageSupport 3 5.0V 3.0V dwProtocols 3 T=0 T=1 dwDefaultClock 3700 dwMaxiumumClock 3700 bNumClockSupported 1 dwDataRate 9946 bps dwMaxDataRate 318280 bps bNumDataRatesSupp. 53 dwMaxIFSD 254 dwSyncProtocols 0007 2-wire 3-wire I2C dwMechanical dwFeatures 000404BE Auto configuration based on ATR Auto activation on insert Auto voltage selection Auto clock change Auto baud rate change Auto PPS made by CCID Auto IFSD exchange Short and extended APDU level exchange dwMaxCCIDMsgLen 272 bClassGetResponseecho bClassEnvelope echo wlcdLayout none bPINSupport 0 bMaxCCIDBusySlots 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN
[Touch-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup
Thank you Ludovic for your quick response. I generated to log-files, logcardrea...@powerup.txt in case it goes wrong (only when the card-reader is plugged in while the computer is starting-up or rebooting LogCardReaderOK.txt after the crash - removed the reader and sudo service pcscd start /usr/sbin/pcscd --version pcsc-lite version 1.8.10. Copyright (C) 1999-2002 by David Corcoran corco...@linuxnet.com. Copyright (C) 2001-2011 by Ludovic Rousseau ludovic.rouss...@free.fr. Copyright (C) 2003-2004 by Damien Sauveron sauve...@labri.fr. Report bugs to mus...@lists.musclecard.com. Enabled features: Linux x86_64-pc-linux-gnu serial usb libudev usbdropdir=/usr/lib/pcsc/drivers ipcdir=/var/run/pcscd configdir=/etc/reader.conf.d pcsc_scan (when the reader is ok) PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.8.10 Using reader plug'n play mechanism Scanning present readers... 0: VASCO DP905v1.1 00 00 Sat Sep 6 10:18:48 2014 Reader 0: VASCO DP905v1.1 00 00 Card state: Card removed, apt-cache policy pcscd pcscd: Geïnstalleerd: 1.8.10-1ubuntu1 Kandidaat: 1.8.10-1ubuntu1 Versietabel: *** 1.8.10-1ubuntu1 0 500 http://be.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status Middleware = eid-mw low-level support for Belgian Electronic Identity Card apt-cache policy eid-mw eid-mw: Geïnstalleerd: 4.0.6r1620-0trusty1 Kandidaat: 4.0.6r1620-0trusty1 Versietabel: *** 4.0.6r1620-0trusty1 0 500 http://files.eid.belgium.be/debian/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ** Attachment added: logcardrea...@powerup.txt https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1366152/+attachment/4196927/+files/LogCardReader%40Powerup.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1366152 Title: System crash when Vasco-card-reader is plugged in at powerup Status in “pcsc-lite” package in Ubuntu: New Bug description: I'm using VASCO Data Security International Digipass 905 SmartCard Reader which is working fine. However if the device is plugged in at power-up, the device isn't handled well. Although the device is in the ilisted usb-devices, pcsc-scan doesn't find the device at all (Which is normal as the green-led is going out after the kernel starts). If one tries to remove the card-reader, a system-crash happens. After that the pcscd-service seems to be halted : pcsc_scan PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.8.10 SCardEstablishContext: Service not available. One can recover from this problem by 1. Unplugging the reader 2. Manually starting the service again by sudo service pcscd start 3. Plugging back the reader in (green led stays on, red led goes on when a card is put in) The bug is not related to a 64-bit architecture as it happens also with 32-bit machines. Info about the device Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 905 SmartCard Reader Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1a44 VASCO Data Security International idProduct 0x0001 Digipass 905 SmartCard Reader bcdDevice1.02 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 93 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass11 Chip/SmartCard bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ChipCard Interface Descriptor: bLength54 bDescriptorType33 bcdCCID 1.00 nMaxSlotIndex 0 bVoltageSupport 3 5.0V 3.0V dwProtocols 3 T=0 T=1 dwDefaultClock 3700 dwMaxiumumClock 3700 bNumClockSupported 1 dwDataRate 9946 bps dwMaxDataRate 318280 bps
[Touch-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup
LogCardReader%40Powerup.txt indicates that the device is not responding correctly: 0024 - 00 65 00 00 00 00 00 00 00 00 00 05000412 ccid_usb.c:751:WriteUSB() write failed (1/4): -7 Resource temporarily unavailable -7 is LIBUSB_ERROR_TIMEOUT So the device is not visible at the PC/SC level. I have no idea what is happening. I suspect a reader firmware bug. I do not see the pcscd crash in this log. Can you run pcscd inside gdb? $ gdb /usr/sbin/pcscd (gdb) set args -dfa (gdb) run remove the reader do make pcscd crash (gdb) backtrace Then send me the complete gdb trace. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1366152 Title: System crash when Vasco-card-reader is plugged in at powerup Status in “pcsc-lite” package in Ubuntu: New Bug description: I'm using VASCO Data Security International Digipass 905 SmartCard Reader which is working fine. However if the device is plugged in at power-up, the device isn't handled well. Although the device is in the ilisted usb-devices, pcsc-scan doesn't find the device at all (Which is normal as the green-led is going out after the kernel starts). If one tries to remove the card-reader, a system-crash happens. After that the pcscd-service seems to be halted : pcsc_scan PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.8.10 SCardEstablishContext: Service not available. One can recover from this problem by 1. Unplugging the reader 2. Manually starting the service again by sudo service pcscd start 3. Plugging back the reader in (green led stays on, red led goes on when a card is put in) The bug is not related to a 64-bit architecture as it happens also with 32-bit machines. Info about the device Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 905 SmartCard Reader Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1a44 VASCO Data Security International idProduct 0x0001 Digipass 905 SmartCard Reader bcdDevice1.02 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 93 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass11 Chip/SmartCard bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ChipCard Interface Descriptor: bLength54 bDescriptorType33 bcdCCID 1.00 nMaxSlotIndex 0 bVoltageSupport 3 5.0V 3.0V dwProtocols 3 T=0 T=1 dwDefaultClock 3700 dwMaxiumumClock 3700 bNumClockSupported 1 dwDataRate 9946 bps dwMaxDataRate 318280 bps bNumDataRatesSupp. 53 dwMaxIFSD 254 dwSyncProtocols 0007 2-wire 3-wire I2C dwMechanical dwFeatures 000404BE Auto configuration based on ATR Auto activation on insert Auto voltage selection Auto clock change Auto baud rate change Auto PPS made by CCID Auto IFSD exchange Short and extended APDU level exchange dwMaxCCIDMsgLen 272 bClassGetResponseecho bClassEnvelope echo wlcdLayout none bPINSupport 0 bMaxCCIDBusySlots 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2
[Touch-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup
Hi, I fear that that the backtrace will be rather disappointing, as the gdb doesn't find any symbols for the pcscd-binary. Now the odd thing is, if you start the gdb if you then remove the card-reader for the first time, it doesn't crash. It is only the second time when the read is removed that the application crashes. As there are no symbols, you get only the addresses in the backtrace. If the gdb starts its notifies me that already another instance of pcscd is running. If you look at the green led of the reader, it goes out just before ubuntu-login-screen pops up. If you remove the reader and plug the reader back in, the green led goes on for a second or two and then goes back out. ** Attachment added: LogGdbVascoReader.txt https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1366152/+attachment/4197264/+files/LogGdbVascoReader.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1366152 Title: System crash when Vasco-card-reader is plugged in at powerup Status in “pcsc-lite” package in Ubuntu: New Bug description: I'm using VASCO Data Security International Digipass 905 SmartCard Reader which is working fine. However if the device is plugged in at power-up, the device isn't handled well. Although the device is in the ilisted usb-devices, pcsc-scan doesn't find the device at all (Which is normal as the green-led is going out after the kernel starts). If one tries to remove the card-reader, a system-crash happens. After that the pcscd-service seems to be halted : pcsc_scan PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.8.10 SCardEstablishContext: Service not available. One can recover from this problem by 1. Unplugging the reader 2. Manually starting the service again by sudo service pcscd start 3. Plugging back the reader in (green led stays on, red led goes on when a card is put in) The bug is not related to a 64-bit architecture as it happens also with 32-bit machines. Info about the device Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 905 SmartCard Reader Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1a44 VASCO Data Security International idProduct 0x0001 Digipass 905 SmartCard Reader bcdDevice1.02 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 93 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass11 Chip/SmartCard bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ChipCard Interface Descriptor: bLength54 bDescriptorType33 bcdCCID 1.00 nMaxSlotIndex 0 bVoltageSupport 3 5.0V 3.0V dwProtocols 3 T=0 T=1 dwDefaultClock 3700 dwMaxiumumClock 3700 bNumClockSupported 1 dwDataRate 9946 bps dwMaxDataRate 318280 bps bNumDataRatesSupp. 53 dwMaxIFSD 254 dwSyncProtocols 0007 2-wire 3-wire I2C dwMechanical dwFeatures 000404BE Auto configuration based on ATR Auto activation on insert Auto voltage selection Auto clock change Auto baud rate change Auto PPS made by CCID Auto IFSD exchange Short and extended APDU level exchange dwMaxCCIDMsgLen 272 bClassGetResponseecho bClassEnvelope echo wlcdLayout none bPINSupport 0 bMaxCCIDBusySlots 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None
[Touch-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup
Could you rebuild pcsc-lite and libccid yourself and install them in /usr/local/ or somewhere else to try to debug the problem? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1366152 Title: System crash when Vasco-card-reader is plugged in at powerup Status in “pcsc-lite” package in Ubuntu: New Bug description: I'm using VASCO Data Security International Digipass 905 SmartCard Reader which is working fine. However if the device is plugged in at power-up, the device isn't handled well. Although the device is in the ilisted usb-devices, pcsc-scan doesn't find the device at all (Which is normal as the green-led is going out after the kernel starts). If one tries to remove the card-reader, a system-crash happens. After that the pcscd-service seems to be halted : pcsc_scan PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.8.10 SCardEstablishContext: Service not available. One can recover from this problem by 1. Unplugging the reader 2. Manually starting the service again by sudo service pcscd start 3. Plugging back the reader in (green led stays on, red led goes on when a card is put in) The bug is not related to a 64-bit architecture as it happens also with 32-bit machines. Info about the device Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 905 SmartCard Reader Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1a44 VASCO Data Security International idProduct 0x0001 Digipass 905 SmartCard Reader bcdDevice1.02 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 93 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass11 Chip/SmartCard bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ChipCard Interface Descriptor: bLength54 bDescriptorType33 bcdCCID 1.00 nMaxSlotIndex 0 bVoltageSupport 3 5.0V 3.0V dwProtocols 3 T=0 T=1 dwDefaultClock 3700 dwMaxiumumClock 3700 bNumClockSupported 1 dwDataRate 9946 bps dwMaxDataRate 318280 bps bNumDataRatesSupp. 53 dwMaxIFSD 254 dwSyncProtocols 0007 2-wire 3-wire I2C dwMechanical dwFeatures 000404BE Auto configuration based on ATR Auto activation on insert Auto voltage selection Auto clock change Auto baud rate change Auto PPS made by CCID Auto IFSD exchange Short and extended APDU level exchange dwMaxCCIDMsgLen 272 bClassGetResponseecho bClassEnvelope echo wlcdLayout none bPINSupport 0 bMaxCCIDBusySlots 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer Type
