problem with latest xterm
 

Hi,

there is a problem with the latest xterm (241).
it always complains about the bold font i want to load.
(misc-fixed 9x18 bold).
It seems it cant find it and tries to get another one, there are
two lines of the "cannot load font ...".
xterm starts and works, though. Seems it just overstrikes the normal
font instead of using the bold font. So this is not a showstopper but
a bit annoying and the feeling "something is wrong".
After trying the package I compiled it by myself (always do that to get rid of freetype and some stuff in xterm), but cant avoid this starting error.
urxvt and the xterm before (235 i think) are running just fine.

And, there is another X related thing, that i experienced from the
start:
if i start xfontsel or some other x tools, i hangs for a while
and complains "missing charset in string to font conversation".
No showstopper as well, but annoying.
Any suggestions? Thanks.

Hi grete!

Just to get our bearings - is this on Slackware? If so, how about some info on the install - full, custom, version, etc...

its custom slackware current.
xterm was upgraded:
"x/xterm-241-i486-1.tgz: Upgraded to xterm-241.
This fixes a vulnerability where displaying a file containing
DECRQSS (Device Control Request Status String) sequences could..." [snip]

xterm problem occured after that upgrade.
xterm 235 and urxvt are running fine without that error message.

xfontsel problem occured directly after fresh 12.2 custom install,
but i did'nt reported that at that time.
custom is, no kde and some stuff, but really everything important
and mandatory.

http://lists.freedesktop.org/mailman/listinfo/xorg is probably a better place to ask.
I don't actually use xterm and thus don't know enough about it to even begin troubleshooting it :/

font warnings
 

This is relevant -

(from the changelog entry for xterm #243)

improve warnings for unloadable fonts introduced in patch #240 by limiting those to the cases where a font would be specified directly by a resource setting rather than a derived fontname.

The problem was that Xorg split-off the fonts used by xterm (and other applications), requiring a fix to check if the fonts are really there. The first cut warned about some cases which aren't that interesting.