fonts-bugs October 2021

fonts-bugs@lists.fedoraproject.org

3 participants
55 discussions

[Bug 1925922] New: dependency loop with harfbuzz confuses xorg-x11-fonts-ISO8859-1-100dpi installation??
by bugzilla＠redhat.com 07 Jun '22

07 Jun '22

https://bugzilla.redhat.com/show_bug.cgi?id=1925922 Bug ID: 1925922 Summary: dependency loop with harfbuzz confuses xorg-x11-fonts-ISO8859-1-100dpi installation?? Product: Fedora Version: rawhide Status: NEW Component: freetype Assignee: mkasik(a)redhat.com Reporter: mtasaka(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, kevin(a)tigcc.ticalc.org, mclasen(a)redhat.com, mkasik(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Comparing: Fedora-Scientific_KDE-Live-Rawhide-20210205.n.0 [SUCCESS] https://koji.fedoraproject.org/koji/buildinfo?buildID=1703766 Fedora-Scientific_KDE-Live-Rawhide-20210206.n.0 [FAIL] https://koji.fedoraproject.org/koji/taskinfo?taskID=61447565 The latter one has scriptlet error: https://kojipkgs.fedoraproject.org//work/tasks/7565/61447565/anaconda-packa… ``` 08:06:12,730 INF packaging: Installed: xorg-x11-font-utils-1:7.5-48.fc34.x86_64 1611907579 2b7ebb243e1e82d3cb66c5268fc9a1d9e43b3a80385b0832bb42d2841859e4c6 08:06:12,768 INF packaging: Configuring (running scriptlet for): xorg-x11-fonts-ISO8859-1-100dpi-7.5-27.fc34.noarch 1611907303 d34990ca2d30c51a49e168a636361c94eb9ec4a4995ed5724c9aab2cea71ac1f 08:06:12,789 INF dnf.rpm: mkfontscale: error while loading shared libraries: libfreetype.so.6: cannot open shared object file: No such file or directory warning: %post(xorg-x11-fonts-ISO8859-1-100dpi-7.5-27.fc34.noarch) scriptlet failed, exit status 127 ``` Note that /usr/bin/mkfontscale is in xorg-x11-font-utils-1:7.5-48.fc34.x86_64 , which surely Requires "libfreetype.so.6()(64bit)", but freetype is not installed when trying to run scriptlet for xorg-x11-fonts-ISO8859-1-100dpi. Comparing the above two, I guess the change in freetype is causing this - dependency loop between freetype and harfbuzz perhaps makes dnf to "postpone" installation of both packages. Version-Release number of selected component (if applicable): xorg-x11-font-utils-1:7.5-48.fc34.x86_64 xorg-x11-fonts-ISO8859-1-100dpi-7.5-27.fc34.noarch freetype-2.10.4-3.fc34.x86_64 harfbuzz-2.7.4-3.fc34.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 43

[Bug 1999240] New: OpenDyslexicMono-Regular is missing
by bugzilla＠redhat.com 07 Jun '22

07 Jun '22

https://bugzilla.redhat.com/show_bug.cgi?id=1999240 Bug ID: 1999240 Summary: OpenDyslexicMono-Regular is missing Product: Fedora Version: 34 Hardware: All OS: Linux Status: NEW Component: opendyslexic-fonts Assignee: spotrh(a)gmail.com Reporter: mikaela(a)mikaela.info QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, spotrh(a)gmail.com Target Milestone: --- Classification: Fedora Description of problem: The package opendyslexic-fonts doesn't include the monospace variant OpenDyslexicMono-Regular. It however exists in upstream (e.g. https://github.com/OpenDyslexic/opendyslexic-chrome/blob/11.0.0/app/fonts/o…) and Debian. Version-Release number of selected component (if applicable): 0.600 How reproducible: Always Steps to Reproduce: 1. sudo dnf install opendyslexic-fonts 2. sudo updatedb 3. locate opendyslexic|grep Mono Actual results: The file OpenDyslexicMono-Regular.otf isn't found or visible in any font selector. Expected results: /usr/share/fonts/opentype/opendyslexic/OpenDyslexicMono-Regular.otf on Debian and I think it should appear in font lists (my Debian is headless though). Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1960052] New: Font-Awesome is not updated
by bugzilla＠redhat.com 07 Jun '22

07 Jun '22

https://bugzilla.redhat.com/show_bug.cgi?id=1960052 Bug ID: 1960052 Summary: Font-Awesome is not updated Product: Fedora Version: 34 Status: NEW Component: fontawesome-fonts Assignee: pvoborni(a)redhat.com Reporter: tjamadeira(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, mrunge(a)redhat.com, pvoborni(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: The font-awesome it isn't updated. What can be done about this? How reproducible: Always. Steps to Reproduce: 1. Install font awesome via dnf 2. See the version of it. Actual results: Actual version is 4.7 Expected results: Version 5.15, maybe Additional info: https://bugzilla.redhat.com/show_bug.cgi?id=1808064 https://fontawesome.com/changelog/latest -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1894757] New: update kanjistrokeorders-fonts to v4.004
by bugzilla＠redhat.com 07 Jun '22

07 Jun '22

https://bugzilla.redhat.com/show_bug.cgi?id=1894757 Bug ID: 1894757 Summary: update kanjistrokeorders-fonts to v4.004 Product: Fedora Version: rawhide Hardware: All OS: Linux Status: NEW Component: kanjistrokeorders-fonts Severity: low Assignee: paul(a)frixxon.co.uk Reporter: piejacker875(a)teknik.io QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, paul(a)frixxon.co.uk, rene.ribaud(a)gmail.com Target Milestone: --- Classification: Fedora a new version of the font is available https://www.nihilist.org.uk/ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1926533] New: Postinstall scripts are failable, fail during KDE netinst (due to dependency loop most likely)
by bugzilla＠redhat.com 13 May '22

13 May '22

https://bugzilla.redhat.com/show_bug.cgi?id=1926533 Bug ID: 1926533 Summary: Postinstall scripts are failable, fail during KDE netinst (due to dependency loop most likely) Product: Fedora Version: rawhide Hardware: All OS: All Status: NEW Component: xorg-x11-fonts Severity: urgent Assignee: xgl-maint(a)redhat.com Reporter: awilliam(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: airlied(a)redhat.com, ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com, caolanm(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org, jglisse(a)redhat.com, negativo17(a)gmail.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, xgl-maint(a)redhat.com Target Milestone: --- Classification: Fedora In current Fedora Rawhide, KDE network installs fail with a scriptlet error in an xorg-x11-fonts subpackage: 16:36:01,304 INF dnf.rpm: mkfontscale: error while loading shared libraries: libfreetype.so.6: cannot open shared object file: No such file or directory warning: %post(xorg-x11-fonts-ISO8859-1-100dpi-7.5-27.fc34.noarch) scriptlet failed, exit status 127 16:36:01,310 ERR dnf.rpm: Error in POSTIN scriptlet in rpm package xorg-x11-fonts-ISO8859-1-100dpi Dependencies should be in place, AFAICT: xorg-x11-fonts subpackages require 'mkfontdir', which is in the same package as mkfontscale (xorg-x11-font-utils) and that package requires libfreetype.so.6. What's likely happening is a dependency loop that dnf has to break somehow. This isn't uncommon on initial install, something like A requires B requires C requires A, and in order to do anything, dnf has to pick *some* dependency to disregard. Probably because of some loop like this, it's ordering install of xorg-x11-fonts-ISO8859-1-100dpi before install of freetype, and so its %post script fails. We could look for and try to fix that loop, but note the packaging guidelines state: "All scriptlets MUST exit with the zero exit status. Because RPM in its default configuration does not execute shell scriptlets with the -e argument to the shell, excluding explicit exit calls (frowned upon with a non-zero argument!), the exit status of the last command in a scriptlet determines its exit status. Most commands in the snippets in this document have a “|| :” appended to them, which is a generic trick to force the zero exit status for those commands whether they worked or not. Usually the most important bit is to apply this to the last command executed in a scriptlet, or to add a separate command such as plain “:” or “exit 0” as the last one in a scriptlet. Note that depending on the case, other error checking/prevention measures may be more appropriate. Non-zero exit codes from scriptlets can break installs/upgrades/erases such that no further actions will be taken for that package in a transaction (see Ordering), which may for example prevent an old version of a package from being erased on upgrades, leaving behind duplicate rpmdb entries and possibly stale, unowned files on the filesystem. There are some cases where letting the transaction to proceed when some things in scriptlets failed may result in partially broken setup. It is however often limited to that package only whereas letting a transaction to proceed with some packages dropped out on the fly is more likely to result in broader system wide problems." https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/#_synt… basically, by policy scriptlets should be written to return 0 even if they don't work. These scriptlets aren't respecting that. Given that not running mkfontdir likely doesn't have any calamitous consequences, I think it would make sense to go with the guidelines and amend all the scriptlets to add `|| :` at the end (which will cause them to exit 0 even if the command failed). -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 2001332] New: pango-view with --backend=ft2 and ---antialias=none generates antialiased renderings
by bugzilla＠redhat.com 12 May '22

12 May '22

https://bugzilla.redhat.com/show_bug.cgi?id=2001332 Bug ID: 2001332 Summary: pango-view with --backend=ft2 and ---antialias=none generates antialiased renderings Product: Fedora Version: 34 Hardware: x86_64 OS: Linux Status: NEW Component: pango Severity: high Assignee: pwu(a)redhat.com Reporter: andre.maute(a)gmx.de QA Contact: extras-qa(a)fedoraproject.org CC: caillon+fedoraproject(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com, pwu(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1820649 --> https://bugzilla.redhat.com/attachment.cgi?id=1820649&action=edit image showing the problem Description of problem: Hello Fedora Team, I have a recently updated Fedora 34 installation. The problem I want to report is that it looks like the pango-view tool is always turning antialiasing on when one uses the FreeType backend --backend=ft2, even when one explicitly switches antialiasing off with --antialias=none, whereas it works for the --backend=cairo option. A second question would be if the FreeType backend generally doesn't/can't support --antialias=none? I tried to find some examples in C with antialising turned off but I wasn't successful. I must confess I didn't check other distributions. As pango-view is regarded as a tool for creating minimal reproducers against the font rendering stack, I dare to set the severity to 'high' :-) Best Regards Andre Version-Release number of selected component (if applicable): $ uname -a Linux localhost.localdomain 5.13.13-200.fc34.x86_64 #1 SMP Thu Aug 26 17:06:39 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux $ dnf list installed | grep dejavu dejavu-lgc-sans-fonts.noarch 2.37-16.fc34 @fedora dejavu-lgc-sans-mono-fonts.noarch 2.37-16.fc34 @fedora dejavu-lgc-serif-fonts.noarch 2.37-16.fc34 @fedora dejavu-sans-fonts.noarch 2.37-16.fc34 @fedora dejavu-sans-mono-fonts.noarch 2.37-16.fc34 @fedora dejavu-serif-fonts.noarch 2.37-16.fc34 @fedora $ dnf list installed | grep ImageMagick ImageMagick.x86_64 1:6.9.11.27-3.fc34 @fedora ImageMagick-libs.x86_64 1:6.9.11.27-3.fc34 @fedora $ dnf list installed | grep pango pango.i686 1.48.9-2.fc34 @updates pango.x86_64 1.48.9-2.fc34 @updates pango-devel.x86_64 1.48.9-2.fc34 @updates pangomm.x86_64 2.46.1-1.fc34 @updates $ dnf list installed | grep freetype freetype.i686 2.10.4-3.fc34 @fedora freetype.x86_64 2.10.4-3.fc34 @fedora freetype-devel.x86_64 2.10.4-3.fc34 @fedora $ dnf list installed | grep fontconfig fontconfig.i686 2.13.94-2.fc34 @updates fontconfig.x86_64 2.13.94-2.fc34 @updates fontconfig-devel.x86_64 2.13.94-2.fc34 @updates $ dnf list installed | grep cairo cairo.i686 1.17.4-3.fc34 @fedora cairo.x86_64 1.17.4-3.fc34 @fedora cairo-devel.x86_64 1.17.4-3.fc34 @fedora cairo-gobject.i686 1.17.4-3.fc34 @fedora cairo-gobject.x86_64 1.17.4-3.fc34 @fedora cairomm.x86_64 1.14.2-8.fc34 @fedora python2-cairo.x86_64 1.18.2-8.fc34 @fedora python3-cairo.x86_64 1.20.0-2.fc34 @fedora How reproducible: Always Steps to Reproduce: $ pango-view --no-display --dpi=72 --backend=cairo --antialias=none --font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ" --output=abc-cairo-aa-none.png $ pango-view --no-display --dpi=72 --backend=cairo --antialias=gray --font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ" --output=abc-cairo-aa-gray.png $ pango-view --no-display --dpi=72 --backend=cairo --antialias=subpixel --font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ" --output=abc-cairo-aa-subpixel.png $ pango-view --no-display --dpi=72 --backend=ft2 --antialias=none --font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ" --output=abc-ft2-aa-none.png $ pango-view --no-display --dpi=72 --backend=ft2 --antialias=gray --font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ" --output=abc-ft2-aa-gray.png $ pango-view --no-display --dpi=72 --backend=ft2 --antialias=subpixel --font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ" --output=abc-ft2-aa-subpixel.png $ gimp abc-*.png Actual results: Attached pngs. The file abc-ft2-aa-none.png is in gray-scale and not as expected in black-white. The file abc-cairo-aa-none.png is in black-white as expected. Expected results: I would have expected the files abc*--aa-none.png looking near identical. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 2009807] New: Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic
by bugzilla＠redhat.com 25 Apr '22

25 Apr '22

https://bugzilla.redhat.com/show_bug.cgi?id=2009807 Bug ID: 2009807 Summary: Change default Amharic font from Abyssinica SIL to Noto Serif Ethiopic Product: Fedora Version: 35 Hardware: x86_64 OS: Linux Status: NEW Component: Fonts Severity: medium Assignee: i18n-bugs(a)lists.fedoraproject.org Reporter: beta-stage(a)tutanota.com QA Contact: fonts-bugs(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Description of problem: Abyssinica SIL is an old font. It's barely legible and breaks in most apps. Noto Serif Ethiopic, on the other hand, is a modern and well designed font. Noto Serif Ethiopic is distributed with Open Font License, so packaging it won't be a problem. Link https://fonts.google.com/noto/specimen/Noto+Serif+Ethiopic?noto.query=Amhar… How reproducible: always Steps to Reproduce: 1. Pretty much using the the Amharic language anywhere on Fedora -- You are receiving this mail because: You are the QA Contact for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2009807

1 23

[Bug 1909251] New: stix-fonts-2.10 is available
by bugzilla＠redhat.com 07 Apr '22

07 Apr '22

https://bugzilla.redhat.com/show_bug.cgi?id=1909251 Bug ID: 1909251 Summary: stix-fonts-2.10 is available Product: Fedora Version: rawhide Status: NEW Component: stix-fonts Keywords: FutureFeature, Triaged Assignee: nicolas.mailhot(a)laposte.net Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, nicolas.mailhot(a)laposte.net, paul(a)frixxon.co.uk Target Milestone: --- Classification: Fedora Latest upstream release: 2.10 Current version/release in rawhide: 2.0.2-8.fc34 URL: http://sourceforge.net/projects/stixfonts Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/4893/ -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1809989] New: By default install Noto fonts for Unicode scripts not already covered by default
by bugzilla＠redhat.com 02 Apr '22

02 Apr '22

https://bugzilla.redhat.com/show_bug.cgi?id=1809989 Bug ID: 1809989 Summary: By default install Noto fonts for Unicode scripts not already covered by default Product: Fedora Version: 31 Status: NEW Component: google-noto-fonts Assignee: petersen(a)redhat.com Reporter: hsivonen(a)hsivonen.fi QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, psatpute(a)redhat.com, pwu(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora There is currently movement towards protecting browser users from font fingerprinting. This means refusing, by default, to load user-installed fonts, which makes the set of fonts that each OS installs by default even more important than before. Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1582687 W3C CSS WG issue: https://github.com/w3c/csswg-drafts/issues/4497 Currently, Windows 10, macOS, Android, and Chrome OS provide broader installed-by-default Unicode coverage than Fedora. Examples of living scripts that have enough active users to make it to the list at https://en.wikipedia.org/wiki/List_of_writing_systems#List_of_writing_scrip… but are not supported by default in Fedora 31 include Javanese, Sundanese, Batak, Balinese, Mongolian, and New Tai Lue. Egyptian hieroglyphs is an example of a dead script the Fedora 31 doesn't support out of the box but Windows 10, macOS, Chrome OS, and Android do. To remedy this with minimal disk space impact, I suggest the same approach that Apple took. Apple bundles with macOS those Noto fonts that cover scripts that were not already covered by the previous installed-by-default set of fonts on macOS. In the macOS case, the on-disk footprint of the Noto fonts that were required to take macOS to Android/Chrome OS-competitive Unicode coverage was only a couple of megabytes. (The fonts are hidden in /Library/Application Support/Apple/Fonts/Language Support/.) In the case of Fedora, the set of Noto fonts required to reach the Chrome OS / Android level of script coverage is a bit larger than in the macOS case but should still be manageable. Please install, by default, those Noto fonts that provide support for scripts that are not properly supported by the fonts that Fedora already installs by default. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1784650] New: Fontconfig is slow, causing stuttering and freezing
by bugzilla＠redhat.com 03 Mar '22

03 Mar '22

https://bugzilla.redhat.com/show_bug.cgi?id=1784650 Bug ID: 1784650 Summary: Fontconfig is slow, causing stuttering and freezing Product: Fedora Version: 31 Status: NEW Component: fontconfig Severity: high Assignee: tagoh(a)redhat.com Reporter: bepvte+bugzilla(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, john.j5live(a)gmail.com, mclasen(a)redhat.com, pnemade(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Fontconfig is much much slower than on other distros, and it stutters or freezes applications that use it. Version-Release number of selected component (if applicable): Name : fontconfig Version : 2.13.92 Release : 3.fc31 Architecture: x86_64 How reproducible: I can reproduce this bug on a fresh Fedora 31 vm with the Xfce desktop and google-noto-sans-* fonts installed. Steps to Reproduce: 1. dnf install google-noto-sans-* 2. run gedit on the attached example file alternatively 1. dnf install google-noto-sans-* 2. open firefox and browse to https://www.wikidata.org/wiki/Q52 (page with lots of languages) Actual results: It takes around 60 seconds for gedit to become responsive to scrolling and input. Mousepad is faster but still slow. It takes firefox upwards of 5 minutes to get to first paint on a page with many fonts or languages, compared to a simpler page. Expected results: Gedit should load files with many fonts at a similar speed as other distros. The page should load quickly, like on Debian and others. Additional info: I have tried to diagnose the source of this issue in many ways. Running `perf trace` on what sysprof indicated was the most busy function (FcStrCmpIgnoreCaseAndDelims), shows that every name of every font family is being compared to every other name of every other font family. I do not know if this is a normal behaviour of fontconfig. I have noticed the amount of calls to "FcStrCmpIgnoreCaseAndDelims" and program startup time both drop to a similar amount as Debian's when all of the "google-noto" configuration files in /etc/fonts/conf.d/ are deleted (These files are not present in Debian). However, this might not be the source of the problem: In the Debian vm, with a copy of my computer's /etc/fonts/, including the google-noto files, (I took care to ensure that there would be no broken symlinks) and /usr/share/fonts, fontconfig does not stall any programs. The amount of calls to FcStrCmpIgnoreCaseAndDelims is also much lower as well. This led me to believe that it was a difference caused by compiler flags but this does not seem to be the case. I tried to replace the optflags in the package, except for the rpmbuild required debug ones, and found no difference. I also checked to ensure that it was not caused by GCC version differences. Debian results for mousepad: 1,845,449 calls to FcStrCmpIgnoreCaseAndDelims Time: 5 seconds Fedora results for mousepad: 11,658,380 calls to FcStrCmpIgnoreCaseAndDelims Time: 23 seconds https://perfht.ml/2tleJxN Here is a link to a Firefox profiler result of the wikidata page, where in the flame graph you can see that Firefox is spending most of its time in fontconfig. You can also see "FirstNonBlankPaint" is at 50 seconds in the marker table. TLDR: Fontconfig matching is slow with all google-noto fonts installed, unless you remove the noto config files. Using the same exact font directory and config directory (including the noto config files) on Debian does not cause the same problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

fonts-bugs October 2021