[Touch-packages] [Bug 1879206] Re: cups hplip not install printer
After sudo apt purge ippusbxd and rebooting, I was able to print and scan with HP Deskjet 3639 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448616] Re: xubuntu15.04 goes into sleep after power-up
Hi Martin, The lid is always open (as you can't power up when the lid is closed, the lid covers the power-button). No extra monitor is attached. First of all, when the power-switch-rules are disabled, the machine starts up normally (no hibernate) as well as the power-down sequence is normal again (it just powers off = no longer to power off by means of the terminal-command sudo shutdown - h now. Here are the power-rules underneath: # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. ACTION==remove, GOTO=power_switch_end SUBSYSTEM==input, KERNEL==event*, SUBSYSTEMS==acpi, TAG+=power-switch SUBSYSTEM==input, KERNEL==event*, KERNELS==thinkpad_acpi, TAG+=power-switch SUBSYSTEM==input, KERNEL==event*, ATTRS{name}==twl4030_pwrbutton, TAG+=power-switch SUBSYSTEM==input, KERNEL==event*, ATTRS{name}==tps65217_pwr_but, TAG+=power-switch LABEL=power_switch_end When powering down you can shortly the Xubuntu-screen as before, while when the power-rules are active, the screen immediately goes black. For the second test, I enabled the rules again and set the debug-flag. The output of the journal is attached. ** Attachment added: JournalWithDebug.txt https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448616/+attachment/4386805/+files/JournalWithDebug.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1448616 Title: xubuntu15.04 goes into sleep after power-up Status in systemd package in Ubuntu: Incomplete Bug description: The machine powers up and then goes automatically into sleep. Pressing the power-button again gives the common log-in screen. This appears to be timed, as if you don't succeed to enter your password within a short time, it goes back into sleep again. During booting the screen is blank. Once logged in, everything runs fine, except that the power- down-button doesn't work prperly, the machine goes into sleep. You can only power the machine down by means of sudo shutdown -h now. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CurrentDesktop: XFCE Date: Sun Apr 26 10:03:11 2015 InstallationDate: Installed on 2014-04-20 (370 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. Inspiron 6000 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=863ca210-f8a1-4d13-9e3a-e173e31bc22d ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-04-24 (1 days ago) dmi.bios.date: 07/22/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0X9238 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/22/2005:svnDellInc.:pnInspiron6000:pvr:rvnDellInc.:rn0X9238:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 6000 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448616] Re: xubuntu15.04 goes into sleep after power-up
Hereby the ouput of journalctl attached in info.txt. Hope It gives you some clues. ** Attachment added: info.txt https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448616/+attachment/4385839/+files/info.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1448616 Title: xubuntu15.04 goes into sleep after power-up Status in systemd package in Ubuntu: Incomplete Bug description: The machine powers up and then goes automatically into sleep. Pressing the power-button again gives the common log-in screen. This appears to be timed, as if you don't succeed to enter your password within a short time, it goes back into sleep again. During booting the screen is blank. Once logged in, everything runs fine, except that the power- down-button doesn't work prperly, the machine goes into sleep. You can only power the machine down by means of sudo shutdown -h now. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CurrentDesktop: XFCE Date: Sun Apr 26 10:03:11 2015 InstallationDate: Installed on 2014-04-20 (370 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. Inspiron 6000 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=863ca210-f8a1-4d13-9e3a-e173e31bc22d ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-04-24 (1 days ago) dmi.bios.date: 07/22/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0X9238 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/22/2005:svnDellInc.:pnInspiron6000:pvr:rvnDellInc.:rn0X9238:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 6000 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448616] [NEW] xubuntu15.04 goes into sleep after power-up
Public bug reported: The machine powers up and then goes automatically into sleep. Pressing the power-button again gives the common log-in screen. This appears to be timed, as if you don't succeed to enter your password within a short time, it goes back into sleep again. During booting the screen is blank. Once logged in, everything runs fine, except that the power-down-button doesn't work prperly, the machine goes into sleep. You can only power the machine down by means of sudo shutdown -h now. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CurrentDesktop: XFCE Date: Sun Apr 26 10:03:11 2015 InstallationDate: Installed on 2014-04-20 (370 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. Inspiron 6000 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=863ca210-f8a1-4d13-9e3a-e173e31bc22d ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-04-24 (1 days ago) dmi.bios.date: 07/22/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0X9238 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/22/2005:svnDellInc.:pnInspiron6000:pvr:rvnDellInc.:rn0X9238:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 6000 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1448616 Title: xubuntu15.04 goes into sleep after power-up Status in systemd package in Ubuntu: New Bug description: The machine powers up and then goes automatically into sleep. Pressing the power-button again gives the common log-in screen. This appears to be timed, as if you don't succeed to enter your password within a short time, it goes back into sleep again. During booting the screen is blank. Once logged in, everything runs fine, except that the power- down-button doesn't work prperly, the machine goes into sleep. You can only power the machine down by means of sudo shutdown -h now. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic i686 ApportVersion: 2.17.2-0ubuntu1 Architecture: i386 CurrentDesktop: XFCE Date: Sun Apr 26 10:03:11 2015 InstallationDate: Installed on 2014-04-20 (370 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. Inspiron 6000 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=863ca210-f8a1-4d13-9e3a-e173e31bc22d ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-04-24 (1 days ago) dmi.bios.date: 07/22/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0X9238 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/22/2005:svnDellInc.:pnInspiron6000:pvr:rvnDellInc.:rn0X9238:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 6000 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240006] Re: Subsequent closing of windows results in small untitled icons in launcher
Ubuntu 14.04. Problem seems to be solved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1240006 Title: Subsequent closing of windows results in small untitled icons in launcher Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: I have an application that creates and destroys a large amount of windows. If a lot of windows have to be closed simultaneously, then a number of untitled window-icons remain in the launcher. These icons can't be removed from the launcher until you log off. Here's a code-snippet underneath which produces this behaviour: #include opencv/highgui.h // includes highGUI definitions int main(int argc, char *argv[]) { const int PlayDelay = 500;// msec const char Escape = 27; // ascii-code CvSize FrameSize; FrameSize.width = 640; FrameSize.height = 480; IplImage* ImageOI = cvCreateImage(FrameSize,IPL_DEPTH_32F,3); cvZero(ImageOI); std::vectorstd::string WindowNames; const int NumberOfWindows = 30; for (int i=0;iNumberOfWindows;i++) { std::stringstream NameTestWindow; NameTestWindow Test; NameTestWindow - i; WindowNames.push_back(NameTestWindow.str()); } while (true) { for (int i=0;iNumberOfWindows;i++) { cvShowImage(WindowNames[i].c_str(),ImageOI); } char c = cvWaitKey(PlayDelay); for (int i=0;iNumberOfWindows;i++) { cvDestroyWindow(WindowNames[i].c_str()); } if (c == Escape ) break; } cvReleaseImage(ImageOI); return 0; ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Oct 15 11:28:28 2013 InstallationDate: Installed on 2013-06-05 (132 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240006/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[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
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
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
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