Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
Am Wed, Nov 16, 2022 at 08:23:58PM -0500 schrieb Thomas Dickey: > never mind - I see the problem now (was thinking that it occurred when > the font _was_ installed). Will upload #376 in the early morning. Cool. Thanks a lot Andreas. -- http://fam-tille.de
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Wed, Nov 16, 2022 at 04:02:18AM -0500, Thomas Dickey wrote: > On Wed, Nov 16, 2022 at 09:50:36AM +0100, Andreas Tille wrote: > > Control: severity -1 minor ... > > After restarting X xterm is starting properly now. It somehow seems > > that the mkfontdir call changed the game. Unfortunately we do not > > really know what might have caused the issue. As I said I would also > > have loved if xterm would not have crashed. > > agreed (I did try reproducing the crash for the case where the font > was missing, but so far unsuccessful). never mind - I see the problem now (was thinking that it occurred when the font _was_ installed). Will upload #376 in the early morning. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Wed, Nov 16, 2022 at 09:50:36AM +0100, Andreas Tille wrote: > Control: severity -1 minor > > Hi Thomas, > > at first thanks a lot for your patience. > > Am Tue, Nov 15, 2022 at 08:10:18PM -0500 schrieb Thomas Dickey: > > On Tue, Nov 15, 2022 at 09:15:43AM +0100, Andreas Tille wrote: > > > Hi again, > > > > > > I need to admit that the issue "vanished" on my workhorse laptop which is > > > nice on one hand but having an explanation would be even nicer. ;-) > > > I've now tried the other laptop with the same problem: > > > > > > $ dpkg --get-selections | grep terminus > > > fonts-terminusinstall > > > $ xlsfonts | grep terminus > > > > That might be one of these possibilities: > > > > a) the X configuration (seen with "xset -q") has something amiss with > >the fontpath (see attached example from my Debian/testing). > > There was no attachment but here is mine: sorry - will do that, for the record > $ xset -q > Keyboard Control: > auto repeat: onkey click percent: 0LED mask: > XKB indicators: > 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off > 03: Compose: off04: Kana:off05: Sleep: off > 06: Suspend: off07: Mute:off08: Misc:off > 09: Mail:off10: Charging:off11: Shift Lock: off > 12: Group 2: off13: Mouse Keys: off > auto repeat delay: 400repeat rate: 20 > auto repeating keys: 00ffdbbf > fedfffefffed > 9fff > fff7 > bell percent: 50bell pitch: 400bell duration: 100 > Pointer Control: > acceleration: 2/1threshold: 4 > Screen Saver: > prefer blanking: yesallow exposures: yes > timeout: 180cycle: 600 > Colors: > default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff > Font Path: > > /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,built-ins > DPMS (Energy Star): > Standby: 0Suspend: 300Off: 600 > DPMS is Enabled > Monitor is On > > > > b) updates to the bitmap font-directories have to be finished using > >mkfontdir (part of xfonts-utils). I've seen occasional comments > >where package updates didn't work as intended. > > > > Either way, "dpkg -L xfonts-terminus" tells me that the relevant files > > are in > > > > /usr/share/fonts/X11/misc > > > > If xset reports that's in the font path, I'd try (based on the manpage) > > > > sudo mkfontdir /usr/share/fonts/X11/misc > > Done. > > > or (by habit, since long ago it ignored the parameter...) > > > > cd /usr/share/fonts/X11/misc > > sudo mkfontdir > > > > and restart X. > > After restarting X xterm is starting properly now. It somehow seems > that the mkfontdir call changed the game. Unfortunately we do not > really know what might have caused the issue. As I said I would also > have loved if xterm would not have crashed. agreed (I did try reproducing the crash for the case where the font was missing, but so far unsuccessful). > In any case I consider the severity of the bug as lower now and have > set it to minor. I'll leave it to your decision whether you consider > it closed or some helpful resource to find a way to avoid the issue. > > Kind regards and thanks again for your help >Andreas. > > -- > http://fam-tille.de > -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net Keyboard Control: auto repeat: onkey click percent: 0LED mask: 0002 XKB indicators: 00: Caps Lock: off01: Num Lock:on 02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 600cycle: 600 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,built-ins DPMS (Energy Star): Standby: 600Suspend: 0Off: 900 DPMS is Enabled Monitor is On signature.asc Description: PGP signature
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
Control: severity -1 minor Hi Thomas, at first thanks a lot for your patience. Am Tue, Nov 15, 2022 at 08:10:18PM -0500 schrieb Thomas Dickey: > On Tue, Nov 15, 2022 at 09:15:43AM +0100, Andreas Tille wrote: > > Hi again, > > > > I need to admit that the issue "vanished" on my workhorse laptop which is > > nice on one hand but having an explanation would be even nicer. ;-) > > I've now tried the other laptop with the same problem: > > > > $ dpkg --get-selections | grep terminus > > fonts-terminus install > > $ xlsfonts | grep terminus > > That might be one of these possibilities: > > a) the X configuration (seen with "xset -q") has something amiss with >the fontpath (see attached example from my Debian/testing). There was no attachment but here is mine: $ xset -q Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 400repeat rate: 20 auto repeating keys: 00ffdbbf fedfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 180cycle: 600 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 300Off: 600 DPMS is Enabled Monitor is On > b) updates to the bitmap font-directories have to be finished using >mkfontdir (part of xfonts-utils). I've seen occasional comments >where package updates didn't work as intended. > > Either way, "dpkg -L xfonts-terminus" tells me that the relevant files > are in > > /usr/share/fonts/X11/misc > > If xset reports that's in the font path, I'd try (based on the manpage) > > sudo mkfontdir /usr/share/fonts/X11/misc Done. > or (by habit, since long ago it ignored the parameter...) > > cd /usr/share/fonts/X11/misc > sudo mkfontdir > > and restart X. After restarting X xterm is starting properly now. It somehow seems that the mkfontdir call changed the game. Unfortunately we do not really know what might have caused the issue. As I said I would also have loved if xterm would not have crashed. In any case I consider the severity of the bug as lower now and have set it to minor. I'll leave it to your decision whether you consider it closed or some helpful resource to find a way to avoid the issue. Kind regards and thanks again for your help Andreas. -- http://fam-tille.de
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Tue, Nov 15, 2022 at 09:15:43AM +0100, Andreas Tille wrote: > Hi again, > > I need to admit that the issue "vanished" on my workhorse laptop which is > nice on one hand but having an explanation would be even nicer. ;-) > I've now tried the other laptop with the same problem: > > $ dpkg --get-selections | grep terminus > fonts-terminusinstall > $ xlsfonts | grep terminus That might be one of these possibilities: a) the X configuration (seen with "xset -q") has something amiss with the fontpath (see attached example from my Debian/testing). b) updates to the bitmap font-directories have to be finished using mkfontdir (part of xfonts-utils). I've seen occasional comments where package updates didn't work as intended. Either way, "dpkg -L xfonts-terminus" tells me that the relevant files are in /usr/share/fonts/X11/misc If xset reports that's in the font path, I'd try (based on the manpage) sudo mkfontdir /usr/share/fonts/X11/misc or (by habit, since long ago it ignored the parameter...) cd /usr/share/fonts/X11/misc sudo mkfontdir and restart X. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
Hi again, I need to admit that the issue "vanished" on my workhorse laptop which is nice on one hand but having an explanation would be even nicer. ;-) I've now tried the other laptop with the same problem: $ dpkg --get-selections | grep terminus fonts-terminus install $ xlsfonts | grep terminus Exit code: 1 $ xfd -fa terminus-32 ---> created a graphical display with the terminus font $ xterm -fa terminus-32 Speicherzugriffsfehler Exit code: 139 Kind regards Andreas. -- http://fam-tille.de
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Mon, Nov 14, 2022 at 06:21:50PM +0100, Andreas Tille wrote: > Am Mon, Nov 14, 2022 at 04:27:30AM -0500 schrieb Thomas Dickey: > > > Since xterm is crashing before this does not report anything > > > interesting. > > > > hmm - it's not showing much. > > > > What does xfd do with that pattern? (using single quotes): > > > > xfd -fn '-*-terminus-*-*-*-32-*-*-*-*-*-*-*' > > > > If you don't have that installed, it's part of x11-utils: /usr/bin/xfd > > > > (reinstalling the font might be helpful) > > OK > > ~$ sudo apt install fonts-terminus > Paketlisten werden gelesen… Fertig > Abhängigkeitsbaum wird aufgebaut… Fertig > Statusinformationen werden eingelesen… Fertig > Die folgenden NEUEN Pakete werden installiert: > fonts-terminus > 0 aktualisiert, 1 neu installiert, 0 zu entfernen und 2 nicht aktualisiert. > Es müssen 81,0 kB an Archiven heruntergeladen werden. > Nach dieser Operation werden 464 kB Plattenplatz zusätzlich benutzt. > Holen:1 http://deb.debian.org/debian testing/main amd64 fonts-terminus amd64 > 1.2.0+ds-7 [81,0 kB] > Es wurden 81,0 kB in 0 s geholt (596 kB/s). > Vormals nicht ausgewähltes Paket fonts-terminus wird gewählt. > (Lese Datenbank ... 417804 Dateien und Verzeichnisse sind derzeit > installiert.) > Vorbereitung zum Entpacken von .../fonts-terminus_1.2.0+ds-7_amd64.deb ... > Entpacken von fonts-terminus (1.2.0+ds-7) ... > fonts-terminus (1.2.0+ds-7) wird eingerichtet ... > Trigger für fontconfig (2.13.1-4.5) werden verarbeitet ... > ~$ xfd -fn '-*-terminus-*-*-*-32-*-*-*-*-*-*-*' > Warning: Cannot convert string "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" to type > FontStruct > xfd: no font to display That's (sort of) promising - it tells me that it's not a bug in _xterm_. xterm and xfd use the same font-related libraries. It could still be a configuration problem -- I seem to recall seeing cases where mkfontdir wasn't run on font updates. xlsfonts should show the terminus fonts in its (usually long) output. For instance, on my Debian/oldstable, I get 494 lines from xlsfonts | grep terminus (including an alias "terminus-32"). xlsfonts doesn't use any of those font-related libraries, talks directly to the X server. The Xlib calls that xterm uses for bitmap fonts (e.g., Terminus) should use the same information. If you were using a TrueType font, xterm and xfd would use the Xft and fontconfig libraries (the "font-related" libraries that I mentioned). xterm and xfd if using "-fa" (rather than "-fn") will ask fontconfig for the font, and it does know enough to do that, e.g., xfd -fa terminus-32 xterm -fa terminus-32 -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
Am Mon, Nov 14, 2022 at 04:27:30AM -0500 schrieb Thomas Dickey: > > Since xterm is crashing before this does not report anything > > interesting. > > hmm - it's not showing much. > > What does xfd do with that pattern? (using single quotes): > > xfd -fn '-*-terminus-*-*-*-32-*-*-*-*-*-*-*' > > If you don't have that installed, it's part of x11-utils: /usr/bin/xfd > > (reinstalling the font might be helpful) OK ~$ sudo apt install fonts-terminus Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Die folgenden NEUEN Pakete werden installiert: fonts-terminus 0 aktualisiert, 1 neu installiert, 0 zu entfernen und 2 nicht aktualisiert. Es müssen 81,0 kB an Archiven heruntergeladen werden. Nach dieser Operation werden 464 kB Plattenplatz zusätzlich benutzt. Holen:1 http://deb.debian.org/debian testing/main amd64 fonts-terminus amd64 1.2.0+ds-7 [81,0 kB] Es wurden 81,0 kB in 0 s geholt (596 kB/s). Vormals nicht ausgewähltes Paket fonts-terminus wird gewählt. (Lese Datenbank ... 417804 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../fonts-terminus_1.2.0+ds-7_amd64.deb ... Entpacken von fonts-terminus (1.2.0+ds-7) ... fonts-terminus (1.2.0+ds-7) wird eingerichtet ... Trigger für fontconfig (2.13.1-4.5) werden verarbeitet ... ~$ xfd -fn '-*-terminus-*-*-*-32-*-*-*-*-*-*-*' Warning: Cannot convert string "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" to type FontStruct xfd: no font to display Exit code: 1 ~$ xterm xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*" Speicherzugriffsfehler Exit code: 139 Anything else I could try? Kind regards Andreas. -- http://fam-tille.de
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Mon, Nov 14, 2022 at 09:02:22AM +0100, Andreas Tille wrote: > Am Sun, Nov 13, 2022 at 08:33:09PM -0500 schrieb Thomas Dickey: > > > LANGUAGE= > > > LC_CTYPE="de_DE.UTF-8" > > > LC_NUMERIC="de_DE.UTF-8" > > > LC_TIME="de_DE.UTF-8" > > > LC_COLLATE="de_DE.UTF-8" > > > LC_MONETARY="de_DE.UTF-8" > > > LC_MESSAGES="de_DE.UTF-8" > > > LC_PAPER="de_DE.UTF-8" > > > LC_NAME="de_DE.UTF-8" > > > LC_ADDRESS="de_DE.UTF-8" > > > LC_TELEPHONE="de_DE.UTF-8" > > > LC_MEASUREMENT="de_DE.UTF-8" > > > LC_IDENTIFICATION="de_DE.UTF-8" > > > LC_ALL= > > > > I tried that - no change > > I admit I do not think the locale setting is responsible for the issue. > > > > I've made the Geometry that size to fit exactly a quarter of my screen > > > fitting 4 xterms at one time. Xfce4 places these intelligently in a > > > 2x2 matrix. > > > > Something like this will work, but fixing the problem with the menus: > > > > XTerm*VT100.geometry: 111x36 > > > > It's in the FAQ: > > > > https://invisible-island.net/xterm/xterm.faq.html#tiny_menus > > Thanks for the hint but I think this was not my main problem. ;-) > > > > I'm using Debian packages exclusively - I have no time to spent > > > extra fancy things. BTW. I'm observing the very same bug on my > > > second laptop I'm using for traveling (but my desktop with the > > > same setup works without any problem) > > > > > > Could you send me the full command line > > >"xrdb -load ??" > > > > I pasted the text from earlier mail as "bad.ad" (attached), > > and loaded it with > > > > xrdb -load bad.ad > > I tried this but it did not changed the problem. > > > > I could check here. What strace call should I send to track > > > down the issue. Please note that while I'm an experienced > > > > I'd just > > > > strace -o trace.log -s 1024 xterm > > > > to capture a long trace (~200kb), > > and look to see if there's something interesting where xterm dies. > > I've attached my gziped trace.log. > > > I also ran xterm using -report-fonts, which shows the fonts opened. > > Since xterm is crashing before this does not report anything > interesting. hmm - it's not showing much. What does xfd do with that pattern? (using single quotes): xfd -fn '-*-terminus-*-*-*-32-*-*-*-*-*-*-*' If you don't have that installed, it's part of x11-utils: /usr/bin/xfd (reinstalling the font might be helpful) -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
Am Sun, Nov 13, 2022 at 08:33:09PM -0500 schrieb Thomas Dickey: > > LANGUAGE= > > LC_CTYPE="de_DE.UTF-8" > > LC_NUMERIC="de_DE.UTF-8" > > LC_TIME="de_DE.UTF-8" > > LC_COLLATE="de_DE.UTF-8" > > LC_MONETARY="de_DE.UTF-8" > > LC_MESSAGES="de_DE.UTF-8" > > LC_PAPER="de_DE.UTF-8" > > LC_NAME="de_DE.UTF-8" > > LC_ADDRESS="de_DE.UTF-8" > > LC_TELEPHONE="de_DE.UTF-8" > > LC_MEASUREMENT="de_DE.UTF-8" > > LC_IDENTIFICATION="de_DE.UTF-8" > > LC_ALL= > > I tried that - no change I admit I do not think the locale setting is responsible for the issue. > > I've made the Geometry that size to fit exactly a quarter of my screen > > fitting 4 xterms at one time. Xfce4 places these intelligently in a > > 2x2 matrix. > > Something like this will work, but fixing the problem with the menus: > > XTerm*VT100.geometry: 111x36 > > It's in the FAQ: > > https://invisible-island.net/xterm/xterm.faq.html#tiny_menus Thanks for the hint but I think this was not my main problem. ;-) > > I'm using Debian packages exclusively - I have no time to spent > > extra fancy things. BTW. I'm observing the very same bug on my > > second laptop I'm using for traveling (but my desktop with the > > same setup works without any problem) > > > > Could you send me the full command line > >"xrdb -load ??" > > I pasted the text from earlier mail as "bad.ad" (attached), > and loaded it with > > xrdb -load bad.ad I tried this but it did not changed the problem. > > I could check here. What strace call should I send to track > > down the issue. Please note that while I'm an experienced > > I'd just > > strace -o trace.log -s 1024 xterm > > to capture a long trace (~200kb), > and look to see if there's something interesting where xterm dies. I've attached my gziped trace.log. > I also ran xterm using -report-fonts, which shows the fonts opened. Since xterm is crashing before this does not report anything interesting. Kind regards Andreas. -- http://fam-tille.de trace.log.gz Description: application/gzip
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Sat, Nov 12, 2022 at 03:17:01PM +0100, Andreas Tille wrote: > Am Sun, Nov 06, 2022 at 07:55:33PM -0500 schrieb Thomas Dickey: > > On Tue, Nov 01, 2022 at 09:23:55AM +0100, Andreas Tille wrote: > > > Am Sun, Oct 30, 2022 at 04:53:24PM -0400 schrieb Thomas Dickey: > > > > > > $ grep font /etc/X11/Xresources/xterm | grep -v ^! > > > > > > *VT100.utf8Fonts.font: fixed > > > > what locale settings are you using? > > > > (that might be relevant - or the choice of desktop/window-manager) > > $ locale > LANG=de_DE.UTF-8 > LANGUAGE= > LC_CTYPE="de_DE.UTF-8" > LC_NUMERIC="de_DE.UTF-8" > LC_TIME="de_DE.UTF-8" > LC_COLLATE="de_DE.UTF-8" > LC_MONETARY="de_DE.UTF-8" > LC_MESSAGES="de_DE.UTF-8" > LC_PAPER="de_DE.UTF-8" > LC_NAME="de_DE.UTF-8" > LC_ADDRESS="de_DE.UTF-8" > LC_TELEPHONE="de_DE.UTF-8" > LC_MEASUREMENT="de_DE.UTF-8" > LC_IDENTIFICATION="de_DE.UTF-8" > LC_ALL= I tried that - no change > Desktop environment is xfce4. > > > > Sorry its "comment". > > > > > > > > (the grep seems to indicate that the latter is meant) > > > > > > > > > > > crash with segmentation fault when not finding some specified font. > > > > I suppose the problem is something along the lines of the X server > > returning some error in using the fonts. If it were TrueType fonts, > > I'd use strace to verify that they're opened -- but for bitmap > > fonts, that's done on the server side. > > I admit I'm fine with any nicely readable font. I once considered the > terminus fonts to fit this requirement and never found any reason > to change this. > > > > The crash happens for > > > > > > $ xrdb -query > > > *VT100.utf8Fonts.font: fixed > > > XTermVT100.faceSize:22 > > > XTerm*geometry: 111x36 > > > > hmm - I'm still not seeing _this_ problem. > > (by the way, the geometry resource is over-broad, making the font-menu > > less than useful). > > I've made the Geometry that size to fit exactly a quarter of my screen > fitting 4 xterms at one time. Xfce4 places these intelligently in a > 2x2 matrix. Something like this will work, but fixing the problem with the menus: XTerm*VT100.geometry: 111x36 It's in the FAQ: https://invisible-island.net/xterm/xterm.faq.html#tiny_menus > > I used xcfe4 for testing, on a virtual machine. > > > > My most recent snapshot (from 2022/11/01) didn't work - some problem > > with X and the window manaager), so I upgraded from 2022/10/29, > > to get a workable machine. > > > > Given that (I also have the terminus font installed), > > I used "xrdb -load" with these resources, and ran xterm > > from the Debian package. It looks okay to me - no crash. > > I'm using Debian packages exclusively - I have no time to spent > extra fancy things. BTW. I'm observing the very same bug on my > second laptop I'm using for traveling (but my desktop with the > same setup works without any problem) > > Could you send me the full command line >"xrdb -load ??" I pasted the text from earlier mail as "bad.ad" (attached), and loaded it with xrdb -load bad.ad > I could check here. What strace call should I send to track > down the issue. Please note that while I'm an experienced I'd just strace -o trace.log -s 1024 xterm to capture a long trace (~200kb), and look to see if there's something interesting where xterm dies. I also ran xterm using -report-fonts, which shows the fonts opened. > Debian user and long year developer I would not consider myself > an X expert. > > Kind regards > >Andreas. > > -- > http://fam-tille.de -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net Loaded VTFonts(font6) fNorm: -*-terminus-*-*-*-32-*-*-*-*-*-*-* all chars: no default char: 63 direction: 0 ascent:26 descent: 6 first char:0 last char: 255 maximum-chars: 256 missing-chars: 37 present-chars: 219 min_byte1: 0 max_byte1: 0 properties:22 min_bounds: lbearing: 0 rbearing: 0 width:16 ascent: -1 descent: -22 max_bounds: lbearing: 6 rbearing: 16 width:16 ascent: 26 descent: 6 fBold: -xos4-Terminus-bold-R-*-*-32-320-72-72-C-160-ISO8859-1 all chars: no default char: 63 direction: 0 ascent:26 descent: 6 first char:0 last char: 255 maximum-chars: 256 missing-chars: 37 present-chars: 219 min_byte1: 0
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
Am Sun, Nov 06, 2022 at 07:55:33PM -0500 schrieb Thomas Dickey: > On Tue, Nov 01, 2022 at 09:23:55AM +0100, Andreas Tille wrote: > > Am Sun, Oct 30, 2022 at 04:53:24PM -0400 schrieb Thomas Dickey: > > > > > $ grep font /etc/X11/Xresources/xterm | grep -v ^! > > > > > *VT100.utf8Fonts.font: fixed > > what locale settings are you using? > > (that might be relevant - or the choice of desktop/window-manager) $ locale LANG=de_DE.UTF-8 LANGUAGE= LC_CTYPE="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= Desktop environment is xfce4. > > Sorry its "comment". > > > > > > (the grep seems to indicate that the latter is meant) > > > > > > > > > crash with segmentation fault when not finding some specified font. > > I suppose the problem is something along the lines of the X server > returning some error in using the fonts. If it were TrueType fonts, > I'd use strace to verify that they're opened -- but for bitmap > fonts, that's done on the server side. I admit I'm fine with any nicely readable font. I once considered the terminus fonts to fit this requirement and never found any reason to change this. > > The crash happens for > > > > $ xrdb -query > > *VT100.utf8Fonts.font: fixed > > XTermVT100.faceSize:22 > > XTerm*geometry: 111x36 > > hmm - I'm still not seeing _this_ problem. > (by the way, the geometry resource is over-broad, making the font-menu > less than useful). I've made the Geometry that size to fit exactly a quarter of my screen fitting 4 xterms at one time. Xfce4 places these intelligently in a 2x2 matrix. > I used xcfe4 for testing, on a virtual machine. > > My most recent snapshot (from 2022/11/01) didn't work - some problem > with X and the window manaager), so I upgraded from 2022/10/29, > to get a workable machine. > > Given that (I also have the terminus font installed), > I used "xrdb -load" with these resources, and ran xterm > from the Debian package. It looks okay to me - no crash. I'm using Debian packages exclusively - I have no time to spent extra fancy things. BTW. I'm observing the very same bug on my second laptop I'm using for traveling (but my desktop with the same setup works without any problem) Could you send me the full command line "xrdb -load ??" I could check here. What strace call should I send to track down the issue. Please note that while I'm an experienced Debian user and long year developer I would not consider myself an X expert. Kind regards Andreas. -- http://fam-tille.de
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
On Tue, Nov 01, 2022 at 09:23:55AM +0100, Andreas Tille wrote: > Am Sun, Oct 30, 2022 at 04:53:24PM -0400 schrieb Thomas Dickey: > > > > $ grep font /etc/X11/Xresources/xterm | grep -v ^! > > > > *VT100.utf8Fonts.font: fixed what locale settings are you using? (that might be relevant - or the choice of desktop/window-manager) > > > > 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"? > > Sorry its "comment". > > > > (the grep seems to indicate that the latter is meant) > > > > > > > crash with segmentation fault when not finding some specified font. I suppose the problem is something along the lines of the X server returning some error in using the fonts. If it were TrueType fonts, I'd use strace to verify that they're opened -- but for bitmap fonts, that's done on the server side. > > > > > > 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). > > I have: > > $ xrdb -query > *VT100.utf8Fonts.font: fixed > XTermVT100.faceSize:22 > XTerm*geometry: 111x36 > xterm*vt100.initialFont:6 > YTerm*geometry: 90x50 > xterm*visualBell: true > Rxvt.keysym.Delete: \b > Rxvt.termName: xterm > XTerm*decTerminalID:200 > XTerm*color0: black > XTerm*color1: red > XTerm*color2: green > XTerm*color3: yellow > XTerm*color4: blue > XTerm*color5: magenta > XTerm*color6: cyan > XTerm*color7: white > XTerm*color8: black > XTerm*color9: red > XTerm*color10: green > XTerm*color11: yellow > XTerm*color12: blue > XTerm*color13: magenta > XTerm*color14: cyan > XTerm*color15: white > XTerm*termName: xterm > XTerm*title:XTerm > XTerm*colorMode:on > XTerm*background: blue > XTerm*foreground: white > XTerm*loginShell: true > XTerm*dynamicColors:on > > > The crash happens for > > $ xrdb -query > *VT100.utf8Fonts.font: fixed > XTermVT100.faceSize:22 > XTerm*geometry: 111x36 hmm - I'm still not seeing _this_ problem. (by the way, the geometry resource is over-broad, making the font-menu less than useful). I used xcfe4 for testing, on a virtual machine. My most recent snapshot (from 2022/11/01) didn't work - some problem with X and the window manaager), so I upgraded from 2022/10/29, to get a workable machine. Given that (I also have the terminus font installed), I used "xrdb -load" with these resources, and ran xterm from the Debian package. It looks okay to me - no crash. > 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-*-*-*-*-*-*-* > xterm*vt100.initialFont:6 > YTerm*geometry: 90x50 > xterm*visualBell: true > Rxvt.keysym.Delete: \b > Rxvt.termName: xterm > XTerm*decTerminalID:200 > XTerm*color0: black > XTerm*color1: red > XTerm*color2: green > XTerm*color3: yellow > XTerm*color4: blue > XTerm*color5: magenta > XTerm*color6: cyan > XTerm*color7: white > XTerm*color8: black > XTerm*color9: red > XTerm*color10: green > XTerm*color11: yellow > XTerm*color12: blue > XTerm*color13: magenta > XTerm*color14: cyan > XTerm*color15: white > XTerm*termName: xterm > XTerm*title:XTerm > XTerm*colorMode:on > XTerm*background: blue > XTerm*foreground: white > XTerm*loginShell: true > XTerm*dynamicColors:on > > > I confirm I have installed xfonts-terminus > > $ apt policy xfonts-terminus > xfonts-terminus: > Installiert: 4.48-3.1 > Installationskandidat: 4.48-3.1 > Versionstabelle: > *** 4.48-3.1 500 > 500 http://deb.debian.org/debian testing/main amd64 Packages > 500 http://deb.debian.org/debian unstable/main amd64 Packages > 500 http://ftp.debian.org/debian unstable/main amd64 Packages > 100 /var/lib/dpkg/status > > Kind regards > >Andreas. > > -- > http://fam-tille.de -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
Am Sun, Oct 30, 2022 at 04:53:24PM -0400 schrieb Thomas Dickey: > > > $ 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"? Sorry its "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). I have: $ xrdb -query *VT100.utf8Fonts.font: fixed XTermVT100.faceSize:22 XTerm*geometry: 111x36 xterm*vt100.initialFont:6 YTerm*geometry: 90x50 xterm*visualBell: true Rxvt.keysym.Delete: \b Rxvt.termName: xterm XTerm*decTerminalID:200 XTerm*color0: black XTerm*color1: red XTerm*color2: green XTerm*color3: yellow XTerm*color4: blue XTerm*color5: magenta XTerm*color6: cyan XTerm*color7: white XTerm*color8: black XTerm*color9: red XTerm*color10: green XTerm*color11: yellow XTerm*color12: blue XTerm*color13: magenta XTerm*color14: cyan XTerm*color15: white XTerm*termName: xterm XTerm*title:XTerm XTerm*colorMode:on XTerm*background: blue XTerm*foreground: white XTerm*loginShell: true XTerm*dynamicColors:on The crash happens for $ xrdb -query *VT100.utf8Fonts.font: fixed XTermVT100.faceSize:22 XTerm*geometry: 111x36 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-*-*-*-*-*-*-* xterm*vt100.initialFont:6 YTerm*geometry: 90x50 xterm*visualBell: true Rxvt.keysym.Delete: \b Rxvt.termName: xterm XTerm*decTerminalID:200 XTerm*color0: black XTerm*color1: red XTerm*color2: green XTerm*color3: yellow XTerm*color4: blue XTerm*color5: magenta XTerm*color6: cyan XTerm*color7: white XTerm*color8: black XTerm*color9: red XTerm*color10: green XTerm*color11: yellow XTerm*color12: blue XTerm*color13: magenta XTerm*color14: cyan XTerm*color15: white XTerm*termName: xterm XTerm*title:XTerm XTerm*colorMode:on XTerm*background: blue XTerm*foreground: white XTerm*loginShell: true XTerm*dynamicColors:on I confirm I have installed xfonts-terminus $ apt policy xfonts-terminus xfonts-terminus: Installiert: 4.48-3.1 Installationskandidat: 4.48-3.1 Versionstabelle: *** 4.48-3.1 500 500 http://deb.debian.org/debian testing/main amd64 Packages 500 http://deb.debian.org/debian unstable/main amd64 Packages 500 http://ftp.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status Kind regards Andreas. -- http://fam-tille.de
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
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 https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
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-*-*-*-*-*-*-* > > 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 - > Kind regards > Andreas. > > > -- System Information: > Debian Release: bookworm/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), > (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages xterm depends on: > ii libc6 2.35-4 > ii libfontconfig1 2.13.1-4.5 > ii libfreetype62.12.1+dfsg-3 > ii libice6 2:1.0.10-1 > ii libtinfo6 6.3+20220423-2 > ii libutempter01.2.1-2 > ii libx11-62:1.8.1-2 > ii libxaw7 2:1.0.14-1 > ii libxext62:1.3.4-1+b1 > ii libxft2 2.3.6-1 > ii libxinerama12:1.1.4-3 > ii libxmu6 2:1.1.3-3 > ii libxpm4 1:3.5.12-1 > ii libxt6 1:1.2.1-1 > ii xbitmaps1.1.1-2.2 > > Versions of packages xterm recommends: > ii x11-utils 7.7+5 > > Versions of packages xterm suggests: > pn xfonts-cyrillic > > -- no debconf information > -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Bug#1022942: xterm: cannot load font "-*-terminus-*-*-*-32-*-*-*-*-*-*-*"
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-*-*-*-*-*-*-* here. If I uncomment these settings xterm starts. However, I think xterm should not crash with segmentation fault when not finding some specified font. Kind regards Andreas. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xterm depends on: ii libc6 2.35-4 ii libfontconfig1 2.13.1-4.5 ii libfreetype62.12.1+dfsg-3 ii libice6 2:1.0.10-1 ii libtinfo6 6.3+20220423-2 ii libutempter01.2.1-2 ii libx11-62:1.8.1-2 ii libxaw7 2:1.0.14-1 ii libxext62:1.3.4-1+b1 ii libxft2 2.3.6-1 ii libxinerama12:1.1.4-3 ii libxmu6 2:1.1.3-3 ii libxpm4 1:3.5.12-1 ii libxt6 1:1.2.1-1 ii xbitmaps1.1.1-2.2 Versions of packages xterm recommends: ii x11-utils 7.7+5 Versions of packages xterm suggests: pn xfonts-cyrillic -- no debconf information
