Bug 802435
| Summary: | remote-viewer does not utilize smart card reader plugged when the client is running | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | David Jaša <djasa> | |
| Component: | libcacard | Assignee: | David Blechter <dblechte> | |
| Status: | CLOSED WONTFIX | QA Contact: | SPICE QE bug list <spice-qe-bugs> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 6.3 | CC: | cfergeau, cwei, dblechte, hbrock, mkenneth, mkrcmari, mzhan, rbalakri, riehecky, rrelyea, salmy, zpeng | |
| Target Milestone: | beta | |||
| Target Release: | 6.3 | |||
| Hardware: | Unspecified | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 801854 | |||
| : | 806038 (view as bug list) | Environment: | ||
| Last Closed: | 2017-12-06 11:03:04 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 806038, 811314, 975600 | |||
| Bug Blocks: | 801854 | |||
|
Description
David Jaša
2012-03-12 14:34:04 UTC
Please provide debug information from qemu side by passing the debug flag to ccid-card-passthru: -device ccid-card-passthru,debug=10 # I don't remember the maximum value for debug, 10 should do Thanks, Alon Maybe usbredir took the device? can you try adding "--spice-disable-usbredir" to remote-viewer invocation? Thanks, Alon Clearing needinfo, all info requested was provided in a debugging session. Managed to reproduce locally, thanks for the help. Alon The bug is not in virt-viewer, it's in libcoolkey and libcacard: coolkey creates a default fake reader and then passes it on to pcscd, confusing it, causing no notifications of new readers. libcacard stops the per-module event blocking thread when there are no slots (caused by removing last reader) Changing component and cloning, have patches for both upstream, will post and start the process of rebasing them. Alon This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. It has been proposed for the next release. If you would like it considered as an exception in the current release, please ask your support representative. For reference, patches: http://patchwork.ozlabs.org/patch/148290/ http://patchwork.ozlabs.org/patch/148291/ http://patchwork.ozlabs.org/patch/148289/ moving to 6.5, the bugs this one is depend on are not fixed yet This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux. This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/ |