fonts-bugs June 2020

fonts-bugs@lists.fedoraproject.org

2 participants
76 discussions

[Bug 1833858] New: Hangul Jamo is seperated and printed respectively
by bugzilla＠redhat.com 27 Nov '24

27 Nov '24

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 Bug ID: 1833858 Summary: Hangul Jamo is seperated and printed respectively Product: Fedora Version: 32 Status: NEW Component: google-droid-fonts Assignee: nicolas.mailhot(a)laposte.net Reporter: hyunwoo.park(a)gmail.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 Created attachment 1687129 --> https://bugzilla.redhat.com/attachment.cgi?id=1687129&action=edit wrong display of Hangul at LibreOffice Writer Description of problem: When Hangul is output to the monitor, Chosung, Neutral, and Jongseong are output separately. Version-Release number of selected component (if applicable): Font file, /usr/share/fonts/google-droid-sans-fonts/DroidSansFallbackFull.ttf, of google-droid-sans-fonts-20200215-3.fc32.noarch How reproducible: If you create a test.html containing "가속도" and open the file in the chrome browser, the Korean alphabet will be displayed separately. Or, write "가속도" at LibreOffice Writer and select font as "Droid Sans Fallback". Steps to Reproduce: 1. write "가속도" at LibreOffece Writer 2. select the text and change font name to "Droid Sans Fallback" Actual results: The text is displayed like "가ㅅㅗㄱㄷㅗ". Expected results: Text should be "가속도" Additional info: https://kldp.org/node/163247 -- You are receiving this mail because: You are on the CC list for the bug.

1 43

[Bug 1761885] New: rpm -V complains about mode for ghost .uuid files
by bugzilla＠redhat.com 24 Feb '24

24 Feb '24

https://bugzilla.redhat.com/show_bug.cgi?id=1761885 Bug ID: 1761885 Summary: rpm -V complains about mode for ghost .uuid files Product: Fedora Version: rawhide Status: NEW Component: fontpackages Assignee: nicolas.mailhot(a)laposte.net Reporter: mtasaka(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, redhat-bugzilla(a)linuxnetz.de, tagoh(a)redhat.com Target Milestone: --- Link ID: Red Hat Bugzilla 1564432 Classification: Fedora Description of problem: rpm -Va complains a lot about mode of %ghost .uuid files: .M....... g /usr/share/fonts/paktype-naqsh/.uuid .M....... g /usr/share/fonts/lilypond/.uuid .M....... g /usr/share/fonts/sil-padauk/.uuid .M....... g /usr/share/fonts/google-droid/.uuid .M....... g /usr/share/fonts/lilypond/.uuid .M....... g /usr/share/fonts/smc-suruma/.uuid .M....... g /usr/share/fonts/google-android-emoji/.uuid .M....... g /usr/share/fonts/google-crosextra-carlito/.uuid .M....... g /usr/share/fonts/lohit-assamese/.uuid .M....... g /usr/share/fonts/dejavu/.uuid .M....... g /usr/share/fonts/lohit-telugu/.uuid .M....... g /usr/share/fonts/lilypond/.uuid ..... Looks like fontpackages-devel template rpmmacro creates .uuid which %ghost %atttr(0000) e.g. [root@localhost ~]# rpm -qf /usr/share/fonts/google-droid/.uuid google-droid-sans-fonts-20120715-16.fc31.noarch [root@localhost ~]# rpm -qlv google-droid-sans-fonts | grep uuid ---------- 1 root root 0 7月 25 23:03 /usr/share/fonts/google-droid/.uuid ref: https://src.fedoraproject.org/rpms/fontpackages/blob/master/f/fontpackages-… but I guess %transfiletriggerin script by fontconfig creates .uuid as 0755 permission (perhaps) Version-Release number of selected component (if applicable): fontpackages-filesystem-1.44-25.fc31.noarch fontconfig-2.13.92-3.fc31.x86_64 fontconfig-2.13.92-3.fc31.i686 google-droid-sans-fonts-20120715-16.fc31.noarch How reproducible: 100% Steps to Reproduce: 1. See above, try $ rpm -Va 2. 3. Actual results: See above, lots of .uuid permission complaint Expected results: No complaint by rpm -Va Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1727602] New: Fedora flatpak for this app on registry.fedoraproject.org
by bugzilla＠redhat.com 30 Jun '23

30 Jun '23

https://bugzilla.redhat.com/show_bug.cgi?id=1727602 Bug ID: 1727602 Summary: Fedora flatpak for this app on registry.fedoraproject.org Product: Fedora Version: rawhide Status: NEW Component: fontforge Assignee: kevin(a)scrye.com Reporter: 7d28c752(a)opayq.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, kevin(a)scrye.com, paul(a)frixxon.co.uk, pnemade(a)redhat.com Target Milestone: --- Classification: Fedora It would be great if you could provide a flatpak package of this app to https://registry.fedoraproject.org/. Especially for users of Fedora Silverblue https://silverblue.fedoraproject.org/ this then allows a seamless installation and upgrades without rebooting the system (just restarting the application). Additionally, flatpaks can of course be installed on any distro, so also non-Fedora users could use it too. More details: * https://fedoraproject.org/wiki/Workstation/Flatpaks * https://fedoraproject.org/wiki/Changes/Graphical_Applications_as_Flatpaks I know this app is available on Flathub as a flatpak, but I still prefer Fedora's package testing/QA etc., that's why I'd also like to have a version on https://registry.fedoraproject.org/. Also Flathub is a third-party source from the Fedora users/projects viewpoint, so I guess some users would not like to use third-party app sources. However, the fact that it is on Flathub should make it easier for you to implement this, because you can have a look on how they do it. (Not that you need to do everything in the same way, but it proves it is possible to package as a flatpak, at least.) -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1813728] New: Square four dot Unicode character has incorrect glyph
by bugzilla＠redhat.com 02 Jun '23

02 Jun '23

https://bugzilla.redhat.com/show_bug.cgi?id=1813728 Bug ID: 1813728 Summary: Square four dot Unicode character has incorrect glyph Product: Fedora Version: 31 Hardware: x86_64 OS: Linux Status: NEW Component: pango Severity: low Assignee: pwu(a)redhat.com Reporter: guillaumepoiriermorency(a)gmail.com 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, john.j5live(a)gmail.com, 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 Description of problem: The glyph for the Unicode "square four dot" character is incorrect. Version-Release number of selected component (if applicable): I think this problem arose when upgrading from Fedora 30 to Fedora 31. How reproducible: The simplest way is to start GNOME Characters Map and search for "square four dot". -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1779123] New: Pango no longer supports type1 fonts
by bugzilla＠redhat.com 25 Apr '23

25 Apr '23

https://bugzilla.redhat.com/show_bug.cgi?id=1779123 Bug ID: 1779123 Summary: Pango no longer supports type1 fonts Product: Fedora Version: rawhide Status: NEW Component: pango Assignee: pwu(a)redhat.com Reporter: mjg(a)fedoraproject.org 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, john.j5live(a)gmail.com, 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 Description of problem: In pango 1.44, pango dropped support for type1 fonts. Therefore, no application which uses pango for font loading can use type1 fonts any more. Version-Release number of selected component (if applicable): pango-1.44.6-1.fc31.x86_64 (and later) How reproducible: always Steps to Reproduce: 1. Upgrade F31 or rawhide 2. Open any pango-using application 3. Try to use type1 font Actual results: No type1 font is usable Expected results: Type1 font is usable Additional info: bug 1753295 is the same bug for dropped bitmap font support. Over there, workarounds specific for bitmap fonts (conversion to opentype bitmap fonts) are discussed. An attempt to discuss type1 there failed. This bug here is specifically about type1 fonts to discuss ways (or their absence) to deal with pangos dropped type 1 support. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1678974] New: libfontenc-1.1.4 is available
by bugzilla＠redhat.com 04 Nov '22

04 Nov '22

https://bugzilla.redhat.com/show_bug.cgi?id=1678974 Bug ID: 1678974 Summary: libfontenc-1.1.4 is available Product: Fedora Version: rawhide Status: NEW Component: libfontenc Keywords: FutureFeature, Triaged Assignee: btissoir(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, btissoir(a)redhat.com, caillon+fedoraproject(a)gmail.com, caolanm(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org, john.j5live(a)gmail.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 1.1.4 Current version/release in rawhide: 1.1.3-10.fc30 URL: http://xorg.freedesktop.org/archive/individual/lib/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/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/1613/ -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1837850] New: Unable to open Noto CJK fonts properly because of no cidmap file
by bugzilla＠redhat.com 26 Jun '22

26 Jun '22

https://bugzilla.redhat.com/show_bug.cgi?id=1837850 Bug ID: 1837850 Summary: Unable to open Noto CJK fonts properly because of no cidmap file Product: Fedora Version: rawhide Status: NEW Component: fontforge Assignee: kevin(a)scrye.com Reporter: tagoh(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, kevin(a)scrye.com, paul(a)frixxon.co.uk, pnemade(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: When going to open Noto CJK fonts on fontforge, fontforge opens an error dialog that claims no cidmap file found. Version-Release number of selected component (if applicable): fontforge-20200314-5.fc32.x86_64 How reproducible: always Steps to Reproduce: 1.fontforge /usr/share/fonts/google-noto-cjk/NotoSansCJK-Regular.ttc 2.Select any family names in the list 3. Actual results: Open an error dialog claims: FontForge was unable to find a cidmap file for this font. It is not essential to have one, but some things will work better if you do. if you have not done so you might want to download the cidmaps from: http://FontForge.sourceforge.net/cidmaps.tgz and then gunzip and untar them and move them to: /usr/share/fontforge Expected results: should start loading a font Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

fonts-bugs June 2020