Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1123027
| From | Thomas Dickey <dickey@his.com> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.maint.x |
| Subject | Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" |
| Date | 2022-10-30 22:10 +0100 |
| Message-ID | <FmnJ7-eBD-5@gated-at.bofh.it> (permalink) |
| References | <Flrvs-hfzK-3@gated-at.bofh.it> <FlsBb-hgpZ-5@gated-at.bofh.it> <Flrvs-hfzK-3@gated-at.bofh.it> <FlsBb-hgpZ-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
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 <dickey@invisible-island.net> https://invisible-island.net ftp://ftp.invisible-island.net
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" Andreas Tille <tille@debian.org> - 2022-10-28 09:00 +0200
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" Thomas Dickey <dickey@his.com> - 2022-10-28 10:10 +0200
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" Thomas Dickey <dickey@his.com> - 2022-10-30 22:10 +0100
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" Andreas Tille <andreas@an3as.eu> - 2022-11-01 09:30 +0100
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" Thomas Dickey <dickey@his.com> - 2022-11-07 02:10 +0100
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" Andreas Tille <andreas@an3as.eu> - 2022-11-12 15:30 +0100
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" Andreas Tille <tille@debian.org> - 2022-11-14 18:30 +0100
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" Andreas Tille <andreas@an3as.eu> - 2022-11-15 09:20 +0100
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" Andreas Tille <andreas@an3as.eu> - 2022-11-16 10:00 +0100
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" Andreas Tille <andreas@fam-tille.de> - 2022-11-17 06:40 +0100
csiph-web