fonts-bugs June 2021

fonts-bugs@lists.fedoraproject.org

2 participants
52 discussions

[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

[Bug 1806272] New: forge-font macro transition causes broken dependencies
by bugzilla＠redhat.com 04 Feb '22

04 Feb '22

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bug ID: 1806272 Summary: forge-font macro transition causes broken dependencies Product: Fedora Version: rawhide Status: NEW Component: dejavu-fonts Assignee: nicolas.mailhot(a)laposte.net Reporter: decathorpe(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, nicolas.mailhot(a)laposte.net, paul(a)frixxon.co.uk, peter(a)thecodergeek.com Target Milestone: --- Classification: Fedora With the transition to new forge-based fonts macros, the -common subpackage was dropped, but some packages depend on that. They are now not installable on fedora 32+ because that package is gone (only Obsoleted, not Provided). This affects at least python3-weasyprint. Additionally, the sdljava-demo package now has broken dependencies as well: - /usr/share/fonts/dejavu/DejaVuSans-Bold.ttf - /usr/share/fonts/dejavu/DejaVuSans-BoldOblique.ttf - /usr/share/fonts/dejavu/DejaVuSans-Oblique.ttf - /usr/share/fonts/dejavu/DejaVuSans.ttf Probably those files were renamed with the forge macro transition. -- You are receiving this mail because: You are on the CC list for the bug.

1 73

[Bug 1977272] New: sil-charis-fonts-6.000 is available
by bugzilla＠redhat.com 02 Feb '22

02 Feb '22

https://bugzilla.redhat.com/show_bug.cgi?id=1977272 Bug ID: 1977272 Summary: sil-charis-fonts-6.000 is available Product: Fedora Version: rawhide Status: NEW Component: sil-charis-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, kevin(a)scrye.com, nicolas.mailhot(a)laposte.net Target Milestone: --- Classification: Fedora Latest upstream release: 6.000 Current version/release in rawhide: 5.000-14.fc33 URL: http://scripts.sil.org/CharisSIL_download 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/4818/ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1890210] New: CVE-2020-15999 freetype: heap-based buffer overflow via malformed ttf files
by bugzilla＠redhat.com 30 Jan '22

30 Jan '22

https://bugzilla.redhat.com/show_bug.cgi?id=1890210 Bug ID: 1890210 Summary: CVE-2020-15999 freetype: heap-based buffer overflow via malformed ttf files Product: Security Response Hardware: All OS: Linux Status: NEW Component: vulnerability Keywords: Security Severity: medium Priority: medium Assignee: security-response-team(a)redhat.com Reporter: gsuckevi(a)redhat.com CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com, erack(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org, gecko-bugs-nobody(a)redhat.com, gghezzo(a)redhat.com, gnome-sig(a)lists.fedoraproject.org, gparvin(a)redhat.com, jhorak(a)redhat.com, john.j5live(a)gmail.com, jramanat(a)redhat.com, jweiser(a)redhat.com, 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, scorneli(a)redhat.com, stcannon(a)redhat.com, stransky(a)redhat.com, thee(a)redhat.com, tpopela(a)redhat.com Target Milestone: --- Classification: Other A flaw was found in freetype in the way it processes PNG images embedded into fonts. A crafted TTF file can lead to heap-based buffer overflow due to integer truncation in Load_SBit_Png function. Reference: https://savannah.nongnu.org/bugs/?59308 Upstream patch: https://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=a3bab16… -- You are receiving this mail because: You are on the CC list for the bug.

1 66

[Bug 1820166] New: Droid sans overrides my default CJK font
by bugzilla＠redhat.com 28 Jan '22

28 Jan '22

https://bugzilla.redhat.com/show_bug.cgi?id=1820166 Bug ID: 1820166 Summary: Droid sans overrides my default CJK font Product: Fedora Version: 32 Status: NEW Component: google-droid-fonts Severity: low Assignee: nicolas.mailhot(a)laposte.net Reporter: taocrismon(a)hotmail.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, nicolas.mailhot(a)laposte.net, oliver(a)redhat.com, paul(a)frixxon.co.uk, tremble(a)tremble.org.uk Target Milestone: --- Classification: Fedora Description of problem: I have this (per-user) fontconfig configuration to set my preferred sans-serif font: <alias> <family>sans-serif</family> <prefer> <family>Noto Sans</family> <family>Noto Sans CJK SC</family> </prefer> </alias> It should fall back to "Noto Sans CJK SC" when displaying CJK characters. Since F32 this isn't working anymore. CJK characters are rendered in a different font, which I cannot recognize. Digging through fc_debug logs, "Droid Sans" is appended right after "Noto Sans", before "Noto Sans CJK SC" in the font matching list. Debug messages confirm it's indeed Droid Sans getting picked. Removing the relevant part in /etc/fonts/conf.d/65-google-droid-sans-fonts.conf mitigates this issue. However since both Noto Sans & Droid Sans do not contain CJK characters, they should both be skipped in favor of CJK fonts. Could this be a metadata problem? i.e. Droid Sans wrongly advertises as CJK capable. Version-Release number of selected component (if applicable): google-droid-sans-fonts-20200215-3.fc32.noarch -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1938205] New: google-droid-sans-fonts has higher priority than google-noto-sans-fonts
by bugzilla＠redhat.com 28 Jan '22

28 Jan '22

https://bugzilla.redhat.com/show_bug.cgi?id=1938205 Bug ID: 1938205 Summary: google-droid-sans-fonts has higher priority than google-noto-sans-fonts Product: Fedora Version: 34 Status: NEW Component: google-droid-fonts Assignee: nicolas.mailhot(a)laposte.net Reporter: tagoh(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, nicolas.mailhot(a)laposte.net, oliver(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Summary says it all. I don't think Droid Fonts is better than Noto Fonts. Version-Release number of selected component (if applicable): google-droid-sans-fonts-20200215-9.fc34.noarch How reproducible: Steps to Reproduce: 1.rpmm -ql google-droid-sans-fonts google-noto-sans-fonts | grep conf.d 2. 3. Actual results: /etc/fonts/conf.d/65-google-droid-sans-fonts.conf /etc/fonts/conf.d/66-google-noto-sans.conf Expected results: google-noto-sans one should come first. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1931547] New: Cantarell Regular rendering issues in Gnome Shell
by bugzilla＠redhat.com 30 Nov '21

30 Nov '21

https://bugzilla.redhat.com/show_bug.cgi?id=1931547 Bug ID: 1931547 Summary: Cantarell Regular rendering issues in Gnome Shell Product: Fedora Version: 33 Hardware: x86_64 OS: Linux Status: NEW Component: abattis-cantarell-fonts Severity: low Assignee: klember(a)redhat.com Reporter: gregswift(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: cosimo.cecchi(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, ian(a)ianweller.org, klember(a)redhat.com, me(a)fale.io, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1758636 --> https://bugzilla.redhat.com/attachment.cgi?id=1758636&action=edit broken font lock screen clock Description of problem: I've got about 7 machines running fedora 33, to the same patch level. 4 of them were showing poorly rendered fonts/wrong characters in various parts of the gnome-shell ui. Primarily: lock screen time, unlock password entry field, and the top bar calendar view. See attached screenshots. For one of the machines it stopped doing it after a week or 2. The other machines kept doing it until I changed the `Interface Text` font using TweakTool, the default is Cantarell Regular, and any other font seems to be fine, including other Cantarell fonts. Version-Release number of selected component (if applicable): The problem started after update on 2/1 which included abattis-cantarell-fonts-0.301-1.fc33.noarch /var/log/dnf.rpm.log:2021-02-01T13:07:46-0600 SUBDEBUG Upgrade: abattis-cantarell-fonts-0.301-1.fc33.noarch /var/log/dnf.rpm.log:2021-02-01T13:10:00-0600 SUBDEBUG Upgraded: abattis-cantarell-fonts-0.201-4.fc33.noarch How reproducible: On the 3 remaining machines with the issue if I set the font back to Cantarell Regular the problem returns. But I haven't been able to make it happen on other machines that arent experiencing the issue. Steps to Reproduce: 1. Run Fedora 33 with Gnome, using defaults Actual results: You will either experience the problem or you won't. Expected results: Fonts to be rendered properly. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1753020] New: Powerline symbols no longer align
by bugzilla＠redhat.com 30 Nov '21

30 Nov '21

https://bugzilla.redhat.com/show_bug.cgi?id=1753020 Bug ID: 1753020 Summary: Powerline symbols no longer align Product: Fedora Version: 30 Status: NEW Component: terminus-font Assignee: extras-orphan(a)fedoraproject.org Reporter: andrew(a)linuxjedi.co.uk QA Contact: extras-qa(a)fedoraproject.org CC: extras-orphan(a)fedoraproject.org, fonts-bugs(a)lists.fedoraproject.org, rhbugs(a)n-dimensional.de Target Milestone: --- Classification: Fedora Created attachment 1615993 --> https://bugzilla.redhat.com/attachment.cgi?id=1615993&action=edit Screenshot of zsh+om-my-zsh using powerline-fonts and terminus-fonts 4.48 Description of problem: With version 4.48 of the Terminus font the powerline symbols no longer align for sizes less than 14pt Version-Release number of selected component (if applicable): terminus-fonts-4.48-1.fc30.noarch How reproducible: 100% Steps to Reproduce: 1. Install terminus-fonts and powerline-fonts. 2. Use something with powerline (zsh, vim, etc...) 3. Update to the latest terminus-fonts version 4. Use powerline things again Actual results: Bad symbol alignment Expected results: Good symbol alignment Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 17

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

fonts-bugs June 2021