April 2020 - i18n-bugs - Fedora mailing-lists

[Fedora-i18n-bugs] [Bug 1790554] New: Keyboard layout of Kana Kanji wont show up
by bugzilla＠redhat.com 02 Feb '26

02 Feb '26

https://bugzilla.redhat.com/show_bug.cgi?id=1790554 Bug ID: 1790554 Summary: Keyboard layout of Kana Kanji wont show up Product: Fedora Version: rawhide Hardware: x86_64 Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: sumukher(a)redhat.com 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 Description of problem: The keyboard layout for Kana Kanji Japanese doesnt show up Version-Release number of selected component (if applicable): Fedora-Rawhide-20200112.n.0 How reproducible: Everytime Steps to Reproduce: 1. Install Fedora-Rawhide-20200112.n.0 WS from live boot 2. Open settings and navigate to Region and Language 3. Add Japanese Kana Kanji in the input source 4. Click the icon looking like an eye button which should open the keyboard layout Actual results: Doesn't show up the keyboard layout Expected results: The keyboard layout should show up like it shows up for english Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Fedora-i18n-bugs] [Bug 1683395] New: emacs-common-ddskk-20150927 is available
by bugzilla＠redhat.com 08 Oct '25

08 Oct '25

https://bugzilla.redhat.com/show_bug.cgi?id=1683395 Bug ID: 1683395 Summary: emacs-common-ddskk-20150927 is available Product: Fedora Version: rawhide Status: NEW Component: emacs-common-ddskk Keywords: FutureFeature, Triaged Assignee: dueno(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 20150927 Current version/release in rawhide: 16.2-5.fc30 URL: http://openlab.ring.gr.jp/skk/maintrunk/ 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/679/ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1813728] New: Square four dot Unicode character has incorrect glyph
by bugzilla＠redhat.com 03 Jun '23

03 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

[Fedora-i18n-bugs] [Bug 1779123] New: Pango no longer supports type1 fonts
by bugzilla＠redhat.com 26 Apr '23

26 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

[Fedora-i18n-bugs] [Bug 1767976] New: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT
by bugzilla＠redhat.com 14 Dec '22

14 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1767976 Bug ID: 1767976 Summary: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:b24defc317ee932c47b15b9c24c231f607dad274;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: rauch.christian(a)gmx.de 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.21-3.fc31 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1001.slice/user@1001.service/gnome-shell-wayland.service cmdline: ibus-daemon --panel disable -r --xim crash_function: bus_dbus_impl_connection_filter_cb executable: /usr/bin/ibus-daemon journald_cursor: s=3ad93f33cf144f27b2bc4f480d8f3f2e;i=4b9e;b=9037b22bbad44adc83ebb6c1be09e1fc;m=1975f869;t=594e3ce75700c;x=34f5463c97ecc8bd kernel: 5.3.5-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001 Potential duplicate: bug 1475710 -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Fedora-i18n-bugs] [Bug 1751061] New: Compose doesn’t work when using ibus
by bugzilla＠redhat.com 13 Dec '22

13 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1751061 Bug ID: 1751061 Summary: Compose doesn’t work when using ibus Product: Fedora Version: 31 Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: mfabian(a)redhat.com 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 I installed Fedora-Everything-netinst-x86_64-31-20190909.n.0.iso in qemu. Ibus version is: ibus-1.5.21-1.fc31.x86_64 I installed the gnome-tweaks package and set the compose key (Multi_key) to “Scroll Lock”. Configured input methods and keyboard layouts (as seen in the gnome panel) are: English (US, euro on 5) en 日本語　　　　　　　 ja 日本語（かな漢字） ja その他（Typing Booster） 🚀 I choose the "English (US, euro on 5)" keyboard layout and try to type into gedit. When pressing <Multi_key> , I see ⎄ i.e. I see U+2384 COMPOSITION SYMBOL as expected. But if I wait about a second, it disappears again. Now I type <Multi_key> <'> fast, not waiting after <Multi_key> I see ⎄' and it disappears again after about a second. <Multi_key> <'> <a> fast and I see: á After waiting for about a second, it turns into á⎄ i.e. U+2384 COMPOSITION SYMBOL is added after the á without pressing any more keys, just by waiting. This U+2384 COMPOSITION SYMBOL stays there, even if I wait more. If I continue to type <'> <a>, I finally get: áá i.e. I have produced this “áá” by typing <Multi_key> <'> <a> <'> <a>. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Fedora-i18n-bugs] [Bug 1733869] New: gettext: Getting errors in double free with msgfmt command.
by bugzilla＠redhat.com 13 Dec '22

13 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1733869 Bug ID: 1733869 Summary: gettext: Getting errors in double free with msgfmt command. Product: Fedora Version: 30 Status: NEW Component: gettext Assignee: panovotn(a)redhat.com Reporter: poyadav(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, jjanco(a)redhat.com, nphilipp(a)redhat.com, panovotn(a)redhat.com, petersen(a)redhat.com, praiskup(a)redhat.com, suanand(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Error in poc, please refer the result section for details. Version-Release number of selected component (if applicable): gettext-0.19.8.1-18.fc30.x86_64 How reproducible: Always Steps to Reproduce: 1. Clone https://github.com/CCCCCrash/POCs.git. 2. Run valgrind msgfmt poc command. 3. Observe the output. Actual results: [poyadav@localhost doublefree]$ valgrind msgfmt poc ==8072== Memcheck, a memory error detector ==8072== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==8072== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==8072== Command: msgfmt poc ==8072== ==8072== Conditional jump or move depends on uninitialised value(s) ==8072== at 0x48D9940: freea (in /usr/lib64/libgettextlib-0.19.8.1.so) ==8072== by 0x487E8EA: po_lex_charset_set (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x487E098: po_gram_parse (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x487EB9A: ??? (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x487A773: catalog_reader_parse (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x10E7C7: ??? (in /usr/bin/msgfmt) ==8072== by 0x10D8EB: ??? (in /usr/bin/msgfmt) ==8072== by 0x4AABF32: (below main) (in /usr/lib64/libc-2.29.so) ==8072== poc:17: duplicate message definition... poc:16: ...this is the location of the first definition poc:18:3: syntax error poc:18: keyword "n" unknown poc:19: end-of-line within string poc:28: duplicate message definition... poc:24: ...this is the location of the first definition poc:35: keyword "msgud_plural" unknown poc:34: missing 'msgstr' section poc:35:13: syntax error poc:40: end-of-line within string poc:46: end-of-line within string poc: warning: Charset missing in header. Message conversion to user's charset will not work. poc:42: duplicate message definition... poc:6: ...this is the location of the first definition poc:46:2: syntax error poc:46: keyword "Ep" unknown poc:47: keyword "C" unknown poc:48: keyword "s" unknown poc:49: keyword "bo" unknown poc:50: keyword "S" unknown poc:50:236: invalid control sequence poc:50:397: invalid control sequence poc:51: end-of-line within string msgfmt: too many errors, aborting ==8072== ==8072== HEAP SUMMARY: ==8072== in use at exit: 59,783 bytes in 123 blocks ==8072== total heap usage: 547 allocs, 424 frees, 99,479 bytes allocated ==8072== ==8072== LEAK SUMMARY: ==8072== definitely lost: 650 bytes in 82 blocks ==8072== indirectly lost: 0 bytes in 0 blocks ==8072== possibly lost: 0 bytes in 0 blocks ==8072== still reachable: 59,133 bytes in 41 blocks ==8072== suppressed: 0 bytes in 0 blocks ==8072== Rerun with --leak-check=full to see details of leaked memory ==8072== ==8072== Use --track-origins=yes to see where uninitialised values come from ==8072== For lists of detected and suppressed errors, rerun with: -s ==8072== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Expected results: No errors. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1771836] New: ibus not responsive on wayland with sway as windowmanager
by bugzilla＠redhat.com 01 Dec '22

01 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1771836 Bug ID: 1771836 Summary: ibus not responsive on wayland with sway as windowmanager Product: Fedora Version: 31 Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: chorn(a)redhat.com 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 Created attachment 1635626 --> https://bugzilla.redhat.com/attachment.cgi?id=1635626&action=edit strace when running ibus-wayland from a terminal in sway Description of problem: ibus not responsive on wayland with sway as windowmanager Version-Release number of selected component (if applicable): ibus-wayland-1.5.21-3.fc31.x86_64 ibus-1.5.21-3.fc31.x86_64 ibus-mozc-2.23.2815.102-8.fc31.x86_64 How reproducible: always Steps to Reproduce: 1. install Fedora31, select lxde-desktop-environment to get wayland installed 2. dnf -y install sway ibus-wayland ibus-mozc 3. useradd -m chris; passwd chris 4. Use this in the users .bashrc : [[ $(pgrep ibus-daemon) ]] || ibus-daemon --xim --daemonize -r export IMSETTINGS_INTEGRATE_DESKTOP=yes export IMSETTINGS_MODULE=ibus export QT_IM_MODULE=ibus export XMODIFIERS=@im=ibus export GTK_IM_MODULE=ibus 5. Boot system into multi-usermode, for example in setting it as default target and rebooting 6. login as user chris 7. run sway in executing 'sway' 8. get a terminal in pressing $mod + return (by default, $mod is the windows-key) 9. verify ibus-daemon is running: 'ps ax|grep ibus' 10. try to run ibuswayland: '/usr/libexec/ibus-wayland' Actual results: No input_method global Expected results: ibus-wayland should run, and I should be able to switch input method to mozc as configured with 'ibus-setup'. Additional info: - Might very well be an issue on my side.. but after trying this now for a week, taking that to bugzilla. - fcitx4 from Fedora works under sway. - When setting up ibus as above, I was never able to run ibus-wayland, and ibus did never react to attempts to switch the input method with shift+space or ctrl+space, I tried these combinations after setting them up with ibus-setup - Instead of running ibus-daemon from user .bashrc, I did run it from sway directly. Steps: mkdir ~/.config/sway cp /etc/sway/config ~/.config/sway/config echo 'exec /usr/bin/ibus-daemon --xim --daemonize' >>~/.config/sway/config The result is the same though. - When running ibus-daemon non-daemonizing from a terminal, I get this: [chris@космос ~]$ ibus-daemon -r -v (ibus-ui-gtk3:75725): IBUS-WARNING **: 15:00:43.303: panel.vala:255: If you launch KDE5 on xterm, export XDG_CURRENT_DESKTOP=KDE before launch KDE5. (ibus-ui-gtk3:75725): IBUS-WARNING **: 15:00:43.335: ibus_bus_call_sync: org.freedesktop.DBus.Properties.Get: GDBus.Error:org.freedesktop.DBus.Error.Failed: No global engine. (and ibus-daemon stays running) - I tried various terminals, for example xterm and terminator -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Fedora-i18n-bugs] [Bug 1757760] New: Hiragana to English conversion with F10 key adds unwanted letters
by bugzilla＠redhat.com 07 Jun '22

07 Jun '22

https://bugzilla.redhat.com/show_bug.cgi?id=1757760 Bug ID: 1757760 Summary: Hiragana to English conversion with F10 key adds unwanted letters Product: Fedora Version: rawhide Status: NEW Component: ibus-kkc Assignee: dueno(a)redhat.com Reporter: ykatabam(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Description of problem: When we enter an English word with consecutive double letters (e.g. assembly) in Hiragana mode and use F10 to convert into English, the double letters becomes the triple letters in some cases (e.g. asssembly). This happens irregularly, but tends to happen more often for longer words. Here are some examples: communication becomes commmunication bugzilla becomes bugzilla Pittsburgh becomes Pitttsburgh FYI, auto-correct is disabled, as auto-correct changes the input when it's not a dictionary word so it doesn't allow us to convert into English properly in hiragana mode. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Fedora-i18n-bugs] [Bug 1787124] New: [abrt] ibus-mozc: __fdelt_chk(): ibus-engine-mozc killed by SIGABRT
by bugzilla＠redhat.com 16 May '22

16 May '22

https://bugzilla.redhat.com/show_bug.cgi?id=1787124 Bug ID: 1787124 Summary: [abrt] ibus-mozc: __fdelt_chk(): ibus-engine-mozc killed by SIGABRT Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:d88e523ce263f66e445a1a6f6cd666d77fad9e05;VAR IANT_ID=matecompiz; Component: mozc Assignee: tagoh(a)redhat.com Reporter: ryutaroh2006(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, robinlee.sysu(a)gmail.com, tagoh(a)redhat.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: I don't know how or why ibuz-engine-mozc was killed by SIGABRT... Version-Release number of selected component: ibus-mozc-2.23.2815.102-8.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/dbus\x2d:1.2\x2dcom.redhat.imsettings.slice/dbus-:1.2-com.redhat.imsettings@0.service cmdline: /usr/libexec/ibus-engine-mozc --ibus crash_function: __fdelt_chk executable: /usr/libexec/ibus-engine-mozc journald_cursor: s=4479f645f2da4f17afc9f9415d05055f;i=b7c0;b=a6e351a2ff374b38832aa98ebe9457dd;m=7e0bcb9b;t=59afce7bb1367;x=508717657a4cb7e9 kernel: 5.3.16-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #6 __fdelt_chk at fdelt_chk.c:25 #7 mozc::(anonymous namespace)::IsWriteTimeout at ../../ipc/unix_ipc.cc:108 #8 mozc::(anonymous namespace)::SendMessage at ../../ipc/unix_ipc.cc:157 #9 mozc::IPCClient::Call at ../../ipc/unix_ipc.cc:328 -- You are receiving this mail because: You are on the CC list for the bug.

1 15

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

[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 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 1659748] New: Characters get deleted as you type
by bugzilla＠redhat.com 13 Oct '21

13 Oct '21

https://bugzilla.redhat.com/show_bug.cgi?id=1659748 Bug ID: 1659748 Summary: Characters get deleted as you type Product: Fedora Version: 29 Status: NEW Component: ibus-m17n Severity: high Assignee: pnemade(a)redhat.com Reporter: lohang(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com, shawn.p.huang(a)gmail.com Target Milestone: --- Classification: Fedora Description of problem: When you type Sinhala using Wijesekera keyboard layout through ibus the first character gets deleted as soon as you start typing the second character. This is similar to the bug previously reported for Fedora 28 https://bugzilla.redhat.com/show_bug.cgi?id=1617978 How reproducible: (1) Steps to Reproduce: 1. Open Libre Office Writer (6.1.2.1) 2. Switch to Sinhala; Sinhalese (wijesekera (m17n)) 3. Type keys vksIal kjSka 4. Hit space to separate the second word from the first word. And hit space at the end of the first word. Actual results: ක වීන් Expected results: ඩනිෂ්ක නවීන් Additional info: (2) When you try this with emacs the results are a little different. I am including it here assuming this is related to the same issue: This is how to reproduce with emacs: 1. Open emacs 26.1 (build 1, x86_64-redhat-linux-gnu, GTK+ Version 3.23.2) of 2018-08-13 2. Switch to Sinhala; Sinhalese (wijesekera (m17n)) 3. Type keys vksIal kjSka 4. Hit space to separate the second word from the first word. And hit space at the end of the first word. Actual results: ඩනිෂ් කනවී න් Expected results: ඩනිෂ්ක නවීන් This adds a space before the last character of the first word, not where you want the space to be. -- You are receiving this mail because: You are on the CC list for the bug.

1 49

[Fedora-i18n-bugs] [Bug 1786596] New: Vertical alignment is off with PANGO_GRAVITY_EAST and PANGO_GRAVITY_HINT_LINE
by bugzilla＠redhat.com 26 Aug '21

26 Aug '21

https://bugzilla.redhat.com/show_bug.cgi?id=1786596 Bug ID: 1786596 Summary: Vertical alignment is off with PANGO_GRAVITY_EAST and PANGO_GRAVITY_HINT_LINE Product: Fedora Version: 31 OS: Linux Status: NEW Component: pango Assignee: pwu(a)redhat.com Reporter: abetakehiko(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: Japanese chars and Latin chars in the same line do not vertically align when the pango context's gravity is set to PANGO_GRAVITY_EAST and its hint set to PANGO_GRAVITY_HINT_LINE. Version-Release number of selected component (if applicable): pango-1.44.7-1.fc31.x86_64 How reproducible: Always Steps to Reproduce: pango-view --text="あーいうえお abcde" --gravity east --gravity-hint line --font="NotoSerifJP 24" Actual results: Japanese chars and Latin chars in the same line do not vertically align. Expected results: Japanese chars and Latin chars in the same line vertically align as before. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Fedora-i18n-bugs] [Bug 1677534] New: texttopaps OOMs with 4GB text file!
by bugzilla＠redhat.com 28 Jun '21

28 Jun '21

https://bugzilla.redhat.com/show_bug.cgi?id=1677534 Bug ID: 1677534 Summary: texttopaps OOMs with 4GB text file! Product: Fedora Version: rawhide Hardware: x86_64 OS: Linux Status: NEW Component: paps Severity: high Assignee: tagoh(a)redhat.com Reporter: petersen(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: desktop-qa-list(a)redhat.com, eng-i18n-bugs(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, rhel(a)vlasiu.net, tagoh(a)redhat.com Depends On: 1635160 Target Milestone: --- Classification: Fedora (Cloned from a RHEL7 report) +++ This bug was initially created as a clone of Bug #1635160 +++ Description of problem: Trying to print with cups a 4Gb text file fail. texttopaps consume all the memory and is killed bye the system: [1023082.003989] Out of memory: Kill process xxxx (texttopaps) score 955 or sacrifice child [1023082.005120] Killed process xxxx (texttopaps) total-vm:19958848kB, anon-rss:7531872kB, file-rss:84kB, shmem-rss:0kB /usr/lib/cups/filter/texttopaps 1 user1 "example" 1 "" sample-4Gb.txt --- Additional comment from Akira TAGOH on 2018-10-03 11:54:48 SGT --- Hmm, that log says it all. I don't think OOM is a software bug. --- Additional comment from GV on 2018-10-03 13:00:48 SGT --- Of course OOM is not a software bug. Where exactly did I said that? The problem is texttopaps that allocate memory out of control. texttopaps should allocate memory, use-it, release-it. Like any sane program. The issue was not present on RHEL 6. I had printed the same file multiple times with cups on RHEL6 and it worked just fine (not sure it was texttopaps cups filter involved). Printing the file does not work on RHEL 7 and it should. The 4Gb file is a testcase for our application we develop. --- Additional comment from Jens Petersen on 2018-10-18 17:49:35 SGT --- I don't think the paps in RHEL7 is significantly different from RHEL6. As you say it could be due to changes in Cups? The cups versions in RHEL 6, 7 and Fedora are certainly quite different. Unless texttopaps really worked in RHEL6 it might make to reassign this to cups? --- Additional comment from GV on 2018-10-25 18:29:46 SGT --- Since the real computer running RHEL 6 was already scrapped, I tried to make a virtual machine using RHEL 6. Unfortunately, now I also get a crash on RHEL 6 when printing the 4GB file. I can't recall how much memory was in that computer. The virtual machine had 8Gb of memory allocated. Still, it does not matter that much. I think texttopaps have an issue and it should be fixed or at least an workaround should be available (other than 'don't print a file that large'). I'm afraid this is not a cups issue since I can reproduce the issue running the texttopaps standalone. Sincerely, Gabriel --- Additional comment from Akira TAGOH on 2018-11-16 17:59:04 SGT --- paps isn't supposed to work with large files. to support it, most of code needs to rewritten. this isn't realistic to provide an update for existing products. for a workaround, you can remove paps package (or simply remove /usr/share/cups/mime/paps.convs file) to fall back the text filter to texttops which CUPS originally provides. this should works for this issue and as long as you don't need the internationalization support for printing. Hope that helps. --- Additional comment from GV on 2018-12-07 14:03:33 SGT --- It helps. Thank you! Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1635160 [Bug 1635160] texttopaps OOMs with 4GB text file! -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1753295] New: Pango no longer supports bitmap fonts
by bugzilla＠redhat.com 25 May '21

25 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1753295 Bug ID: 1753295 Summary: Pango no longer supports bitmap fonts Product: Fedora Version: 31 Status: NEW Component: pango Assignee: tagoh(a)redhat.com Reporter: jsbillin(a)umich.edu 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 bitmap fonts, so font packages like terminus-fonts and ucs-miscfixed-fonts no longer appear in GNOME applications that use pango, such as Terminal. If you did a dnf system-upgrade from Fedora 30 and were using a bitmap font like Terminus, all your terminals will show the rectangular placeholders the first time you start a terminal. Bitmap fonts like terminus and ucs-miscfixed are much easier to read in a terminal since they are pixel perfect. If Fedora 31 is going to disable support for bitmap fonts, it needs to be announced and the package maintainers of those bitmap font packages are going to need to find a way to convert their fonts. Version-Release number of selected component (if applicable): pango-1.44.6-1.fc31.x86_64 How reproducible: always Steps to Reproduce: 1. install 'terminus-fonts' 2. Start GNOME terminal 3. Open Terminal Preferences 4. Attempt to change the font to Terminus font Actual results: If you upgraded from Fedora 30 and had Terminus fonts as the default font, the first time you launch Terminal, all the text will be the rectangular placeholders. If you search for the Terminus font in the preferences, you won't be able to find it. Expected results: Use the Terminus font as usual Additional info: It appears that pango switched from using FreeType to HarfBuzz, which only supports truetype. I rebuilt the Fedora 30 pango package (1.43) for Fedora 31, downgraded it, and now my terminals are fine showing my bitmap fonts. -- You are receiving this mail because: You are on the CC list for the bug.

1 127

[Fedora-i18n-bugs] [Bug 1711646] New: Scriptlet error when updating through SSH
by bugzilla＠redhat.com 09 May '21

09 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1711646 Bug ID: 1711646 Summary: Scriptlet error when updating through SSH Product: Fedora Version: 30 Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: dreua(a)posteo.de 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 Description of problem: When I update or reinstall ibus-1.5.20-4.fc30 over SSH, dnf outputs the error "X11 connection rejected because of wrong authentication.". This is caused by https://src.fedoraproject.org/rpms/ibus/blob/master/f/ibus.spec#_338 running `sudo ibus write-cache --system` results in the same error when called over SSH. Version-Release number of selected component (if applicable): ibus-1.5.20-4.fc30 How reproducible: Always over SSH, never when using the terminal directly on the machine. Steps to Reproduce: 1. Reinstall or update to ibus-1.5.20-4.fc30 Actual results: Running scriptlet: ibus-1.5.20-4.fc30.x86_64 X11 connection rejected because of wrong authentication. X11 connection rejected because of wrong authentication. Verifying : ibus-1.5.20-4.fc30.x86_64 Expected results: Running scriptlet: ibus-1.5.20-4.fc30.x86_64 Verifying : ibus-1.5.20-4.fc30.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Fedora-i18n-bugs] [Bug 1749943] New: pango contain header with wrong hb.h include
by bugzilla＠redhat.com 08 Mar '21

08 Mar '21

https://bugzilla.redhat.com/show_bug.cgi?id=1749943 Bug ID: 1749943 Summary: pango contain header with wrong hb.h include Product: Fedora Version: rawhide Status: NEW Component: pango Assignee: tagoh(a)redhat.com Reporter: vascom2(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: I am try to build eiskaltdcpp and it fsilrd with error: BUILDSTDERR: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory BUILDSTDERR: 28 | #include <hb.h> BUILDSTDERR: | ^~~~~~ Full build log https://kojipkgs.fedoraproject.org/work/tasks/5226/37235226/build.log Version-Release number of selected component (if applicable): pango-1.44.6-1.fc32 How reproducible: Always. As I see this line was added in pango 1.44. But harfbuzz's hb.h in Fedora placed at /usr/include/harfbuzz/ Need to solve it for build other packages. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1807534] New: pyzy requires Python 2 to build
by bugzilla＠redhat.com 18 Jan '21

18 Jan '21

https://bugzilla.redhat.com/show_bug.cgi?id=1807534 Bug ID: 1807534 Summary: pyzy requires Python 2 to build Product: Fedora Version: rawhide Status: NEW Component: pyzy Assignee: pwu(a)redhat.com Reporter: pviktori(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, pwu(a)redhat.com Blocks: 1803205 (BRPY27) Target Milestone: --- Classification: Fedora Python 2 reached upstream end-of-life in January 2020. In Fedora Rawhide, it's now provided from the compat package `python27`. Packages that only use Python 2 at build time, like pyzy, had a general exception to keep using it in Fedora 31. Now, the dependency should be removed. Let us know if you need any help investigating or removing the dependency. (There are dozens of packages like this, so we didn't investigate this one thoroughly. We assume you know the package best.) If it's possible that the dependency won't be removed in Fedora 33. Please request a FESCo exception. You can refer to the exception for mercurial as an example: https://pagure.io/fesco/issue/2243 It's good to mention: - What is the reason for the Python 2 build dependency? - What are the upstream/community plans/timelines regarding Python 2? - What is the guidance for porting the build to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?) If you need anything from us, or something is unclear, please mention it here. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1803205 [Bug 1803205] Tracking: Packages BuildRequiring python27 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Fedora-i18n-bugs] [Bug 1707001] New: Ibus-pinyin ERROR
by bugzilla＠redhat.com 12 Jan '21

12 Jan '21

https://bugzilla.redhat.com/show_bug.cgi?id=1707001 Bug ID: 1707001 Summary: Ibus-pinyin ERROR Product: Fedora Version: 30 Hardware: All OS: Linux Status: NEW Component: ibus-pinyin Severity: urgent Assignee: pwu(a)redhat.com Reporter: 1990konger(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: The input method is incorrect and cannot be recognized correctly. The text to be entered is required. For example, 'nihao' should be right, '你好'. Now enter 'nihao' to show 'niha o'.Unrecognized what you need 'ni' is a word. 'hao' is a word. 'ha' is a word but the display is wrong at this time and cannot be selected. Unable to recognize 'hao'. Affect all input suggestions to withdraw to the old version Version-Release number of selected component (if applicable): Name : ibus-pinyin Version : 1.5.0 Release : 16.fc30 How reproducible: 'nihao' is meaning is 'Hello' 'niha o', it is an error Steps to Reproduce: 1.All Chinese input is wrong Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Fedora-i18n-bugs] [Bug 1787190] New: Windows+ Space shortcut opened KRunner instead of switch keyboard (ibus) in KDE plasma
by bugzilla＠redhat.com 04 Nov '20

04 Nov '20

https://bugzilla.redhat.com/show_bug.cgi?id=1787190 Bug ID: 1787190 Summary: Windows+ Space shortcut opened KRunner instead of switch keyboard (ibus) in KDE plasma Product: Fedora Version: 31 Status: NEW Component: kf5-plasma Keywords: i18n Assignee: me(a)dvratil.cz Reporter: aalam(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, jgrulich(a)redhat.com, kde-sig(a)lists.fedoraproject.org, me(a)dvratil.cz, rdieter(a)gmail.com, than(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: after updating KDE with Fedora 31, Windows+Space is opening 'Krunner', but not switching keyboard (which is default shortcut for ibus keybaord switch). Krunner is not running with Alt+F2 Krunner is running with Windows +F2 Version-Release number of selected component (if applicable): plasma-desktop-5.17.4-1.fc31.x86_64 plasma-nm-openswan-5.17.4-1.fc31.x86_64 plasma-desktop-doc-5.17.4-1.fc31.noarch plasma-browser-integration-5.17.4-1.fc31.x86_64 plasma-workspace-5.17.4-1.fc31.x86_64 plasma-nm-vpnc-5.17.4-1.fc31.x86_64 plasma-workspace-common-5.17.4-1.fc31.x86_64 plasma-nm-5.17.4-1.fc31.x86_64 plasma-workspace-geolocation-5.17.4-1.fc31.x86_64 plasma-milou-5.17.4-1.fc31.x86_64 plasma-integration-5.17.4-1.fc31.x86_64 plasma-discover-5.17.4-1.fc31.x86_64 plasma-nm-openvpn-5.17.4-1.fc31.x86_64 plasma-breeze-5.17.4-1.fc31.x86_64 plasma-drkonqi-5.17.4-1.fc31.x86_64 kdeplasma-addons-5.17.4-1.fc31.x86_64 plasma-user-manager-5.17.4-1.fc31.x86_64 plasma-pk-updates-0.3.2-4.fc31.x86_64 plasma-nm-l2tp-5.17.4-1.fc31.x86_64 plasma-nm-openconnect-5.17.4-1.fc31.x86_64 kf5-plasma-5.64.0-1.fc31.x86_64 plasma-workspace-geolocation-libs-5.17.4-1.fc31.x86_64 plasma-lookandfeel-fedora-5.17.4-1.fc31.noarch plasma-nm-pptp-5.17.4-1.fc31.x86_64 plasma-workspace-libs-5.17.4-1.fc31.x86_64 plasma-systemsettings-5.17.4-1.fc31.x86_64 kde-settings-plasma-31.0-1.fc31.noarch glibc-2.30-8.fc31.x86_64 glibc-langpack-pa-2.30-8.fc31.x86_64 glibc-langpack-en-2.30-8.fc31.x86_64 glibc-all-langpacks-2.30-8.fc31.x86_64 glibc-common-2.30-8.fc31.x86_6 ibus-setup-1.5.21-5.fc31.noarch ibus-gtk3-1.5.21-5.fc31.x86_64 ibus-m17n-1.4.1-3.fc31.x86_64 ibus-gtk2-1.5.21-5.fc31.x86_64 ibus-qt-1.3.3-22.fc31.x86_64 ibus-libs-1.5.21-5.fc31.x86_64 ibus-1.5.21-5.fc31.x86_64 How reproducible: Everytime after updating Fedora 31 KDE desktop with latest package Steps to Reproduce: 1. Fresh install KDE Plasma with language (Punjabi, Hindi, any language using iBus) 2. try to input by switching keyboard (ibus) pressing Windows+Space 3. sudo dnf update 4. Reboot 5. try to input by switching keyboard (ibus) pressing Windows+Space Actual results: Opened 'KRunner' Expected results: input keyboard layout should switch with 'Windows+space'. Krunner should run with 'Alt+F2', which is not working Additional info: before updating, opened system setting -> Shortcut -> Global Shortcut - There is NO krunner' After update, system setting -> Shortcut -> Global Shortcut -> Krunner (this is something new) -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1703849] New: [pango] pango-view fails for backend ft2 because of missing dependency on ImageMagick
by bugzilla＠redhat.com 21 Oct '20

21 Oct '20

https://bugzilla.redhat.com/show_bug.cgi?id=1703849 Bug ID: 1703849 Summary: [pango] pango-view fails for backend ft2 because of missing dependency on ImageMagick Product: Fedora Version: 29 Hardware: x86_64 OS: Linux Status: NEW Component: pango Assignee: tagoh(a)redhat.com Reporter: jfrieben(a)hotmail.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: Using pango-view with backend ft2 in a current Fedora 29 Workstation installation fails because pango-view tries to launch the display utility from ImageMagick which has not been pulled in as a dependency. Version-Release number of selected component (if applicable): pango-1.42.4-2.fc29 How reproducible: Always Steps to Reproduce: 1. Launch GNOME session of a current Fedora 29 Workstation installation. 2. Run 'pango-view --backend=ft2 -t PANGO'. Actual results: Utility pango-view aborts with the error message: "pango-view: When running ImageMagick 'display' command: Failed to execute child process “display” (No such file or directory)" Expected results: Utility pango-view displays the sample text. Additional info: - Installing package ImageMagick prior to running pango-view ensures correct execution. Therefore, adding ImageMagick as a requirement of package pango solves this issue. - It is probably preferable to patch pango-view such that it calls "gm display" from package GraphicsMagick and to pull in the latter instead of ImageMagick. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Fedora-i18n-bugs] [Bug 1797926] New: Korean Baekmuk fonts does not map missing glyphs to id 0
by bugzilla＠redhat.com 21 Oct '20

21 Oct '20

https://bugzilla.redhat.com/show_bug.cgi?id=1797926 Bug ID: 1797926 Summary: Korean Baekmuk fonts does not map missing glyphs to id 0 Product: Fedora Version: 31 Hardware: All OS: All Status: NEW Component: baekmuk-ttf-fonts Severity: medium Assignee: pwu(a)redhat.com Reporter: matt(a)nightrealms.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 Target Milestone: --- Classification: Fedora From https://bugs.chromium.org/p/chromium/issues/detail?id=1042994 "So the font, does not map missing characters to a glyph id 0, missing glyph id, but instead maps it to a glyph named '.null', glyph id 12505." The result is that when Chrome tries to display the Korean characters listed at http://www.alanwood.net/unicode/hangul-jamo-extended-b.html the characters come out as blank. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1747731] New: [abrt] ibus-libpinyin: pinyin::MemoryChunk::ensure_has_more_space(unsigned long)(): ibus-engine-libpinyin killed by SIGABRT
by bugzilla＠redhat.com 29 Sep '20

29 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1747731 Bug ID: 1747731 Summary: [abrt] ibus-libpinyin: pinyin::MemoryChunk::ensure_has_more_space(unsigned long)(): ibus-engine-libpinyin killed by SIGABRT Product: Fedora Version: 30 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:ebfdf9e0e88e902f1a9d6c72641712e29b0aca46; Component: ibus-libpinyin Assignee: pwu(a)redhat.com Reporter: dcdrake42(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, pwu(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Seemed to occur while typing immediately after changing from English to Chinese input while using the browser version of Facebook Messenger (Chromium). Version-Release number of selected component: ibus-libpinyin-1.11.1-1.fc30 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: pinyin::MemoryChunk::ensure_has_more_space(unsigned long) executable: /usr/libexec/ibus-engine-libpinyin journald_cursor: s=9c254645106a4209b447b2a1893383ad;i=189698;b=c5ac01a80c3a439eb3832a0a5ed88e02;m=202900d17;t=59173a5b8af7b;x=99dc5a43153fc974 kernel: 5.2.9-200.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #7 pinyin::MemoryChunk::ensure_has_more_space(unsigned long) at ../../src/include/memory_chunk.h:122 #8 pinyin::MemoryChunk::ensure_has_space(unsigned long) at ../../src/include/memory_chunk.h:92 #9 pinyin::MemoryChunk::set_content(unsigned long, void const*, unsigned long) at ../../src/include/memory_chunk.h:286 #10 pinyin::MemoryChunk::append_content(void const*, unsigned long) at ../../src/include/memory_chunk.h:302 #11 pinyin::merge_single_gram(pinyin::SingleGram*, pinyin::SingleGram const*, pinyin::SingleGram const*) at ngram.cpp:322 #12 pinyin::PhoneticLookup<2, 3>::search_bigram2(_GPtrArray*, int, int, _GArray**) at ../src/include/memory_chunk.h:86 #13 pinyin::PhoneticLookup<2, 3>::get_nbest_match(_GArray*, pinyin::PhoneticKeyMatrix const*, pinyin::ForwardPhoneticConstraints const*, pinyin::NBestMatchResults*) at ../src/storage/phrase_index.h:731 #14 PY::FullPinyinEditor::insert(int) at PYPFullPinyinEditor.cc:56 #15 PY::PinyinEngine::processKeyEvent(unsigned int, unsigned int, unsigned int) at /usr/include/c++/9/bits/shared_ptr_base.h:1020 -- You are receiving this mail because: You are on the CC list for the bug.

1 13

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs April 2020