Red Hat Bugzilla – Bug 173374
xemacs is missing most icons, strange font with modular X
Last modified: 2007-11-30 17:11:17 EST
Description of problem:
xemacs starts up with a large font, and most icons in the toolbar are gone.
The cursor is invisible.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start xemacs from xterm
On the xterm:
Warning: Color name "black" is not defined
Warning: Color name "Blue" is not defined
Warning: Color name "Red" is not defined
Warning: Color name "Maroon" is not defined
Warning: Color name "ForestGreen" is not defined
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
In the *Warnings* buffer:
(1) (xim-lib/warning) Can't get fontset resource for Input Method
Ouch, I'm afraid fixing this is going to take a while unless someone submits
tested patches as I don't have a Rawhide box nor can I upgrade to one soon.
Anyway, first, being unable to resolve the color names smells like something's
trying to access /usr/X11R6/lib/X11/rgb.txt while it should be
trying /usr/lib/X11/rgb.txt. I grepped through the XEmacs source tree and it
does seem to be doing the right thing (through fallback lists), and the error
comes from a failing XLookupColor call in src/event-Xt.c. Could you try this
temporarily and see if it makes any difference?
# mkdir /usr/X11R6/lib/X11
# ln -s /usr/lib/X11/rgb.txt /usr/X11R6/lib/X11/
No change at all.
A few more comments: Fedora rawhide has modular X, this used to work yesterday
(before updating X).
I've just adapted neXtaw for modular X, and it (0.15.1-7.fc5) should appear in
the Extras devel repository in the next push. I doubt that it'll help much if
at all per se, but at least it could allow rebuilding XEmacs again (and it
would be interesting to hear if _that_ changes anything).
This should be significantly improved in 21.4.17-5.fc5 (and 6.fc5 coming up
soon). The edit area monospace font is still ugly though :(
Popup dialog font is still wrong too. See also bug 174617.
Things should be fixed in 21.4.17-7.fc5.