On Fri, Oct 28, 2022 at 03:49:52AM -0400, Thomas Dickey wrote: > On Fri, Oct 28, 2022 at 08:51:50AM +0200, Andreas Tille wrote: > > Package: xterm > > Version: 375-1 > > Severity: important > > > > Hi, > > > > after upgrading from xterm 374-1 to 375-1 I get: > > > > $ xterm > > xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" > > Segmentation fault > > > > I guess this local setting is relevant: > > > > $ grep font /etc/X11/Xresources/xterm | grep -v ^! > > *VT100.utf8Fonts.font: fixed > > XTerm.VT100.font1: -*-terminus-*-*-*-16-*-*-*-*-*-*-* > > XTerm.VT100.font2: -*-terminus-*-*-*-18-*-*-*-*-*-*-* > > > > XTerm.VT100.font3: -*-terminus-*-*-*-20-*-*-*-*-*-*-* > > > > XTerm.VT100.font4: -*-terminus-*-*-*-24-*-*-*-*-*-*-* > > XTerm.VT100.font5: -*-terminus-*-*-*-28-*-*-*-*-*-*-* > > > > XTerm.VT100.font6: -*-terminus-*-*-*-32-*-*-*-*-*-*-*
for the record, xfonts-terminus includes all of these sizes. > > here. If I uncomment these settings xterm starts. However, I think xterm > > should not > > Is that "uncomment", or "comment"? > > (the grep seems to indicate that the latter is meant) > > > crash with segmentation fault when not finding some specified font. > > agreed - I've not been able to reproduce the problem, which I suspect is in the error-recovery section of xterm's xtermLoadFont function. Perhaps seeing the whole set of resources would help (the output of "xrdb -query", too). -- Thomas E. Dickey <dic...@invisible-island.net> https://invisible-island.net ftp://ftp.invisible-island.net
signature.asc
Description: PGP signature
