Red Hat Bugzilla – Bug 173428
emacs with modular X: 'Undefined color: "black"'
Last modified: 2007-11-30 17:11:17 EST
Description of problem:
Starting emacs just gives the above message, and emacs fails to start. There are
several other applications that complain about colors (like xemacs)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. try to start emacs in an xterm
emacs doesn't start, error message:
Undefined color: "black"
X team, any ideas about this one?
Is this because /usr/X11R6/lib/X11/rgb.txt moved, perhaps?
Maybe not - emacs seems to include its own rgb.txt fwiw.
This is most likely a dupe of bug #173036.
To everyone experiencing this:
Edit your xorg.conf file, and remove the line that has:
Then restart the X server. Does this make the problem go away? If so,
then I can have a real quick fix for this problem for everyone by having
the upgrade of the X server, remove RgbPath from xorg.conf, as it should
never have been put in there by our crazy config tools anyway. ;o)
Then the actual location of rgb.txt becomes transparent to the system
hopefully, and I can lower the priority of fixing it by a week or so,
and divert my resources to other more critical problems that have come
up, and either pick up a fix from RC3, or fix it in a few weeks.
Yes, this fixed it. xemacs alsso works now, and xclock (#173483) doesn't
complain about colors anymore.
CLOSED->DEFERED is not the correct bug state.
*** This bug has been marked as a duplicate of 173453 ***
*** Bug 173734 has been marked as a duplicate of this bug. ***
Hmm, even without RgbPath or after setting RgbPath, I still get
the 'Undefined color: "black"' message and emacs stops.
The fixed xorg-x11-server-utils package is in CVS right now, however
beehive will not let me build it, giving an error stating that
"xbitmaps-devel" is an unmet dependency.
Since xbitmaps-devel is a virtual provide of the xorg-x11-xbitmaps package,
and it does exist in dist-fc5, I hereby declare this problem to be blocking
on beehive being broken.
Once beehive is un-broken, and permits the package to be built, we'll be
one step closer to solving the rgb.txt related problems however.
See comment 2 of Bug 173734. If there's no RgbPath, /usr/lib/X11/rgb.txt will