Bug 1002357

Summary: Color of enabled and disabled input widgets doesn't differ
Product: Red Hat Enterprise Linux 6 Reporter: haiyang,dong <hadong>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.5CC: acathrow, bsarathy, cboyle, fdeutsch, gouyang, hadong, jboggs, leiwang, mburns, mgoldboi, ovirt-bugs, ovirt-maint, ycui, yeylon
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-3.0.1-3.el6 Doc Type: Bug Fix
Doc Text:
--no tech note required
Story Points: ---
Clone Of: 1002126 Environment:
Last Closed: 2014-01-21 19:49:10 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:
Bug Depends On: 1002126    
Bug Blocks:    

Description haiyang,dong 2013-08-29 02:05:29 UTC
+++ 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.

Comment 1 haiyang,dong 2013-08-29 02:07:01 UTC
Need to clone this bug from upstream into downstream to track this issue on rhev-h

Comment 3 Fabian Deutsch 2013-09-30 14:04:14 UTC
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?

Comment 4 Mike Burns 2013-09-30 18:58:23 UTC
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.

Comment 5 Fabian Deutsch 2013-09-30 19:48:45 UTC
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.

Comment 7 haiyang,dong 2013-10-21 07:47:49 UTC
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"

Comment 10 Cheryn Tan 2013-11-08 00:36:32 UTC
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.

Comment 12 errata-xmlrpc 2014-01-21 19:49:10 UTC
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