[Bug 1837850] New: Unable to open Noto CJK fonts properly because of
no cidmap file
by bugzilla＠redhat.com
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 year, 10 months
[Bug 1894757] New: update kanjistrokeorders-fonts to v4.004
by bugzilla＠redhat.com
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 year, 11 months
[Bug 1809989] New: By default install Noto fonts for Unicode scripts
not already covered by default
by bugzilla＠redhat.com
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_scr...
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.
2 years, 1 month
[Bug 1784650] New: Fontconfig is slow, causing stuttering and
freezing
by bugzilla＠redhat.com
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.
2 years, 2 months
[Bug 1806272] New: forge-font macro transition causes broken
dependencies
by bugzilla＠redhat.com
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.
2 years, 3 months
[Bug 1890210] New: CVE-2020-15999 freetype: heap-based buffer
overflow via malformed ttf files
by bugzilla＠redhat.com
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=a3bab...
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 3 months
[Bug 1820166] New: Droid sans overrides my default CJK font
by bugzilla＠redhat.com
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.
2 years, 3 months
[Bug 1753020] New: Powerline symbols no longer align
by bugzilla＠redhat.com
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.
2 years, 5 months
[Bug 1851919] New: Pango 1.45 crashes pidgin with any link click
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1851919
Bug ID: 1851919
Summary: Pango 1.45 crashes pidgin with any link click
Product: Fedora
Version: rawhide
Status: NEW
Component: pango
Assignee: pwu(a)redhat.com
Reporter: zkabelac(a)redhat.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:
I've noticed instant crash of a pidgin - with this new pango 1.45 package.
I've downgraded to version pango-1.44.7-3.fc33 and pidgin is 'usable'
again (aka I can click on URL without getting instant core dump).
This is backtrace I'm getting on a crash:
(pidgin 2.13.0-20)
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
--Type <RET> for more, q to quit, c to continue without paging--
49 return ret;
[Current thread is 1 (Thread 0x7f2b86c61cc0 (LWP 100183))]
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#1 0x00007f2b883a78a4 in __GI_abort () at abort.c:79
#2 0x00007f2b886d5b6c in g_assertion_message
(domain=<optimized out>, file=0x7f2b88b7e19b "../pango/pango-context.c",
line=<optimized out>, func=<optimized out>, message=<optimized out>) at
../glib/gtestutils.c:2930
#3 0x00007f2b8873408f in g_assertion_message_expr
(domain=0x7f2b88b79e0d "Pango", file=0x7f2b88b7e19b
"../pango/pango-context.c", line=1435, func=0x7f2b88b7e3d0
"itemize_state_process_run", expr=<optimized out>) at ../glib/gtestutils.c:2956
#4 0x00007f2b88b603d6 in itemize_state_process_run () at
/lib64/libpango-1.0.so.0
#5 0x00007f2b88b61218 in pango_itemize_with_base_dir () at
/lib64/libpango-1.0.so.0
#6 0x00007f2b88b6a695 in pango_layout_check_lines.part () at
/lib64/libpango-1.0.so.0
#7 0x00007f2b88b6c539 in pango_layout_get_extents_internal () at
/lib64/libpango-1.0.so.0
#8 0x00007f2b88b6cac1 in pango_layout_get_pixel_size () at
/lib64/libpango-1.0.so.0
#9 0x000056100c9047f1 in gtk_imhtml_tip ()
#10 0x00007f2b8870ba51 in g_timeout_dispatch
(source=source@entry=0x56100ec326c0, callback=0x56100c9045b0
<gtk_imhtml_tip>, user_data=0x56100d93c2b0)
at ../glib/gmain.c:4800
#11 0x00007f2b8870aeaf in g_main_dispatch (context=0x56100d287540) at
../glib/gmain.c:3309
#12 g_main_context_dispatch (context=0x56100d287540) at ../glib/gmain.c:3974
#13 0x00007f2b8870b238 in g_main_context_iterate
(context=0x56100d287540, block=block@entry=1, dispatch=dispatch@entry=1,
self=<optimized out>)
at ../glib/gmain.c:4047
#14 0x00007f2b8870b553 in g_main_loop_run (loop=0x56100ea147e0) at
../glib/gmain.c:4241
#15 0x00007f2b88f37ba2 in gtk_main () at /lib64/libgtk-x11-2.0.so.0
#16 0x000056100c8bdb4c in main ()
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 5 months
[Bug 1853937] New: Inconsistent rendering of ti, tt ligatures
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1853937
Bug ID: 1853937
Summary: Inconsistent rendering of ti, tt ligatures
Product: Fedora
Version: 32
Status: NEW
Component: lato-fonts
Assignee: pikachu.2014(a)gmail.com
Reporter: james(a)ettle.org.uk
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
pikachu.2014(a)gmail.com, piotr1212(a)gmail.com
Target Milestone: ---
Classification: Fedora
Created attachment 1699956
--> https://bugzilla.redhat.com/attachment.cgi?id=1699956&action=edit
Sample renderings
The horizontal 't-crossing' strokes of the ti and tt ligatures are rendered
slightly below the x-height, in a manner that is more- or less-visible
depending on font size. It's most visible at 11pt.
Attached are samples rendered with RGB subpixel anti-aliasing, slight hinting.
The issue is visible in the 8, 11 and 14pt samples.
lato-fonts-2.015-9.fc32.noarch
freetype-2.10.1-2.fc32.x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 7 months