[Fedora-i18n-bugs] [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, 1 month
[Fedora-i18n-bugs] [Bug 1938091] New: Kasumi-unicode: Check for only hiragana letters in reading column fails as user can input non-hiragana characters in it.
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1938091
Bug ID: 1938091
Summary: Kasumi-unicode: Check for only hiragana letters in
reading column fails as user can input non-hiragana
characters in it.
Product: Fedora
Version: 34
Status: NEW
Component: kasumi
Keywords: i18n
Assignee: tagoh(a)redhat.com
Reporter: bbarve(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1762901
--> https://bugzilla.redhat.com/attachment.cgi?id=1762901&action=edit
kasumi unicode non-hiragana letters
Description of problem: In the kasumi-unicode dict, there is a message which
pops-up if user tries to input non-hiragana characters like kanji or katakana.
However this check is not consistent as user can input other non-hiragana input
like English words, letters, numbers etc. This can be done using any mode in
Anthy like hiragana or direct input. Attaching screenshot for reference.
Version-Release number of selected component (if applicable):
Fedora 34
kasumi-unicode-2.5.33.fc34
How reproducible:
always
Steps to Reproduce:
1. Run /usr/bin/kasumi-unicode from terminal
2. click on add
3. add a jpn word in any script under first column i.e. words
4. hit tab and enter to input in the second column i.e. reading
5. In hiragana mode, input 'k' and hit enter
6. click on save.
Actual results:
user is ablke to input non-hiragana input in reading column
Expected results:
The check for non-hiragana input should be consistent.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 1 month
[Bug 1969644] New: xkeyboard-config-2.33 is available
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1969644
Bug ID: 1969644
Summary: xkeyboard-config-2.33 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: xkeyboard-config
Keywords: FutureFeature, Triaged
Assignee: peter.hutterer(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org,
negativo17(a)gmail.com, peter.hutterer(a)redhat.com,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 2.33
Current version/release in rawhide: 2.32-3.fc35
URL: https://www.freedesktop.org/wiki/Software/XKeyboardConfig/
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/5191/
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 2 months
[Bug 1993670] New: segfault with pango-view assert in cairo
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1993670
Bug ID: 1993670
Summary: segfault with pango-view assert in cairo
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
Description of problem:
1. This one works
$ pango-view --nodisplay --text "abc"
2. This one doesn't
$ pango-view --no-display --text "abc"
pango-view: cairo-hash.c:217: _cairo_hash_table_destroy: Assertion
`hash_table->live_entries == 0' failed.
Aborted (core dumped)
So pango-view triggers an assertion in Cairo.
Version-Release number of selected component (if applicable):
$ dnf repoquery --installed pango
pango-0:1.48.7-1.fc34.i686
pango-0:1.48.7-1.fc34.x86_64
How reproducible:
always
Steps to Reproduce:
1. see 1. of description above
2. see 2. of description above
Actual results:
segfault
Expected results:
no segfault
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 3 months
[Fedora-i18n-bugs] [Bug 1919760] New: [abrt] ibus: invoke_get_property_in_idle_cb(): ibus-ui-gtk3 killed by SIGABRT
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1919760
Bug ID: 1919760
Summary: [abrt] ibus: invoke_get_property_in_idle_cb():
ibus-ui-gtk3 killed by SIGABRT
Product: Fedora
Version: 33
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:1550d568515be5da0d8fa0ca9eb0b2e4d8db85bc;
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: alain.thiaville(a)sfr.fr
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-1.5.23-2.fc33
Additional info:
reporter: libreport-2.14.0
backtrace_rating: 4
cgroup:
0::/user.slice/user-1001.slice/user@1001.service/dbus\x2d:1.3\x2dcom.redhat.imsettings.slice/dbus-:1.3-com.redhat.imsettings@0.service
cmdline: /usr/libexec/ibus-ui-gtk3
crash_function: invoke_get_property_in_idle_cb
executable: /usr/libexec/ibus-ui-gtk3
journald_cursor:
s=9fdab79de00a4521972b23b84b3df8a6;i=9604;b=1a89d997ec324b54ade433d343bd315b;m=b4c8678a9;t=5b9b18c4cc4b5;x=749fe5d392007729
kernel: 5.10.9-201.fc33.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1001
xsession_errors:
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 4 months
[Fedora-i18n-bugs] [Bug 1910907] New: [abrt] ibus-kkc: gee_array_list_real_get(): ibus-engine-kkc killed by SIGABRT
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1910907
Bug ID: 1910907
Summary: [abrt] ibus-kkc: gee_array_list_real_get():
ibus-engine-kkc killed by SIGABRT
Product: Fedora
Version: 33
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:88de9664ac0f50184e02ce3df98d857f4c9334f0;VAR
IANT_ID=workstation;
Component: ibus-kkc
Assignee: dueno(a)redhat.com
Reporter: ramot(a)ramottamado.dev
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-kkc-1.5.22-14.fc33
Additional info:
reporter: libreport-2.14.0
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service
cmdline: /usr/libexec/ibus-engine-kkc --ibus
crash_function: gee_array_list_real_get
executable: /usr/libexec/ibus-engine-kkc
journald_cursor:
s=b9a02946f72241c5826b5804d8ded9b6;i=13b91a;b=f6f1121902224e3c95d41e6edabda311;m=72e3e2286;t=5b749367c7aab;x=4eeb00e5e71d231f
kernel: 5.9.14-200.fc33.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 4 months
[Fedora-i18n-bugs] [Bug 1919932] New: Culmus Hebrew fonts aren't usable by TeXLive after installation
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1919932
Bug ID: 1919932
Summary: Culmus Hebrew fonts aren't usable by TeXLive after
installation
Product: Fedora
Version: 33
Status: NEW
Component: culmus-fonts
Assignee: petersen(a)redhat.com
Reporter: nikita(a)leshenko.net
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pnemade(a)redhat.com,
psatpute(a)redhat.com, vishalvijayraghavan(a)gmail.com
Target Milestone: ---
Classification: Fedora
Created attachment 1750496
--> https://bugzilla.redhat.com/attachment.cgi?id=1750496&action=edit
Basic Hebrew document
Description of problem:
On a clean Fedora 33 after installing texlive, babel-hebrew, and
tex-fonts-hebrew, I
can't use pdflatex to render a Hebrew document. Detailed steps to reproduce and
a possible fix are provided below.
Version-Release number of selected component (if applicable):
texlive 9:2020-34.fc33
texlive-babel-hebrew 9:svn30273.2.3h-34.fc33
tex-fonts-hebrew 0.1-33.fc33
How reproducible: Always
Steps to Reproduce:
1. Start a new Fedora 33 container: podman run -it fedora:33
2. dnf install texlive texlive-babel-hebrew tex-fonts-hebrew
3. Try to render hello.tex document attached to this bug report (this is a
basic
Hebrew document).
\documentclass{article}
\usepackage[utf8x]{inputenc}
\usepackage[english,hebrew]{babel}
\begin{document}
שלום!
\end{document}
Actual results:
We get the following error message:
!pdfTeX error: pdflatex (file rdavid): Font rdavid at 600 not found
==> Fatal error occurred, no output PDF file produced!
Full log is at first.log.
Expected results:
Document is rendered :)
Additional info:
We need two steps to resolve the problem here. I'm not sure if these steps are
the idiomatic way to fix the issue, but it worked for me...
The first issue that that culmus.map is not included in the pdflatex.map, even
though culmus.map is enabled in /etc/texlive/web2c/updmap.cfg. I was able to
solve it with
- updmap-sys --syncwithtrees
- updmap-sys
to recreate the map file. It would be nice the Culmus will do this by default
as
part of the installation. (Another temporary per-document solution is to add
\pdfmapfile{culmus.map} to the Hebrew document.)
Now if we re-run pdflatex we get a new error:
!pdfTeX error: pdflatex (file DavidCLM-Medium.pfa): cannot open Type 1 font
file for reading
==> Fatal error occurred, no output PDF file produced!
The full log is in second.log.
There are multiple ways around this problem:
1. Note that /usr/share/texmf/fonts/type1/public/ has a broken symlink to
culmus. Even if we fix the symlink to point to /usr/share/fonts/culmus/, it
doesn't work because pdflatex doesn't seem to follow directory symlinks. But
if we actually create a directory and symlink fonts individually, it will
work, like this:
mkdir /usr/share/texmf/fonts/type1/public/culmus2
for i in /usr/share/fonts/culmus/*; do ln $i
/usr/share/texmf/fonts/type1/public/culmus2/${i##*/}; done
2. A more "general" fix is to edit /etc/texlive/web2c/texmf.cnf instead and set
OSFONTDIR to /usr/share/fonts/, but it seems like this change extends beyond
Culmus so I'm not sure how practical is it to edit OSFONTDIR as part of
installation.
After building the map file and teaching latex to find Type1 Culmus fonts the
Hebrew document can compile successfully.
I hope that it will be possible to adjust the Culmus package so that Hebrew
latex works out of the box.
Thanks! I'm available for questions and clarifications.
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 4 months
[Fedora-i18n-bugs] [Bug 1937240] New: [abrt] kasumi-unicode: emission_find(): kasumi-unicode killed by SIGSEGV
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1937240
Bug ID: 1937240
Summary: [abrt] kasumi-unicode: emission_find(): kasumi-unicode
killed by SIGSEGV
Product: Fedora
Version: 34
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:33f7835124f3940bfb5f3043f97e4bebd869f6b1;VAR
IANT_ID=workstation;
Component: kasumi
Assignee: tagoh(a)redhat.com
Reporter: mfabian(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
kasumi-unicode-2.5-33.fc34
Additional info:
reporter: libreport-2.14.0
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service
cmdline: kasumi-unicode
crash_function: emission_find
executable: /usr/bin/kasumi-unicode
journald_cursor:
s=aeb2461fa27a41febb2b69e0c1f19a49;i=2a3ca;b=02ae636d7bd94d8399fe1a589a2cc54d;m=e5e7d209d;t=5bd2a7d5e7076;x=eaacb353af23ab38
kernel: 5.11.3-300.fc34.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (1 frames)
#0 emission_find at ../gobject/gsignal.c:893
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 4 months