Bug 1002357 - Color of enabled and disabled input widgets doesn't differ
Color of enabled and disabled input widgets doesn't differ
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node (Show other bugs)
Unspecified Unspecified
medium Severity medium
: rc
: ---
Assigned To: Fabian Deutsch
Virtualization Bugs
Depends On: 1002126
  Show dependency treegraph
Reported: 2013-08-28 22:05 EDT by haiyang,dong
Modified: 2014-01-21 14:49 EST (History)
14 users (show)

See Also:
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
Last Closed: 2014-01-21 14:49:10 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 19706 None None None Never

  None (edit)
Description haiyang,dong 2013-08-28 22:05:29 EDT
+++ 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-28 22:07:01 EDT
Need to clone this bug from upstream into downstream to track this issue on rhev-h
Comment 3 Fabian Deutsch 2013-09-30 10:04:14 EDT
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 14:58:23 EDT
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 15:48:45 EDT
Yes, good suggestion.

The following patch fixes the issue at least for thr 8colors case (console).


We can improve it upstream to use more colors when available.
Comment 7 haiyang,dong 2013-10-21 03:47:49 EDT
Test version:

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-07 19:36:32 EST
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:


Thanks in advance.
Comment 12 errata-xmlrpc 2014-01-21 14:49:10 EST
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.


Note You need to log in before you can comment on or make changes to this bug.