Package: grace
Version: 1:5.1.25-6
Severity: important
Dear Maintainer,
When the latest ghostscript (9.27~dfsg-3) is installed, it forces the
installation of the fonts-urw-base35 package which contains binary font
files ending in a *.t1 instead of *.pfa or *.pfb. The grace package updates
its font mapping when new fonts are installed using the update-grace-fonts
script and all the fonts available are mapped in the file
/usr/share/grace/fonts/FontDataBase with links to the ascii and binary font
files in the /usr/share/grace/fonts/type1 directory.
When grace is started up, it reads the FontDataBase file and then searches
the /usr/share/grace/fonts/type1 directory for each of the fonts listed
there in one of three forms as per the strace output below
stat("/usr/share/grace/fonts/type1/n019023l", 0x7ffee1e43d70) = -1 ENOENT (No
such file or directory)
stat("/usr/share/grace/fonts/type1/n019023l.pfa", 0x7ffee1e43d70) = -1 ENOENT
(No such file or directory)
stat("/usr/share/grace/fonts/type1/n019023l.pfb", {st_dev=makedev(0x8, 0x1),
... }) = 0
Because the fonts in the fonts-urw-base35 have an extension of *.t1, they
are not recognized and grace does not handle this well at all because it
assigns that font name to the next binary font file with a valid extension.
This results in having only the fonts with binary files which end in no
extension, *.pfa or *.pfb being available but with names all scrambled up
and assigned to the unrecognized fonts.
If the links ending in *.t1 in the /usr/share/grace/fonts/type1/ directory
are renamed as *.pfb, then grace identifies all the fonts correctly and
makes them all available with their proper name designations. This
indicates that the bug is in the source code for grace which should add a
search for a fourth variant of the file name, i.e. with *.t1 as the
extension.
A second fix would be to have grace search only for the specific file name
that is listed in the third column of the FontdataBase file, which has the
correct file names associated with the fonts.
Either of the two above fixes would solve the bug correctly but a kludgy
solution would be to modify the update-grace-fonts script to rename the
links in the /usr/share/grace/fonts/type1/ directory which end in *.t1 as
having no extension of a *.pfb extension. However this is only a stopgap
solution.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages grace depends on:
ii fontconfig 2.13.1-2
ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.4
ii libc6 2.28-10
ii libfftw3-double3 3.3.8-2
ii libjpeg62-turbo 1:1.5.2-2+b1
ii libnetcdf13 1:4.6.2-1
ii libpng16-16 1.6.37-1
ii libx11-6 2:1.6.7-1
ii libxbae4m 4.60.4-7+b11
ii libxm4 2.3.8-2
ii libxmhtml1.1 1.1.10-3
ii libxmu6 2:1.1.2-2+b3
ii libxpm4 1:3.5.12-1
ii libxt6 1:1.1.5-1+b3
ii xterm 348-1
Versions of packages grace recommends:
ii xfonts-100dpi 1:1.0.4+nmu1
ii xfonts-75dpi 1:1.0.4+nmu1
Versions of packages grace suggests:
ii gconf2 3.2.6-5
hi ghostscript 9.27~dfsg-2
ii texlive-extra-utils 2019.20190710-1
-- no debconf information
