Bug 1258394 - the light of Capslock key dose not work and dose not have any enlighten when tab the Capslock key
Summary: the light of Capslock key dose not work and dose not have any enlighten when ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 3.5.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Ryan Barry
QA Contact: chenche
URL:
Whiteboard: node
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-31 09:34 UTC by chenche
Modified: 2022-04-15 10:11 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-20 09:41:36 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-45681 0 None None None 2022-04-15 10:11:08 UTC

Description chenche 2015-08-31 09:34:01 UTC 
Description of problem:
the light of Capslock key dose not work and dose not have any enlighten when tab the Capslock key.

Version-Release number of selected component (if applicable):
rhev-hypervisor7-7.1-20150827.1.el7ev
ovirt-node-3.2.3-20.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1.Install rhev-hypervisor7-7.1-20150827.1.el7ev
2.in the TUI page,input the password and tab the CapsLock key.

Actual results:
After step2, the light of the Capsloak key dose not work and dose not have any enlighten in the page.

Expected results:
The light of the Capsloak which on the top of the keybroad will be shine when tap the Capsloak or have some enlighten words.

Additional info:
Comment 1 Fabian Deutsch 2015-09-01 09:59:19 UTC 
Is this only happening with RHEV-H?
Comment 2 chenche 2015-09-28 09:05:09 UTC 
(In reply to Fabian Deutsch from comment #1)
> Is this only happening with RHEV-H?

yes
Comment 3 Fabian Deutsch 2015-10-20 09:41:36 UTC 
The affected functionality will move to a different component in future where this bug does not apply anymore.
Note You need to log in before you can comment on or make changes to this bug.