i18n-bugs April 2021

i18n-bugs@lists.fedoraproject.org

1 participants
91 discussions

[Fedora-i18n-bugs] [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

[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 03 Mar '22

03 Mar '22

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.

1 18

[Fedora-i18n-bugs] [Bug 1923676] New: emacs-lookup: FTBFS in Fedora rawhide/f34
by bugzilla＠redhat.com 24 Jan '22

24 Jan '22

https://bugzilla.redhat.com/show_bug.cgi?id=1923676 Bug ID: 1923676 Summary: emacs-lookup: FTBFS in Fedora rawhide/f34 Product: Fedora Version: rawhide Status: NEW Component: emacs-lookup Assignee: dueno(a)redhat.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Blocks: 1868278 (F34FTBFS) Target Milestone: --- Classification: Fedora emacs-lookup failed to build from source in Fedora rawhide/f34 https://koji.fedoraproject.org/koji/taskinfo?taskID=60913717 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild Please fix emacs-lookup at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, emacs-lookup will be orphaned. Before branching of Fedora 35, emacs-lookup will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails… Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1868278 [Bug 1868278] (F34FTBFS) - Fedora 34 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Fedora-i18n-bugs] [Bug 1919760] New: [abrt] ibus: invoke_get_property_in_idle_cb(): ibus-ui-gtk3 killed by SIGABRT
by bugzilla＠redhat.com 30 Nov '21

30 Nov '21

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.

1 5

[Fedora-i18n-bugs] [Bug 1910907] New: [abrt] ibus-kkc: gee_array_list_real_get(): ibus-engine-kkc killed by SIGABRT
by bugzilla＠redhat.com 30 Nov '21

30 Nov '21

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.

1 3

[Fedora-i18n-bugs] [Bug 1919932] New: Culmus Hebrew fonts aren't usable by TeXLive after installation
by bugzilla＠redhat.com 30 Nov '21

30 Nov '21

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.

1 8

[Fedora-i18n-bugs] [Bug 1937240] New: [abrt] kasumi-unicode: emission_find(): kasumi-unicode killed by SIGSEGV
by bugzilla＠redhat.com 27 Nov '21

27 Nov '21

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.

1 1

[Fedora-i18n-bugs] [Bug 1934320] New: Led indicator of FnLock doesnot work...on 15ARH05H
by bugzilla＠redhat.com 26 Nov '21

26 Nov '21

https://bugzilla.redhat.com/show_bug.cgi?id=1934320 Bug ID: 1934320 Summary: Led indicator of FnLock doesnot work...on 15ARH05H Product: Fedora Version: 33 Hardware: x86_64 OS: Linux Status: NEW Component: xkeyboard-config Severity: medium Assignee: peter.hutterer(a)redhat.com Reporter: saurab.gyawali032(a)gmail.com 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 Description of problem:My Fn + Esc key activates the FNLOCK key which has a led indicator in it but it either remain on or off on its own..... While booting if it is on it remain on all the time and viceversa....... I just want to make this correct....While hitting Fn +Ecs can you help me to make the led indicator responsive Version-Release number of selected component (if applicable): I don't know anything How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Fedora-i18n-bugs] [Bug 1815510] New: Input hangul -> cursor becomes ahead in preedit
by bugzilla＠redhat.com 24 Nov '21

24 Nov '21

https://bugzilla.redhat.com/show_bug.cgi?id=1815510 Bug ID: 1815510 Summary: Input hangul -> cursor becomes ahead in preedit Product: Fedora Version: 32 Hardware: x86_64 OS: Linux Status: NEW Component: ibus-hangul Assignee: pwu(a)redhat.com Reporter: sangu.fedora(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, pwu(a)redhat.com, shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Input hangul -> cursor becomes ahead in preedit Version-Release number of selected component (if applicable): 1.5.3-2.fc32.x86_64 How reproducible: always in haungul input state Steps to Reproduce: 1. gedit starts 2. switch hangul 3. input hangul Actual results: Expected results: Additional info: ibus-1.5.22-4.fc32.x86_64 gtk3-3.24.14-1.fc32.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1851919] New: Pango 1.45 crashes pidgin with any link click
by bugzilla＠redhat.com 24 Nov '21

24 Nov '21

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.

1 12

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs April 2021