Bug 57996 - gnome-terminal color browser fights back
Summary: gnome-terminal color browser fights back
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-core   
(Show other bugs)
Version: 7.2
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact: Aaron Brown
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-01-04 17:26 UTC by Joe Harrington
Modified: 2007-04-18 16:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-01-18 23:01:11 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Joe Harrington 2002-01-04 17:26:45 UTC
In the color browser under preferences/colors, it sometimes takes
several attempts to get the requested color to "appear" in the
foreground/background color entries, *and* several successful attempts
to get them to appear in the terminal when "apply" is clicked.  This
is on a 16-bit display.

gnome-core-1.4.0.4-38 under 7.2 i386 with all updates

--jh--

Comment 1 Havoc Pennington 2002-01-18 23:01:05 UTC
Very strange, will look.

Comment 2 Havoc Pennington 2002-02-26 16:48:48 UTC
I haven't been able to reproduce this or gotten other reports of it.

Note that the color selector is kind of hard to use, it's been revamped in GTK 2.
It's easy to leave it stuck on black or white in GTK 1.2, when you thought 
you selected a color.

At this point only release-critical showstoppers are going in to the GNOME 1.x
packages, so deferring a lot of bugs to GNOME 2.

Comment 3 Joe Harrington 2002-02-26 16:57:44 UTC
Ah!  This makes sense.  My foreground and background colors are black and white,
respectively.  Hope this is fixed in the new version.  Hope RH releases it as an
update if a regular OS release is more than a month away...

--jh--



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