Bug 12293

Summary: Cannot install custom rgb.txt file in RHEL 5
Product: xorg Reporter: Isaac W. <ibwilsonvt92>
Component: Lib/XlibAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED NOTOURBUG QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium CC: agj
Version: 7.1 (2006.05)   
Hardware: x86 (IA32)   
OS: Linux (All)   
URL: https://bugzilla.redhat.com/show_bug.cgi?id=247483
Whiteboard:
i915 platform: i915 features:

Description Isaac W. 2007-09-05 13:30:48 UTC
Description of problem:
Cannot install a customized rgb.txt file because the /usr/share/X11/rgb.txt 
file is ignored by the X server.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 5 Server running Xorg 7.1.1

How reproducible:


Steps to Reproduce:
1.  Edit the rgb.txt file, changing the "Blue" and "blue" entries to "255 0 0".
2.  Start the X server.
3.  Create an xterm with the following command: "xterm -fg blue".
  
Actual results:
The xterm window appears with blue foreground text.

Expected results:
The xterm window should appear with red foreground text, since the rgb.txt was 
edited to associate the name "blue" with a red color "255 0 0".

Additional info:
No other copies of rgb.txt reside in the system.  Also, there were no errors in 
the /var/log/Xorg.0.log file.  RgbPath is set to "/usr/share/X11/rgb" in the 
xorg.conf file.
Comment 1 Adam Jackson 2008-02-24 17:53:22 UTC
rgb.txt is deprecated, sorry.  The default upstream is to build without support for it.

Your distribution may choose to do otherwise, of course, but that's not for X.org to enforce.
Comment 2 Aubrey Jaffer 2008-02-27 19:39:27 UTC
Is it color-from-name that is being deprecated by X.org or just the use of better color dictionaries (http://swiss.csail.mit.edu/~jaffer/Color/Dictionaries)?

I find no mention of rgb.txt in www.x.org/wiki/.  Is it discussed by X.org somewhere?

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.