SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.