Bug 1413271
Summary: | Cyberjack e-com will not work. | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Frank Büttner <bugzilla> | ||||||
Component: | pcsc-cyberjack | Assignee: | Patrick C. F. Ernzer <pcfe> | ||||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 27 | CC: | fedora, pcfe | ||||||
Target Milestone: | --- | Keywords: | Reopened | ||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2018-11-30 21:26:23 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Frank Büttner
2017-01-14 09:04:00 UTC
Can you give exact steps to reproduce ? When did you plugin the card-reader, when did you start the daemon etc. I can not reproduce it with my ecom-usb or my secoder reader (also seen as ecom). Can you start pcscd directly ? I have to make /var/run/pcscd world-writable to be able to start pcscd as normal user. And I think pcscd.socket should start the dameon (via pcscd.service ?) automatically when the reader is plugged in. But this does not happen. I can start the daemon as root or via pcscd.service explicitely without error. By the way, I see /var/run/openct in your log-snippet, but as far as I know this is not part of Fedora. Where does it come from ? Hi, I have tried both. Start the daemon when the device is connected and connect the device after start the daemon. In both scenarios, the device is recognized. But the init of it fails. I also try different usb ports. When I enable the debug mode I get the following error in the debug log: COMERR:[00003d2c]:2017/01/14 11:11:22:769448:[<USB>]:Using USB implementation 1 COMERR:[00003d2c]:2017/01/14 11:11:22:774867:[<USB>]:Claim interface COMERR:[00003d2c]:2017/01/14 11:11:22:774906:[<USB>]:Unable to start receiving interrupts COMERR:[00003d51]:2017/01/14 11:12:25:641184:[<USB>]:Using USB implementation 1 COMIN :[00003d51]:2017/01/14 11:12:25:645418:[<USB>]:ausb.c: 112: ausb_set_configuration COMERR:[00003d51]:2017/01/14 11:12:25:645786:[<USB>]:Claim interface COMIN :[00003d51]:2017/01/14 11:12:25:645808:[<USB>]:ausb.c: 92: ausb_claim_interface COMIN :[00003d51]:2017/01/14 11:12:25:645833:[<USB>]:ausb.c: 81: registering callback:0x7f780011b020 COMIN :[00003d51]:2017/01/14 11:12:25:645841:[<USB>]:ausb.c: 186: ausb_start_interrupt COMIN :[00003d51]:2017/01/14 11:12:25:645849:[<USB>]:ausb11.c: 334: Starting interrupt pipe for endpoint 131 COMIN :[00003d51]:2017/01/14 11:12:25:645860:[<USB>]:ausb11.c: 350: Error on libusb_submit_transfer: -1 COMERR:[00003d51]:2017/01/14 11:12:25:645867:[<USB>]:Unable to start receiving interrupts COMIN :[00003d51]:2017/01/14 11:12:25:645875:[<USB>]:ausb.c: 176: ausb_close COMERR:[00003d99]:2017/01/14 11:14:55:243305:[<USB>]:Using USB implementation 1 COMIN :[00003d99]:2017/01/14 11:14:55:246228:[<USB>]:ausb.c: 112: ausb_set_configuration COMERR:[00003d99]:2017/01/14 11:14:55:246463:[<USB>]:Claim interface COMIN :[00003d99]:2017/01/14 11:14:55:246474:[<USB>]:ausb.c: 92: ausb_claim_interface COMIN :[00003d99]:2017/01/14 11:14:55:246494:[<USB>]:ausb.c: 81: registering callback:0x7f5a2f7bc020 COMIN :[00003d99]:2017/01/14 11:14:55:246503:[<USB>]:ausb.c: 186: ausb_start_interrupt COMIN :[00003d99]:2017/01/14 11:14:55:246512:[<USB>]:ausb11.c: 334: Starting interrupt pipe for endpoint 131 COMIN :[00003d99]:2017/01/14 11:14:55:246522:[<USB>]:ausb11.c: 350: Error on libusb_submit_transfer: -1 COMERR:[00003d99]:2017/01/14 11:14:55:246528:[<USB>]:Unable to start receiving interrupts COMIN :[00003d99]:2017/01/14 11:14:55:246533:[<USB>]:ausb.c: 176: ausb_close I can start the daemon itself without any errors. rpm -qf /var/run/openct openct-0.6.20-12.fc23.x86_64 rpm -qi openct Name : openct Version : 0.6.20 Release : 12.fc23 Architecture: x86_64 Install Date: Di 26 Jan 2016 10:34:38 CET Group : System Environment/Libraries Size : 890771 License : LGPLv2+ Signature : RSA/SHA256, Sa 25 Jul 2015 07:59:17 CEST, Key ID 32474cf834ec9cba Source RPM : openct-0.6.20-12.fc23.src.rpm Build Date : Do 23 Jul 2015 04:44:32 CEST Build Host : buildvm-06.phx2.fedoraproject.org This package comes from fedora 23. This was running before I upgrade to fedora 25. Today I tested the device on an other system. The same result. Native in fedora it fails. On an virtual Windows on the same hardware will work. Created attachment 1249495 [details]
The older driver patched for F25
Some news for it. Using the older pcsc-cyberjack-3.99.5final.SP08-2 will work. But it will need an patch to compile for fedora 25. So I include it. I don't know what was changed in SP09-1. Version SP10 will also fail. Created attachment 1249589 [details] Working actual package I have found an patch for the driver module at the debian bug tracker. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819659 It will fix it. I have create an complete srpm contains it. When using it, please remove the cjgeldkarte part. Because after some tests, the tool is useless since, the ctapi part was removed from the driver package. I just maile Frank Neuber, (on of) the upstream devleoper(s), about the commented part in the initialization. As far as I see the comment appears in SP10, so it can not be the reason for your issue with the SP09 package. This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Same for F26 This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |