fonts-bugs August 2024

fonts-bugs@lists.fedoraproject.org

3 participants
20 discussions

[Bug 2262410] New: Fonts are looking wrong after 20240101 update
by bugzilla＠redhat.com 13 Dec '25

13 Dec '25

https://bugzilla.redhat.com/show_bug.cgi?id=2262410 Bug ID: 2262410 Summary: Fonts are looking wrong after 20240101 update Product: Fedora Version: 39 Hardware: x86_64 OS: Linux Status: NEW Component: google-noto-fonts Severity: medium Assignee: tagoh(a)redhat.com Reporter: priv.luk(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, pwu(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Fonts look improperly in multiple places, e.g. mpv or KDE file picker. Reproducible: Always Steps to Reproduce: 1. Open mpv and look at OSD fonts Actual Results: Fonts look wrong Expected Results: Fonts look properly See https://github.com/mpv-player/mpv/issues/13396 for screenshots. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2262410 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 41

[Bug 2267629] New: liberation-mono-fonts breaks default font for Hebrew
by bugzilla＠redhat.com 11 Jul '25

11 Jul '25

https://bugzilla.redhat.com/show_bug.cgi?id=2267629 Bug ID: 2267629 Summary: liberation-mono-fonts breaks default font for Hebrew Product: Fedora Version: 40 OS: Linux Status: NEW Component: google-noto-fonts Keywords: i18n Severity: medium Assignee: tagoh(a)redhat.com Reporter: tagoh(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, pwu(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora google-noto-sans-hebrew-vf-fonts is supposed to be a default monospace font for Hebrew though, liberation-mono-fonts is picked up as the default monospace font when it is installed. This happens because liberation use 59 as the priority number although google-noto-sans-hebrew-vf-fonts use 66. The priority number needs to be updated. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2267629 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 4

[Bug 2166360] New: sil-andika-fonts-6.200 is available
by bugzilla＠redhat.com 11 Jul '25

11 Jul '25

https://bugzilla.redhat.com/show_bug.cgi?id=2166360 Bug ID: 2166360 Summary: sil-andika-fonts-6.200 is available Product: Fedora Version: rawhide Status: NEW Component: sil-andika-fonts Keywords: FutureFeature, Triaged Assignee: aekoroglu(a)linux.intel.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: aekoroglu(a)linux.intel.com, fonts-bugs(a)lists.fedoraproject.org, nicolas.mailhot(a)laposte.net Target Milestone: --- Classification: Fedora Releases retrieved: 6.200 Upstream release that is considered latest: 6.200 Current version/release in rawhide: 6.101-3.fc38 URL: https://software.sil.org/andika/ 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://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_M… 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/4816/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/sil-andika-fonts -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2166360

1 8

[Bug 2308744] New: Upgrade Fira Sans to version 4.301 (post-Mozilla involvement) and package FiraGO
by bugzilla＠redhat.com 14 Jun '25

14 Jun '25

https://bugzilla.redhat.com/show_bug.cgi?id=2308744 Bug ID: 2308744 Summary: Upgrade Fira Sans to version 4.301 (post-Mozilla involvement) and package FiraGO Product: Fedora Version: 40 Hardware: All OS: Linux Status: NEW Component: mozilla-fira-fonts Severity: medium Assignee: ego.cordatus(a)gmail.com Reporter: mateusrodcosta(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, ego.cordatus(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora From https://bboxtype.com/fira/ : > Originally designed as a typeface for the Mozilla OS, Fira Sans has developed towards a standalone Open Font project. In 2012, we designed the firstversion of Fira in cooperation with Erik Spiekermann and Mozilla. Over the next years, Fira covered more and more languages and provided further weights and styles. > In 2016, with version 4.2, Mozilla decided to not put effort into the project anymore and in fact quit (please note that their Git is not up to date). Since 2016, we advance the project with the help of different partners. Fira Sans 4.3 will presumably be the last version. All upcoming extensions will be based on FiraGO. Essentially Mozilla stopped working on Fira Sans but it was kept being worked on by bBox Type GmbH. This might also make a opportunity to migrate to the Fira Mono version by bBox Type GmbH and also package FiraGo which isn't packaged yet. For more info about Fira GO vs Fira Sans: https://bboxtype.com/downloads/Projects/FiraGO_FiraSans_180109.pdf Migrating to the bBox Type versions might requiring renaming of the package to drop the "mozilla" prefix, as Mozilla is not involved anymore. Reproducible: Always This is essentially a request to move the Fira Sans e Fira Mono fonts from the Mozilla upstream to the bBox Type upstream. As an extra it's also a request to separately start packaging FiraGO, an extended version of Fira Sans with improved language support. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2308744 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 6

[Bug 2304153] New: freetype-2.13.3 is available
by bugzilla＠redhat.com 28 May '25

28 May '25

https://bugzilla.redhat.com/show_bug.cgi?id=2304153 Bug ID: 2304153 Summary: freetype-2.13.3 is available Product: Fedora Version: rawhide Status: NEW Component: freetype Keywords: FutureFeature, Triaged Assignee: mkasik(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, mclasen(a)redhat.com, mkasik(a)redhat.com, rstrode(a)redhat.com, suraj.ghimire7(a)gmail.com Target Milestone: --- Classification: Fedora Releases retrieved: 2.13.3 Upstream release that is considered latest: 2.13.3 Current version/release in rawhide: 2.13.2-6.fc41 URL: https://www.freetype.org/ 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://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_M… 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/854/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/freetype -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2304153 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 3

[Bug 2302845] New: [abrt] fontforge: _PasteToSC(): fontforge killed by SIGSEGV
by bugzilla＠redhat.com 20 May '25

20 May '25

https://bugzilla.redhat.com/show_bug.cgi?id=2302845 Bug ID: 2302845 Summary: [abrt] fontforge: _PasteToSC(): fontforge killed by SIGSEGV Product: Fedora Version: 40 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:a2035d90b85cf9fe222a7339dce93244f2ef2aa5;VAR IANT_ID=workstation; Component: fontforge Assignee: kevin(a)scrye.com Reporter: lasse.siemoneit(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, kevin(a)scrye.com, pnemade(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: I tried to convert the Hubot Sans font developed by GitHub to a NerdFont. I cloned the nerds-font repository and executed the following command in this directory: fontforge -script font-patcher $HOME/Documents/HubotSans/Hubot-Sans.ttf Version-Release number of selected component: fontforge-20230101-11.fc40 Additional info: reporter: libreport-2.17.15 type: CCpp reason: fontforge killed by SIGSEGV journald_cursor: s=1f13099aed44407eb8f9f65c6222e01e;i=c16178;b=d9f7df05b9394ad880fd776f46dcf298;m=16d0a6d04;t=61eec33c80de7;x=fe1c1aae4fdecfb2 executable: /usr/bin/fontforge cmdline: fontforge -script font-patcher /home/lasse/Documents/HubotSans/Hubot-Sans.ttf cgroup: 0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-d1fe7599-7506-44c4-9066-3af7dbf963e0.scope rootdir: / uid: 1000 kernel: 6.9.12-200.fc40.x86_64 package: fontforge-20230101-11.fc40 runlevel: N 5 backtrace_rating: 4 crash_function: _PasteToSC Truncated backtrace: Thread no. 1 (22 frames) #0 _PasteToSC at /usr/src/debug/fontforge-20230101-11.fc40.x86_64/fontforge/cvundoes.c:2357 #1 PasteIntoFV at /usr/src/debug/fontforge-20230101-11.fc40.x86_64/fontforge/cvundoes.c:3712 #2 PyFFFont_paste at /usr/src/debug/fontforge-20230101-11.fc40.x86_64/fontforge/python.c:17355 #3 _PyEval_EvalFrameDefault at Python/bytecodes.c:3158 #4 PyEval_EvalCode at /usr/src/debug/python3.12-3.12.4-1.fc40.x86_64/Python/ceval.c:578 #5 run_eval_code_obj at /usr/src/debug/python3.12-3.12.4-1.fc40.x86_64/Python/pythonrun.c:1722 #6 run_mod at /usr/src/debug/python3.12-3.12.4-1.fc40.x86_64/Python/pythonrun.c:1743 #7 pyrun_file at /usr/src/debug/python3.12-3.12.4-1.fc40.x86_64/Python/pythonrun.c:1643 #8 _PyRun_SimpleFileObject at /usr/src/debug/python3.12-3.12.4-1.fc40.x86_64/Python/pythonrun.c:433 #9 _PyRun_AnyFileObject at /usr/src/debug/python3.12-3.12.4-1.fc40.x86_64/Python/pythonrun.c:78 #10 pymain_run_file_obj at /usr/src/debug/python3.12-3.12.4-1.fc40.x86_64/Modules/main.c:360 #11 pymain_run_file at /usr/src/debug/python3.12-3.12.4-1.fc40.x86_64/Modules/main.c:379 #12 pymain_run_python at /usr/src/debug/python3.12-3.12.4-1.fc40.x86_64/Modules/main.c:629 #13 Py_RunMain at /usr/src/debug/python3.12-3.12.4-1.fc40.x86_64/Modules/main.c:709 #14 Py_Main at /usr/src/debug/python3.12-3.12.4-1.fc40.x86_64/Modules/main.c:751 #15 PyFF_Main at /usr/src/debug/fontforge-20230101-11.fc40.x86_64/fontforge/python.c:19621 #16 _CheckIsScript at /usr/src/debug/fontforge-20230101-11.fc40.x86_64/fontforge/scripting.c:10524 #17 CheckIsScript at /usr/src/debug/fontforge-20230101-11.fc40.x86_64/fontforge/scripting.c:10546 #18 fontforge_main at /usr/src/debug/fontforge-20230101-11.fc40.x86_64/fontforgeexe/startui.c:744 #19 __libc_start_call_main at ../sysdeps/nptl/libc_start_call_main.h:58 #20 __libc_start_main_impl at ../csu/libc-start.c:360 #21 _start -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2302845 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 2

[Bug 2112732] New: Fail to build from source
by bugzilla＠redhat.com 16 May '25

16 May '25

https://bugzilla.redhat.com/show_bug.cgi?id=2112732 Bug ID: 2112732 Summary: Fail to build from source Product: Fedora Version: rawhide Status: NEW Component: campivisivi-titillium-fonts Assignee: luya_tfz(a)thefinalzone.net Reporter: tagoh(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, luya_tfz(a)thefinalzone.net Target Milestone: --- Classification: Fedora Description of problem: Titillium_roman_upright_italic_2_0_OT.zip contains two directory. one is Titillium_roman_upright_italic_2_0_OT which is specified as a base directory in the spec file. another one is __MACOSX. the spec file doesn't clean up __MACOSX, thus, the build stop on extracting like: + /usr/lib/rpm/rpmuncompress -x /var/home/tagoh/rpmbuild/SOURCES/Titillium_roman_upright_italic_2_0_OT.zip replace __MACOSX/Titillium_roman_upright_italic_2_0_OT/._Titillium-Black.otf? [y]es, [n]o, [A]ll, [N]one, [r]ename: Version-Release number of selected component (if applicable): campivisivi-titillium-fonts-20120913-25.fc37 How reproducible: always Steps to Reproduce: 1.download SRPM 2.rpmbuild --rebuild campivisivi-titillium-fonts-20120913-25.fc37.src.rpm 3.try again once the rebuild finished. Actual results: the rebuild always fails except first try. Expected results: the rebuild should be successfully finished any time. Additional info: -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2112732

1 6

[Bug 1954359] Many emoji don't show up in Qt apps because qt does not handle 'emoji' font family
by bugzilla＠redhat.com 07 May '25

07 May '25

https://bugzilla.redhat.com/show_bug.cgi?id=1954359 --- Comment #18 from Peng Wu <pwu(a)redhat.com> --- Okay, I will submit the change to Qt upstream for review. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1954359 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

2 1

[Bug 2277345] New: NotoSansMono[wght].ttf file name causes scripts with failglob enabled to fail
by bugzilla＠redhat.com 03 Mar '25

03 Mar '25

https://bugzilla.redhat.com/show_bug.cgi?id=2277345 Bug ID: 2277345 Summary: NotoSansMono[wght].ttf file name causes scripts with failglob enabled to fail Product: Fedora Version: 40 Hardware: All OS: Linux Status: NEW Component: google-noto-fonts Severity: medium Assignee: tagoh(a)redhat.com Reporter: hartsjc(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, pwu(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora shopt failglob If set, patterns which fail to match filenames during pathname expansion result in an expansion error. Using this feature is good practice in scripts as helps prevent scripting mistakes; however, having file name with square brackets causes failures. And with Fedora 40 upgrade seems google-noto-sans-mono-vf-fonts-20240301-2.fc40.noarch has added one with: /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf Reproducible: Always Steps to Reproduce: 1. Causes globs that don't expand to cause errors $ shopt -s failglob 2. Try use files from rpm as variable, and fail $ for file in $(rpm -q --list google-noto-sans-mono-vf-fonts) ; do [[ -f "/${file}" ]] || echo "${file}" done -bash: no match: /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf 3. Note the RC $ echo $? 1 4. Or even command line $ rpm -qf /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf -bash: no match: /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf $ rpm -qf '/usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf' google-noto-sans-mono-vf-fonts-20240301-2.fc40.noarch Actual Results: -bash: no match: /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf Expected Results: no error accessing files with failglob shopt enabled started fedora 40 upgrade, as daily script of mine fails because this file is included in initramfs too. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2277345 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 6

[Bug 2274629] New: Please branch and build artwiz-aleczapka-fonts in epel9
by bugzilla＠redhat.com 27 Feb '25

27 Feb '25

https://bugzilla.redhat.com/show_bug.cgi?id=2274629 Bug ID: 2274629 Summary: Please branch and build artwiz-aleczapka-fonts in epel9 Product: Fedora EPEL Version: epel9 Status: NEW Component: artwiz-aleczapka-fonts Assignee: dchen(a)redhat.com Reporter: davide(a)cavalca.name QA Contact: extras-qa(a)fedoraproject.org CC: dchen(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org, spotrh(a)gmail.com Blocks: 1914423 (EPELPackagersSIG) Target Milestone: --- Classification: Fedora Please branch and build artwiz-aleczapka-fonts in epel9. If you do not wish to maintain artwiz-aleczapka-fonts in epel9, or do not think you will be able to do this in a timely manner, the EPEL Packagers SIG would be happy to be a co-maintainer of the package; please add the epel-packagers-sig group through https://src.fedoraproject.org/rpms/artwiz-aleczapka-fonts/addgroup and grant it commit access, or collaborator access on epel* branches. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1914423 [Bug 1914423] Tracker for epel-packagers-sig -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2274629 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 10

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

fonts-bugs August 2024