| Summary: | Document newly supported HP keyboard KUS1206 with builtin smartcard reader and the keyboard hang issue | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Asha Akkiangady <aakkiang> |
| Component: | Red_Hat_Enterprise_Linux-Release_Notes-6-en-US | Assignee: | Aneta Šteflová Petrová <apetrova> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.8 | CC: | aakkiang, jmagne, kwaldron, rhel-docs, rpattath |
| Target Milestone: | rc | Keywords: | Documentation |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: |
The HP keyboard KUS1206 does not handle smart cards correctly and can become unresponsive
When using the HP keyboard KUS1206 with a built-in smart card reader, you might experience the following problems:
* The keyboard detects smart cards inconsistently.
* When the user logs in to the system with a password and the smart card is not inserted, the following message appears continuously in the /var/log/messages file:
Mar 3 15:05:52 [host_name] pcscd: commands.c:957:CmdGetSlotStatus Card absent or mute
* The keyboard sometimes becomes unresponsive.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-14 06:37:29 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: | |
|
Description
Asha Akkiangady
2016-02-18 13:59:14 UTC
Asha, I found this BZ when going through old doc bugs. Is this a request to document a known issue? If so, it should probably be documented in the Release Notes - that's where known issues are listed. Please let me know if I should change this BZ's component to the correct guide. https://bugzilla.redhat.com/show_bug.cgi?id=1229459#c40 was an issue during RHEL 6.8 testing which was fixed in coolkey build that came with RHEL 6.9. As per https://bugzilla.redhat.com/show_bug.cgi?id=1229459#c74, everything works as expected with the keyboard reader except that SC650 SCP02 was not detected. As per https://bugzilla.redhat.com/show_bug.cgi?id=1229459#c73 developers had confirmed that card is not supported any longer, so it do not need to be tested. So IMO there are no issues that needs to be documented for this bug. Sorry Aneta, Just noticed this is RHEL 6.8 doc bug. In that case you need to document 2 points: 1. Keyboard hung and inconsistency in card detection. 2. When logged into the machine with a password and the smart card is not inserted I see following message continuously (2-3 times in a second) logged in /var/log/messages even when smart card is not inserted: Mar 3 15:05:52 dhcp129-123 pcscd: commands.c:957:CmdGetSlotStatus Card absent or mute Thanks for the clarification, Roshni. It looks like we should add this to the 6.8 Release Notes. Roshni, can you please review the description in the Doc Text field? FYI, I didn't mention RHEL 6.8 anywhere in the text because if we publish the description in the RHEL 6.8 Release Notes, it should be clear that it is related only to this version. Hi Aneta, I feel we can do without this line "The HP keyboard KUS1206 does not handle smart cards correctly and can become unresponsive". The rest of the description looks good to me. (In reply to Roshni from comment #7) > Hi Aneta, > > I feel we can do without this line "The HP keyboard KUS1206 does not handle > smart cards correctly and can become unresponsive". The rest of the > description looks good to me. Thanks for the review, Roshni. To clarify: The first line of the description is converted to a title. It's used to summarize the issue. For example, you can see the result here: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.8_Release_Notes/known_issues_authentication_and_interoperability.html Therefore, I'll keep the line. It should look okay when published on the Customer Portal. |