Hide Forgot
+++ This bug was initially created as a clone of Bug #1002126 +++ Description of problem: Normally disbaled input entries should be "grayed out". But it seems that they are actually painted in black (same color as the enabled widgets) on some terminals. This needs to be fixed to give th ecorretc visual feedback to the user.
Need to clone this bug from upstream into downstream to track this issue on rhev-h
Okay. The console only supports 8 colors. We could anyhow e.g. launch a terminal like fbterm which is opening a framebuffer and then allowing 256 colors. Also other terminals like xterm and gnome-terminal also support 256 colors, that's why this bug only appears on the console. We can - Switch to a terminal supporting 256 colors, like fbterm, but this might lead to hw problems - if there isn't a fb driver for the gfx hardware - unlikely, but possible - Hide disabled widgets completely - Choose a different color for disabled or for the active widgets Any opinions on one of these points or other ideas?
I think we make every attempt to stick to the 8 colors, even if it's not really clean looking. For the other terminals (ssh, etc), we can possibly use additional colors and make it look nicer.
Yes, good suggestion. The following patch fixes the issue at least for thr 8colors case (console). http://gerrit.ovirt.org/19706 We can improve it upstream to use more colors when available.
Test version: rhev-hypervisor6-6.5-20131017.0.iso ovirt-node-3.0.1-4.el6 Now Color of enabled input widgets was black and Color of disabled input widgets was red. so this bug has been fixed, change the status into "VERIFIED"
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0033.html