May 2020 - i18n-bugs - Fedora mailing-lists

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

07 May '24

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 23

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

02 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 25 Apr '23

25 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 1842034] 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=1842034 Bug ID: 1842034 Summary: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT Product: Fedora Version: 32 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:b24defc317ee932c47b15b9c24c231f607dad274;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: niki.guldbrand(a)gmail.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 Version-Release number of selected component: ibus-1.5.22-7.fc32 Additional info: reporter: libreport-2.13.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-42.slice/session-c1.scope cmdline: ibus-daemon --panel disable -r --xim crash_function: bus_dbus_impl_connection_filter_cb executable: /usr/bin/ibus-daemon journald_cursor: s=f592520f518043e0bf22bcb1059f85fa;i=5f0d;b=e5641f6c2ed84e629455c7ec8e6a1276;m=1c9e25e;t=5a6dbe50f3604;x=b9e38dca02503832 kernel: 5.6.15-300.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 42 Potential duplicate: bug 1475710 -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[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 30 Nov '22

30 Nov '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 1832351] New: Macintosh keyboard variants not available
by bugzilla＠redhat.com 24 Mar '22

24 Mar '22

https://bugzilla.redhat.com/show_bug.cgi?id=1832351 Bug ID: 1832351 Summary: Macintosh keyboard variants not available Product: Fedora Version: 32 Hardware: x86_64 Status: NEW Component: xkeyboard-config Severity: medium Assignee: peter.hutterer(a)redhat.com Reporter: mthoemme(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, john.j5live(a)gmail.com, 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: I do not have any variants for Macintosh available when trying to change the keyboard layout via the GUI (Region & Language Settings). Trying to manually set the keymap in the locale works for the VC keymap, but not for the X11 Layout. It will set VC keymap to "de-mac" or "de_mac" respectively, leave the X11 Layout at "de" localectl set-keymap de-mac Digging even deeper, the following commands all yield the same errors: localectl set-x11-keymap de-mac localectl set-x11-keymap de_mac localectl set-x11-keymap de macintosh de_mac All yield: "Failed to set keymap: Specified keymap cannot be compiled, refusing as invalid." Version-Release number of selected component (if applicable): dnf info xkeyboard-config Last metadata expiration check: 1:03:51 ago on Mi 06 Mai 2020 15:54:00 CEST. Installed Packages Name : xkeyboard-config Version : 2.29 Release : 1.fc32 Architecture : noarch Size : 5.5 M Source : xkeyboard-config-2.29-1.fc32.src.rpm Repository : @System From repo : anaconda Summary : X Keyboard Extension configuration data URL : http://www.freedesktop.org/wiki/Software/XKeyboardConfig License : MIT Description : This package contains configuration data used by the X Keyboard Extension (XKB), : which allows selection of keyboard layouts when using a graphical interface. How reproducible: Happens consistently. I'm on a fresh Fedora 32 install. Steps to Reproduce: 1. localectl set-x11-keymap de macintosh de_mac Actual results: "Failed to set keymap: Specified keymap cannot be compiled, refusing as invalid." Expected results: Successfully sets the keyboard layout to a Macintosh variant. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[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 1832098] New: Due to socket path changes ibus not working in F32 Wayland for qt4 apps
by bugzilla＠redhat.com 26 May '21

26 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1832098 Bug ID: 1832098 Summary: Due to socket path changes ibus not working in F32 Wayland for qt4 apps Product: Fedora Version: 32 Status: NEW Component: ibus-qt Severity: high Assignee: tfujiwar(a)redhat.com Reporter: petersen(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: Due to changes in socket path for Wayland, ibus input does not work for qt4 apps under Wayland in Fedora 32. https://github.com/ibus/ibus-qt/pull/5 Version-Release number of selected component (if applicable): ibus-qt-1.3.3-22.fc31 How reproducible: 100% -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Fedora-i18n-bugs] [Bug 1836327] New: Hangul text commit and key forward don't preserve order sometimes
by bugzilla＠redhat.com 25 May '21

25 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1836327 Bug ID: 1836327 Summary: Hangul text commit and key forward don't preserve order sometimes Product: Fedora Version: 32 Hardware: x86_64 OS: Linux Status: NEW Component: ibus Severity: medium Assignee: tfujiwar(a)redhat.com Reporter: edward.park0203(a)gmail.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: Hangul text commit and key forward don't preserve order sometimes Version-Release number of selected component (if applicable): 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 8

[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 1830709] New: Invalid metainfo files
by bugzilla＠redhat.com 16 May '21

16 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1830709 Bug ID: 1830709 Summary: Invalid metainfo files Product: Fedora Version: 32 Status: NEW Component: google-noto-fonts Assignee: petersen(a)redhat.com Reporter: mohd.akram(a)outlook.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, psatpute(a)redhat.com, pwu(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Metainfo files provided by the package are deemed invalid by appstream. Version-Release number of selected component (if applicable): 20181223-7.fc32 How reproducible: Always. Steps to Reproduce: 1. appstreamcli validate /usr/share/metainfo/google-noto-sans-sinhala-vf.metainfo.xml Actual results: E: google-noto-sans-sinhala-vf:~: font-no-font-data E: google-noto-sans-sinhala-vf:4: cid-is-not-rdns google-noto-sans-sinhala-vf I: google-noto-sans-sinhala-vf:~: font-description-missing E: google-noto-sans-sinhala-vf:~: component-summary-missing E: google-noto-sans-sinhala-vf:~: component-name-missing E: google-noto-sans-sinhala-vf:~: extends-not-allowed I: google-noto-sans-sinhala-vf:4: cid-contains-hyphen google-noto-sans-sinhala-vf Validation failed: errors: 5, infos: 2 Expected results: Validation was successful. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[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 03 Nov '20

03 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 20 Oct '20

20 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 20 Oct '20

20 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

[Fedora-i18n-bugs] [Bug 1821595] New: [abrt] ibus: bus_server_init(): ibus-daemon killed by SIGTRAP
by bugzilla＠redhat.com 28 Sep '20

28 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1821595 Bug ID: 1821595 Summary: [abrt] ibus: bus_server_init(): ibus-daemon killed by SIGTRAP Product: Fedora Version: 32 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:e70f4ca101def3ac6f2be9e0173bd33fef6ba0ee;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: ricky.tigg(a)gmail.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 Version-Release number of selected component: ibus-1.5.22-4.fc32 Additional info: reporter: libreport-2.12.0 backtrace_rating: 3 cgroup: 0::/user.slice/user-979.slice/user@979.service/gnome-shell-wayland.service cmdline: ibus-daemon --panel disable -r crash_function: bus_server_init executable: /usr/bin/ibus-daemon journald_cursor: s=697aadd3b95f4a93ac72e13a9075b53a;i=22db;b=ac0f25036df04c609b191269d1daabed;m=4e4dab7;t=5a2499b1481cd;x=62df3cc33cd4848a kernel: 5.6.0-0.rc5.git0.2.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 979 Potential duplicate: bug 1785276 -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Fedora-i18n-bugs] [Bug 1766971] New: Default monospace font Amharic is weird, makes gnome-terminal look weird
by bugzilla＠redhat.com 23 Sep '20

23 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1766971 Bug ID: 1766971 Summary: Default monospace font Amharic is weird, makes gnome-terminal look weird Product: Fedora Version: 31 Status: NEW Component: fontconfig Assignee: tagoh(a)redhat.com Reporter: mfabian(a)redhat.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 Created attachment 1630570 --> https://bugzilla.redhat.com/attachment.cgi?id=1630570&action=edit Screenshot.png [mfabian@localhost ~]$ fc-match monospace:lang=de DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book" [mfabian@localhost ~]$ fc-match monospace:lang=ja NotoSansCJK-Regular.ttc: "Noto Sans Mono CJK JP" "Regular" [mfabian@localhost ~]$ fc-match monospace:lang=en DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book" [mfabian@localhost ~]$ fc-match monospace:lang=am FreeSerif.ttf: "FreeSerif" "Regular" [mfabian@localhost ~]$ cat /etc/fedora-release Fedora release 31 (Thirty One) [mfabian@localhost ~]$ Maybe there is no monospace font for Amharic ☹ This makes gnome-terminal look weird in am_ET.UTF-8 locale, see screenshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1781372] New: [abrt] ibus: invoke_set_property_in_idle_cb(): ibus-daemon killed by SIGABRT
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1781372 Bug ID: 1781372 Summary: [abrt] ibus: invoke_set_property_in_idle_cb(): ibus-daemon killed by SIGABRT Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:75f531706153dfdd85ddf0be1692b26d7940fb0d;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: daniel(a)demus.dk 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-4.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cmdline: ibus-daemon --panel disable -r --xim crash_function: invoke_set_property_in_idle_cb executable: /usr/bin/ibus-daemon journald_cursor: s=c4148406e0464aa6b028a69dbd858103;i=2332cb;b=9b80660c325a4e97b03f82a722e4c4df;m=49832e189;t=59943b5e4b38d;x=d732a9d65ff2477 kernel: 5.3.14-300.fc31.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 13

[Fedora-i18n-bugs] [Bug 1752858] New: Combinations Reph (र्श्व) not rendering correctly with Harfbuzz in gedit
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1752858 Bug ID: 1752858 Summary: Combinations Reph (र्श्व) not rendering correctly with Harfbuzz in gedit Product: Fedora Version: 31 Status: NEW Component: lohit-devanagari-fonts Assignee: petersen(a)redhat.com Reporter: psatpute(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, psatpute(a)redhat.com, sshedmak(a)redhat.com, vishalvijayraghavan(a)gmail.com Target Milestone: --- Classification: Fedora Created attachment 1615839 --> https://bugzilla.redhat.com/attachment.cgi?id=1615839&action=edit Image showing rendering issue Description of problem: Combination र्श्व is not rendering correctly in gedit/harfbuzz. But it works properly in Firefox Version-Release number of selected component (if applicable): lohit-devanagari-fonts 2.95.4-9 harfbuzz-2.6.0-1 How reproducible: Evertime Steps to Reproduce: 1. Open Terminal 2. Type commng: hb-view /usr/share/fonts/lohit-devanagari/Lohit-Devanagari.ttf र्श्व 3. Observe result Actual results: Reph not getting form. Expected results: Expected Reph should get formed. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1730242] New: unable to see ibus-sayura in Region panel
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1730242 Bug ID: 1730242 Summary: unable to see ibus-sayura in Region panel Product: Fedora Version: rawhide Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: pnemade(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: On Fedora 30 updated Silverblue system, I layered ibus-sayura package. Then tried to add it via Region panel. I cannot see it listed there. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Layer ibus-sayura package 2. reboot or you can ibus restart 3. try to add Sayura input using Region panel Actual results: There is no entry for Sayura in Region panel Expected results: It should allow to select Sayura Additional info: As I did not see Sayura, I executed "ibus write-cache" Then, I executed [parag@f30sb ~]$ ibus read-cache|grep -i sayura <description>Sayura Component</description> <exec>/usr/libexec/ibus-engine-sayura --ibus</exec> <textdomain>ibus-sayura</textdomain> <path mtime="0" >/usr/share/ibus/component/sayura.xml</path> <name>sayura</name> <longname>Sayura</longname> <description>Sayura Input Method</description> <icon>/usr/share/ibus-sayura/icons/ibus-sayura.png</icon> Then, [parag@f30sb ~]$ ibus list-engine|grep -i sayura no output for above command -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1689745] New: [abrt] ibus-libpinyin: pinyin_save(): ibus-engine-libpinyin killed by SIGSEGV
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1689745 Bug ID: 1689745 Summary: [abrt] ibus-libpinyin: pinyin_save(): ibus-engine-libpinyin killed by SIGSEGV Product: Fedora Version: 30 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:cb822be7ac46c50ce113ca1671deec6e2f6c4599; Component: ibus-libpinyin Assignee: pwu(a)redhat.com Reporter: robinlee.sysu(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: Crash when updating system Version-Release number of selected component: ibus-libpinyin-1.11.0-2.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: pinyin_save executable: /usr/libexec/ibus-engine-libpinyin journald_cursor: s=cc3b4d7aa103497a99d675649b9ae013;i=94c7;b=13573ad620e541ff8cacc1ad1ceca0c3;m=eea6a32;t=584549ca4b236;x=245f7212fc098115 kernel: 5.0.0-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 pinyin_save at pinyin.cpp:736 #1 PY::LibPinyinBackEnd::clearPinyinUserData at PYLibPinyin.cc:307 #2 PY::PinyinConfig::valueChanged at /usr/include/c++/9/bits/basic_string.h:2297 #3 PY::LibPinyinConfig::valueChangedCallback at /usr/include/c++/9/bits/char_traits.h:300 #8 g_settings_real_change_event at ../gio/gsettings.c:391 #9 ffi_call_unix64 at ../src/x86/unix64.S:76 #10 ffi_call at ../src/x86/ffi64.c:525 #11 g_cclosure_marshal_generic_va at ../gobject/gclosure.c:1614 #12 _g_closure_invoke_va at ../gobject/gclosure.c:873 #15 settings_backend_path_changed at ../gio/gsettings.c:466 Potential duplicate: bug 1649100 -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Fedora-i18n-bugs] [Bug 1758852] New: [abrt] ibus-libpinyin: pinyin_save(): ibus-engine-libpinyin killed by SIGSEGV
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1758852 Bug ID: 1758852 Summary: [abrt] ibus-libpinyin: pinyin_save(): ibus-engine-libpinyin killed by SIGSEGV Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:cb822be7ac46c50ce113ca1671deec6e2f6c4599;VAR IANT_ID=workstation; Component: ibus-libpinyin Assignee: pwu(a)redhat.com Reporter: neoh.ys(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 Version-Release number of selected component: ibus-libpinyin-1.11.1-2.fc31 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/gnome-shell-wayland.service cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: pinyin_save executable: /usr/libexec/ibus-engine-libpinyin journald_cursor: s=d0bfbd77a305433ab20ca800db00de73;i=1c977;b=a298c5cc72eb401d9e2263a3bc469e87;m=163503887a;t=59436eaaf2c10;x=ab8ddda419eaa95f kernel: 5.3.2-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 pinyin_save at pinyin.cpp:736 #1 PY::LibPinyinBackEnd::clearPinyinUserData at PYLibPinyin.cc:307 #2 PY::PinyinConfig::valueChanged at /usr/include/c++/9/bits/basic_string.h:2300 #3 PY::LibPinyinConfig::valueChangedCallback at /usr/include/c++/9/bits/char_traits.h:300 #4 g_cclosure_marshal_VOID__STRINGv at ../gobject/gmarshal.c:1462 #5 _g_closure_invoke_va at ../gobject/gclosure.c:873 #8 g_settings_real_change_event at ../gio/gsettings.c:392 #9 _g_cclosure_marshal_BOOLEAN__POINTER_INTv at ../gio/gmarshal-internal.c:426 #10 _g_closure_invoke_va at ../gobject/gclosure.c:873 #13 settings_backend_path_changed at ../gio/gsettings.c:467 Potential duplicate: bug 1689745 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Fedora-i18n-bugs] [Bug 1738159] New: tomoe depends on Python 2
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1738159 Bug ID: 1738159 Summary: tomoe depends on Python 2 Product: Fedora Version: rawhide Status: NEW Component: tomoe Assignee: pwu(a)redhat.com Reporter: lbalhar(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dingyichen(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, pwu(a)redhat.com, tagoh(a)redhat.com Blocks: 1698500 (F31_PY2REMOVAL) Target Milestone: --- Classification: Fedora Python 2.7 will reach end-of-life in January 2020, over 9 years after it was released. This falls within the Fedora 31 lifetime. Packages that depend on Python 2 are being switched to Python 3 or removed from Fedora: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#In… Python 2 will be retired in Fedora 32: https://fedoraproject.org/wiki/Changes/RetirePython2 To help planning, we'd like to know the plans for tomoe's future. Specifically: - What is the reason for the Python2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?) - What are the upstream/community plans/timelines regarding Python 3? - What is the guidance for porting 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?) This bug is filed semi-automatically, and might not have all the context specific to tomoe. If you need anything from us, or something is unclear, please mention it here. Thank you. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1698500 [Bug 1698500] F31 Mass Python 2 Package Removal -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Fedora-i18n-bugs] [Bug 1797132] New: [abrt] ibus-hangul: hangul_ic_select_keyboard(): ibus-engine-hangul killed by SIGSEGV
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1797132 Bug ID: 1797132 Summary: [abrt] ibus-hangul: hangul_ic_select_keyboard(): ibus-engine-hangul killed by SIGSEGV Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:b29b9b3ef26017f5e61f13f4a450123ebc924ac9;VAR IANT_ID=workstation; Component: ibus-hangul Assignee: pwu(a)redhat.com Reporter: josephjang(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 Version-Release number of selected component: ibus-hangul-1.5.3-1.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/gnome-shell-x11.service cmdline: /usr/libexec/ibus-engine-hangul --ibus crash_function: hangul_ic_select_keyboard executable: /usr/libexec/ibus-engine-hangul journald_cursor: s=3365f1612aba4253b3c17698db629f15;i=a34c;b=acd031cfd150446bb42d2ee5431f7d80;m=205c0e9f7b;t=59d72706f4bbb;x=454895e6dbb1675d kernel: 5.4.12-200.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 hangul_ic_select_keyboard at hangulinputcontext.c:1626 #1 settings_changed at engine.c:1941 #6 g_settings_real_change_event at ../gio/gsettings.c:392 #7 _g_cclosure_marshal_BOOLEAN__POINTER_INTv at ../gio/gmarshal-internal.c:426 #8 _g_closure_invoke_va at ../gobject/gclosure.c:873 #11 settings_backend_path_changed at ../gio/gsettings.c:467 #12 g_settings_backend_invoke_closure at ../gio/gsettingsbackend.c:273 #18 ibus_main at ibusshare.c:301 #19 start_component at main.c:116 -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Fedora-i18n-bugs] [Bug 1779586] New: [abrt] ibus-table: g_settings_schema_get_value(): python3.7 killed by SIGTRAP
by bugzilla＠redhat.com 15 Sep '20

15 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1779586 Bug ID: 1779586 Summary: [abrt] ibus-table: g_settings_schema_get_value(): python3.7 killed by SIGTRAP Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:004184fdd6fa1b8e4e49df86a1c57ac5847dd204;VAR IANT_ID=workstation; Component: ibus-table Assignee: mfabian(a)redhat.com Reporter: mfabian(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dingyichen(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, kent.neo(a)gmail.com, mfabian(a)redhat.com, pwu(a)redhat.com, shawn.p.huang(a)gmail.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-table-1.9.21-5.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-10030.slice/session-2.scope cmdline: /usr/bin/python3 /usr/share/ibus-table/engine/main.py --profile --ibus crash_function: g_settings_schema_get_value executable: /usr/bin/python3.7 journald_cursor: s=c0d79f79862b4941981f04495d4f8245;i=8bf219;b=16aabd8bda544929bc6ad65c9e902988;m=37114158;t=5985239b337cb;x=955981e5440c8c5d kernel: 5.3.12-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 10030 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #4 g_settings_schema_get_value at ../gio/gsettingsschema.c:973 #6 g_settings_schema_key_init at ../gio/gsettingsschema.c:1253 #7 g_settings_set_value at ../gio/gsettings.c:1578 #8 ffi_call_unix64 at ../src/x86/unix64.S:76 #9 ffi_call at ../src/x86/ffi64.c:525 #10 pygi_invoke_c_callable at ../gi/pygi-invoke.c:690 #11 pygi_function_cache_invoke at ../gi/pygi-cache.c:863 #12 pygi_callable_info_invoke at ../gi/pygi-invoke.c:770 #13 _wrap_g_callable_info_invoke at ../gi/pygi-invoke.c:770 #14 _Py_CheckRecursionLimit -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Fedora-i18n-bugs] [Bug 1672442] New: Bug that will not accept input from keyboard
by bugzilla＠redhat.com 02 Sep '20

02 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1672442 Bug ID: 1672442 Summary: Bug that will not accept input from keyboard Product: Fedora Version: 29 OS: Linux Status: NEW Component: ibus Severity: medium Assignee: tfujiwar(a)redhat.com Reporter: qqke6wd9k(a)apricot.ocn.ne.jp 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 input characters, sometimes this bug occurs, the PC will not accept input from the keyboard morever. Since it accepts mouse operation, logout and shutdown are possible. When I log out and re-login, PC is able to accept only direct input (English). Also, the IME icon on the task bar is lost. It will also be impossible to switch input modes. I am a Japanese user, but when after login, I cannot enter Japanese characters. After this bug occurrence, only English characters can be entered. Version-Release number of selected component (if applicable): How reproducible: everyday Steps to Reproduce: 1.Open an application that can enter letters (eg gedit or Firefox) 2.keep typing characters until this bug occurs. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Fedora-i18n-bugs] [Bug 1750891] New: font cache not getting update on Silverblue 31?
by bugzilla＠redhat.com 01 Aug '20

01 Aug '20

https://bugzilla.redhat.com/show_bug.cgi?id=1750891 Bug ID: 1750891 Summary: font cache not getting update on Silverblue 31? Product: Fedora Version: 31 Status: NEW Component: fontconfig Assignee: tagoh(a)redhat.com Reporter: pnemade(a)redhat.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: I have this system state [parag@localhost ~]$ rpm-ostree status State: idle AutomaticUpdates: disabled Deployments: ● ostree://fedora:fedora/31/x86_64/silverblue Version: 31.20190909.n.0 (2019-09-09T08:24:14Z) BaseCommit: 093a07e18c0514e47e978c9c33ef73a2615117db343e0eef7218c298b1e3502c GPGSignature: Valid signature by 7D22D5867F2A4236474BF7B850CB390B3C3359C4 LayeredPackages: gedit gnome-tweaks hunspell-hi langpacks-hi libreoffice-core ostree://fedora:fedora/31/x86_64/silverblue Version: 31.20190909.n.0 (2019-09-09T08:24:14Z) BaseCommit: 093a07e18c0514e47e978c9c33ef73a2615117db343e0eef7218c298b1e3502c GPGSignature: Valid signature by 7D22D5867F2A4236474BF7B850CB390B3C3359C4 LayeredPackages: gedit gnome-tweaks hunspell-hi libreoffice-core [parag@localhost ~]$ rpm-ostree db diff ostree diff commit from: rollback deployment (0ad271d38c5aa4e1ce194ea625f83862d2c317774d96ba9b94d53c5324133265) ostree diff commit to: booted deployment (61f7aea98b458e53e42e85131e62ad7c84f80592676f28949cc5aa411e34ff55) Added: glibc-langpack-hi-2.30-1.fc31.x86_64 google-noto-sans-devanagari-ui-vf-fonts-20181223-6.fc31.noarch google-noto-sans-devanagari-vf-fonts-20181223-6.fc31.noarch hyphen-hi-1:0.7.0-14.fc31.noarch langpacks-core-hi-2.0-6.fc31.noarch langpacks-hi-2.0-6.fc31.noarch libreoffice-help-hi-1:6.3.1.2-1.fc31.x86_64 libreoffice-langpack-hi-1:6.3.1.2-1.fc31.x86_64 samyak-devanagari-fonts-1.2.2-22.fc31.noarch samyak-fonts-common-1.2.2-22.fc31.noarch [parag@localhost ~]$ fc-list :lang=hi /usr/share/fonts/lohit-devanagari/Lohit-Devanagari.ttf: Lohit Devanagari:style=Regular /usr/share/fonts/google-droid/DroidSansDevanagari-Regular.ttf: Droid Sans:style=Regular [parag@localhost ~]$ Version-Release number of selected component (if applicable): fontconfig-2.13.92-2.fc31.x86_64 How reproducible: always Steps to Reproduce: 1. on F31, install any langpacks which will install additional fonts packages like langpacks-hi 2. execute fc-list :lang=hi 3. Actual results: "fc-list :lang=hi" output remained same Expected results: "fc-list :lang=hi" should included rencently installed font packages as well Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Fedora-i18n-bugs] [Bug 1770450] New: Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
by bugzilla＠redhat.com 23 Jun '20

23 Jun '20

https://bugzilla.redhat.com/show_bug.cgi?id=1770450 Bug ID: 1770450 Summary: Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample .conf", line 6: unknown element "reset-dirs" Product: Fedora Version: 30 Status: NEW Component: fontconfig Assignee: tagoh(a)redhat.com Reporter: lhaastdaiz(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 When upgrading to fontconfig-2.13.1-9.fc30.x86_64, dnf emits this warning: Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs" $ cat -n /usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf 1 <?xml version="1.0"?> 2 <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> 3 <fontconfig> 4 <description>Re-define fonts dirs sample</description> 5 6 <reset-dirs /> 7 <dir prefix="xdg">fonts</dir> 8 9 </fontconfig> -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Fedora-i18n-bugs] [Bug 1811258] New: unicode-ucd-13.0.0 is available
by bugzilla＠redhat.com 16 Jun '20

16 Jun '20

https://bugzilla.redhat.com/show_bug.cgi?id=1811258 Bug ID: 1811258 Summary: unicode-ucd-13.0.0 is available Product: Fedora Version: rawhide Status: NEW Component: unicode-ucd Keywords: FutureFeature, Triaged Assignee: petersen(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com, petersen(a)redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 13.0.0 Current version/release in rawhide: 12.1.0-3.fc32 URL: http://www.unicode.org/Public/zipped/ 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/5045/ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Fedora-i18n-bugs] [Bug 1831977] New: [abrt] ibus: g_log_structured_standard(): ibus-ui-gtk3 killed by SIGTRAP
by bugzilla＠redhat.com 03 Jun '20

03 Jun '20

https://bugzilla.redhat.com/show_bug.cgi?id=1831977 Bug ID: 1831977 Summary: [abrt] ibus: g_log_structured_standard(): ibus-ui-gtk3 killed by SIGTRAP Product: Fedora Version: 32 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:0afd953949188f1bddce50d5e2657a3a81d27368; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: david.hu.2035(a)gmail.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 Version-Release number of selected component: ibus-1.5.22-4.fc32 Additional info: reporter: libreport-2.12.0 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-ui-gtk3 crash_function: g_log_structured_standard executable: /usr/libexec/ibus-ui-gtk3 journald_cursor: s=fa59e6e57b244c4f9e3c365e162af59d;i=45b5;b=323ad363289c43b29f37dfc2b19b233b;m=21c478c5;t=5a4f2bce67d95;x=ef98704bed73462c kernel: 5.6.8-300.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 xsession_errors: -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Fedora-i18n-bugs] [Bug 1842162] New: F33FailsToInstall: python3-woffTools
by bugzilla＠redhat.com 01 Jun '20

01 Jun '20

https://bugzilla.redhat.com/show_bug.cgi?id=1842162 Bug ID: 1842162 Summary: F33FailsToInstall: python3-woffTools Product: Fedora Version: rawhide Status: NEW Component: woffTools Assignee: sshedmak(a)redhat.com Reporter: igor.raits(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com, sshedmak(a)redhat.com Blocks: 1803235 (F33FailsToInstall) Target Milestone: --- Classification: Fedora Hello, Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (ignatenkobrain(a)fedoraproject.org) Your package (woffTools) Fails To Install in Fedora 33: can't install python3-woffTools: - nothing provides python(abi) = 3.8 needed by python3-woffTools-0.1-0.28.20160211git.fc32.noarch If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails…) your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/rawhide-gating/multi-builds/ Thanks! Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1803235 [Bug 1803235] (F33FailsToInstall) - Fedora 33 Fails To install Tracker -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 30 May '20

30 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bug 1806272 depends on bug 1839164, which changed state. Bug 1839164 Summary: DejaVu font issue https://bugzilla.redhat.com/show_bug.cgi?id=1839164 What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Resolution|--- |ERRATA -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 500110] [Indic][CodePoint]Press backspace key it delete the whole char and letter before it
by bugzilla＠redhat.com 26 May '20

26 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=500110 Ben Cotton <bcotton(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|POST |CLOSED Resolution|--- |EOL Last Closed|2017-08-08 11:39:04 |2020-05-26 18:36:40 --- Comment #50 from Ben Cotton <bcotton(a)redhat.com> --- Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1035486] Cantarell text renders fuzzy
by bugzilla＠redhat.com 26 May '20

26 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1035486 Ben Cotton <bcotton(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |EOL Last Closed| |2020-05-26 14:53:28 --- Comment #56 from Ben Cotton <bcotton(a)redhat.com> --- Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1839492] New: [abrt] system-config-language: load(): repo.py:580:load:dnf.exceptions.RepoError: Failed to download metadata for repo 'virtualbox': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
by bugzilla＠redhat.com 26 May '20

26 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1839492 Bug ID: 1839492 Summary: [abrt] system-config-language: load(): repo.py:580:load:dnf.exceptions.RepoError: Failed to download metadata for repo 'virtualbox': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried Product: Fedora Version: 32 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:818e8a52dde4427ab3d94b65fa3510f0209df37f;VAR IANT_ID=workstation; Component: system-config-language Assignee: pnemade(a)redhat.com Reporter: kardi.mg(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, nav007(a)gmail.com, pnemade(a)redhat.com, psatpute(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: system-config-language-3.5.0-4.fc32 Additional info: reporter: libreport-2.13.1 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/gnome-shell-wayland.service cmdline: /usr/bin/python3 /usr/share/system-config-language/system-config-language.py crash_function: load exception_type: RuntimeError executable: /usr/share/system-config-language/system-config-language.py interpreter: python3-3.8.2-2.fc32.x86_64 kernel: 5.6.8-300.fc32.x86_64 runlevel: N 5 type: Python3 uid: 0 Truncated backtrace: repo.py:580:load:dnf.exceptions.RepoError: Failed to download metadata for repo 'virtualbox': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/dnf/repo.py", line 573, in load ret = self._repo.load() File "/usr/lib64/python3.8/site-packages/libdnf/repo.py", line 328, in load return _repo.Repo_load(self) RuntimeError: Failed to download metadata for repo 'virtualbox': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/share/system-config-language/language_gui.py", line 319, in ok_btn installed = self.instpkg.install_packages3(dlang) File "/usr/share/system-config-language/install_packages3.py", line 147, in install_packages3 self.base.fill_sack() File "/usr/lib/python3.8/site-packages/dnf/base.py", line 392, in fill_sack self._add_repo_to_sack(r) File "/usr/lib/python3.8/site-packages/dnf/base.py", line 137, in _add_repo_to_sack repo.load() File "/usr/lib/python3.8/site-packages/dnf/repo.py", line 580, in load raise dnf.exceptions.RepoError(str(e)) dnf.exceptions.RepoError: Failed to download metadata for repo 'virtualbox': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried Local variables in innermost frame: self: <Repo virtualbox> ret: False msg: "Errors during downloading metadata for repository 'virtualbox':\n - Status code: 404 for http://download.virtualbox.org/virtualbox/rpm/fedora/32/x86_64/repodata/rep… (IP: 92.122.172.94)" failure: 'Status code: 404 for http://download.virtualbox.org/virtualbox/rpm/fedora/32/x86_64/repodata/rep… (IP: 92.122.172.94)' -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 25 May '20

25 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 --- Comment #27 from Akira TAGOH <tagoh(a)redhat.com> --- (In reply to Peng Wu from comment #24) > Maybe nautilus uses similar code like hexchat, but fontconfig > returns different fonts format randomly. To clarify, it's not random. the default weight is Regular and bitmap version of Terminus supports that weight despite not supporting Regular weight in OTB. see: $ FC_DEBUG=3 fc-match Terminus ... Font 3958 Pattern has 27 elts (size 27) family: "Terminus"(w) familylang: "en"(w) style: "Regular"(w) stylelang: "en"(w) fullname: "Terminus Regular"(w) fullnamelang: "en"(w) slant: 0(i)(w) weight: 100(f)(w) width: 100(f)(w) pixelsize: 12(f)(w) 18(f)(w) 22(f)(w) 28(f)(w) 16(f)(w) 14(f)(w) 20(f)(w) 24(f)(w) 32(f)(w) spacing: 100(i)(w) foundry: "UNKN"(w) antialias: False(w) file: "/usr/share/fonts/terminus-fonts/Terminus.otb"(w) index: 0(i)(w) outline: False(w) scalable: False(w) charset: 0000: 00000000 ffffffff ffffffff 7fffffff 00000000 ffffffff ffffffff ffffffff 0001: ffffffff ffffffff ffffffff ffffffff 6005c040 00e00000 001fe000 f031fffc 0002: 0f000000 008c0000 0b100000 00040000 00040000 38000000 3b0000c0 00000000 0003: 00001dff 00000200 00000000 00000000 ffffd7f0 fffffffb 00227fff 007f0000 0004: ffffffff ffffffff ffffffff 00000c0c 3fff0000 0fcfcc3f ffff8007 033ffffc 0005: 00000000 00000000 00000000 00000000 00000000 00000000 ffff0000 000007ff 001e: 00003000 00f00000 000000ff 00003000 00000000 33000000 00003c00 03000030 0020: ffffffff 560d0047 00000000 fff30000 05ff7fff 00005480 00000000 00000000 0021: 2460c004 00200054 00000000 00000000 003f0000 08200150 003f1800 00000000 0022: c67c3ff9 000007a0 00000100 00000c33 000000cc 00000020 0000000c 00000000 0023: 02010f05 00000003 00000000 00000000 f8000000 3c00fbff 00010000 00000000 0024: 00003e00 00000010 00000000 00000000 00000000 00000000 00000000 00000000 0025: ffffff0f ffffffff ffff0fff ffffffff ffcfffff 14445001 03008c51 00000000 0026: 00000000 1c000000 00000005 00000c69 00000000 00000000 00000000 00000000 0027: 01980000 00000000 00000000 00000000 00000000 00000000 00000000 00000f00 0028: ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff 002e: 00000000 00001000 00000000 00000000 00000000 00000000 00000000 00000000 00e0: 00000000 00000000 00000000 00000000 00000000 000f0007 00000000 00000000 00f6: 00000000 00000000 00000000 00000000 00000000 40000000 00000000 00000000 00ff: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 20000000 (w) lang: aa|af|av|ay|az-az|ba|bm|be|bg|bi|bin|br|bs|bua|ca|ce|ch|chm|co|cs|cv|da|de|el|en|eo|es|et|eu|fi|fj|fo|fr| fur|fy|gd|gl|gn|gv|haw|he|ho|hr|hu|ia|ig|id|ie|ik|io|is|it|kaa|ki|kk|kl|kum|kv|kw|ky|la|lb|lez|ln|lt|lv|mg|mh|mi|mk|mo| mt|nb|nds|nl|nn|no|nr|nso|ny|oc|om|os|pl|pt|rm|ro|ru|sah|se|sel|sh|sk|sl|sm|sma|smj|smn|sms|so|sq|sr|ss|st|sv|sw|tg|tk| tl|tn|to|tr|ts|tt|tw|tyv|uk|uz|vo|vot|wa|wen|wo|xh|yap|yi|zu|ak|an|crh|csb|fat|fil|hsb|ht|jv|kj|ku-tr|kwm|lg|li|mn-mn|m s|na|ng|nv|pap-an|pap-aw|rn|rw|sc|sg|sn|su|ty|za(w) fontversion: 65536(i)(w) fontformat: "TrueType"(w) decorative: False(w) postscriptname: "Terminus"(w) color: False(w) symbol: False(w) variable: False(w) fonthashint: False(w) ... weight: 20000 80(i)(s), 100(f)(w) ... Score 0 0 0 0 0 0 0 0 0 2000 1001 0 0 0 0 500 0 0 20000 0 0 0 0 0 0 2.14742e+12 ... Font 3960 Pattern has 28 elts (size 28) family: "Terminus"(w) familylang: "en"(w) style: "Regular"(w) stylelang: "en"(w) fullname: "Terminus Regular"(w) fullnamelang: "en"(w) slant: 0(i)(w) weight: 80(f)(w) width: 100(f)(w) pixelsize: 12(f)(w) spacing: 110(i)(w) foundry: "xos4"(w) antialias: False(w) file: "/usr/share/fonts/terminus-fonts-legacy-x11/ter-112n.pcf.gz"(w) index: 0(i)(w) outline: False(w) scalable: False(w) charset: 0000: ffffffff ffffffff ffffffff ffffffff dffe5ffd ffffffff ffffffff ffffffff (w) lang: aa|ay|bi|br|ch|da|de|en|es|eu|fj|fo|fur|fy|gd|gl|gv|ho|ia|id|ie|io|is|it|lb|mg|nb|nds|nl|nn|no|nr|oc|om|p t|rm|sma|smj|so|sq|ss|st|sv|sw|tl|ts|uz|vo|wa|xh|yap|zu|an|fil|ht|jv|kj|kwm|li|ms|ng|pap-an|pap-aw|rn|rw|sc|sg|sn|su|za (w) fontversion: 0(i)(w) fontformat: "PCF"(w) decorative: False(w) postscriptname: "Terminus"(w) color: False(w) symbol: False(w) variable: False(w) fonthashint: False(w) ... weight: 0 80(i)(s), 80(f)(w) ... Score 0 0 0 0 0 0 0 0 0 2000 1001 0 0 0 0 500 0 0 0 0 0 0 0 0 0 2.14748e+12 Again, look at this: Score 0 0 0 0 0 0 0 0 0 2000 1001 0 0 0 0 500 0 0 20000 0 0 0 0 0 0 2.14742e+12 Score 0 0 0 0 0 0 0 0 0 2000 1001 0 0 0 0 500 0 0 0 0 0 0 0 0 0 2.14748e+12 Only difference in score is weight. if requirements is "Terminus" only, this behavior *is* correct. The problem here would be either or all of: * [font] No Regular weight for OTB * [font] Lying style as Regular despite being Medium weight (Bug#1839689) * [apps] No fontformat=truetype,cff in query despite not supporting legacy bitmap format In fact, these queries works fine: $ fc-match Terminus:weight=medium Terminus.otb: "Terminus" "Regular" $ fc-match Terminus:fontformat=truetype,cff Terminus.otb: "Terminus" "Regular" -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 25 May '20

25 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1827905 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1827905 [Bug 1827905] Terminus Italic variant only shows as unicode hex code glyphs -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 25 May '20

25 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 --- Comment #26 from Andrew Obuchowicz <aobuchow(a)redhat.com> --- (In reply to Peng Wu from comment #24) > Maybe nautilus uses similar code like hexchat, but fontconfig > returns different fonts format randomly. > > Andrew Obuchowicz, could you try to delete ter-*.pcf.gz files, > and re-generate the fontconfig cache using `fc-cache -fvr`? > > I delete the ter-*.pcf.gz files, and re-generate the fontconfig > system cache and user cache, maybe also re-login, it seems > nautilus works with "Terminus Regular". I deleted the ter-*.pcf.gz files in /usr/share/fonts/terminus, and ran fc-cache -fvr. While I was logged in, most of KDE Plasma's text became messed up however this was fixed when I logged out and logged in. Unfortunately, Nautilus (now renamed to Files?) still shows Glyphs even thought I have "Terminus Regular" selected as my GTK system font in lxappearance. HOWEVER, when I check my ~/.config/gtk-3.0/settings.ini, I can see that Terminus regular is not actually set. Instead, Terminus Medium is being set. [Settings] gtk-button-images=1 gtk-cursor-theme-name=Adwaita gtk-cursor-theme-size=0 gtk-enable-event-sounds=1 gtk-enable-input-feedback-sounds=1 gtk-font-name=Terminus Medium 12 <---------------------- gtk-icon-theme-name=breeze-dark-red gtk-menu-images=1 gtk-modules=appmenu-gtk-module gtk-shell-shows-menubar=1 gtk-theme-name=Abrus-dark gtk-toolbar-icon-size=GTK_ICON_SIZE_LARGE_TOOLBAR gtk-toolbar-style=GTK_TOOLBAR_BOTH gtk-xft-antialias=1 gtk-xft-hinting=0 gtk-xft-hintstyle=hintnone gtk-xft-rgba=rgb Keep me updated, I'm eager to see this fixed :D (And will help test any fixes needed!). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1836675] New: degree symbol "°" is broken
by bugzilla＠redhat.com 25 May '20

25 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1836675 Bug ID: 1836675 Summary: degree symbol "°" is broken Product: Fedora Version: 32 Status: NEW Component: unicode-ucd Assignee: petersen(a)redhat.com Reporter: ltfkyu(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com, petersen(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1689449 --> https://bugzilla.redhat.com/attachment.cgi?id=1689449&action=edit url workaround example (\°) Description of problem: degree symbol is broken, this makes keyboard slow, can causes stuck scrolling and affect screen colors. How reproducible: any time Expected results: degree symbol can't affect keyboard responsiveness, scrolling speed and colors of screen Additional info: "\°" typed in url bar appears to work around the visible problem https://bugzilla.redhat.com/show_bug.cgi?id=1674486 :) -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 25 May '20

25 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 --- Comment #25 from Akira TAGOH <tagoh(a)redhat.com> --- Hmm, interesting. PCF files weighted as Regular like ter-[1-9c-gik]*.pcf.gz was converted from the same source of BDF files. there might be some idea there to have *Regular* otb fonts. BTW putting "Regular" into style for current Terminus*.otb is completely wrong. that is Medium as the weight property indicates it is 100. plus, when applications doesn't specify any weight property into query, the default value will be Regular (80). but no Regular weight available in Terminus*.otb. I'll file a separate bug for that. So if you do "fc-match Terminus", the best font will be bitmap fonts and no synthetic emboldening supported for them. thus, hex code glyphs. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 25 May '20

25 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 Peng Wu <pwu(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(pwu(a)redhat.com) | --- Comment #24 from Peng Wu <pwu(a)redhat.com> --- Akira TAGOH, the ter-u12n.bdf file contains 'WEIGHT_NAME "Medium"', I think its weight is Medium in the source font. Maybe nautilus uses similar code like hexchat, but fontconfig returns different fonts format randomly. Andrew Obuchowicz, could you try to delete ter-*.pcf.gz files, and re-generate the fontconfig cache using `fc-cache -fvr`? I delete the ter-*.pcf.gz files, and re-generate the fontconfig system cache and user cache, maybe also re-login, it seems nautilus works with "Terminus Regular". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 24 May '20

24 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 Akira TAGOH <tagoh(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(pwu(a)redhat.com) --- Comment #23 from Akira TAGOH <tagoh(a)redhat.com> --- Peng Wu, Why was the weight of Terminus.otb changed to 100 (Medium)? the original weight should be 80 (Regular). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 24 May '20

24 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 --- Comment #22 from Andrew Obuchowicz <aobuchow(a)redhat.com> --- Created attachment 1691592 --> https://bugzilla.redhat.com/attachment.cgi?id=1691592&action=edit KDE font selection dialog KDE seems to be handling this better, or at least differently. Note the [xos4]. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 24 May '20

24 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 --- Comment #21 from Andrew Obuchowicz <aobuchow(a)redhat.com> --- Created attachment 1691591 --> https://bugzilla.redhat.com/attachment.cgi?id=1691591&action=edit Other versions (non-italics) of Terminus look fine -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 24 May '20

24 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 --- Comment #20 from Andrew Obuchowicz <aobuchow(a)redhat.com> --- Created attachment 1691590 --> https://bugzilla.redhat.com/attachment.cgi?id=1691590&action=edit Italics font broken in GTK font selection dialog (lxappearance) This might be redundant and more related to Bug 1827905, but I figured I'd mention it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 24 May '20

24 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 --- Comment #19 from Andrew Obuchowicz <aobuchow(a)redhat.com> --- Created attachment 1691589 --> https://bugzilla.redhat.com/attachment.cgi?id=1691589&action=edit Firefox (and HexChat) seem to handle the font better, and aren't broken. Learning why these applications aren't completely broken could be useful in finding a temporary workaround (even if it would be on a per-application basis). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 24 May '20

24 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 --- Comment #18 from Andrew Obuchowicz <aobuchow(a)redhat.com> --- Created attachment 1691588 --> https://bugzilla.redhat.com/attachment.cgi?id=1691588&action=edit GTK apps are broken This is noteworthy because, although only the italics version of the font seems to be glyphs/boxes, a lot of GTK applications are unable to correctly display the font. This also affects Eclipse and many Gnome applications. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 24 May '20

24 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 Andrew Obuchowicz <aobuchow(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aobuchow(a)redhat.com --- Comment #17 from Andrew Obuchowicz <aobuchow(a)redhat.com> --- I've encountered this issue recently after updating to F32 from F30. Is there a suggested workaround? I really would like to continue using Terminus as my system font, and the Terminus TTF font is blurry :( Some additional notes: - Despite the fact that only the Italic version of Terminus is broken in my font selection dialog (using lxappearance), GTK apps such as the Gnome file manager and Eclipse are completely broken when Terminus is used as the system font. Only glyphs appear. - Certain GTK applications don't seem to break (such as Firefox and HexChat). They seem to handle this bug better? If someone could find out what these applications are doing better, then other applications could make a workaround update until the core issue is resolved. I work on Eclipse IDE and would be willing to try and get this workaround into Eclipse. - Removing all *.pcf.gz fonts didn't seem to fix the issue for me, and worst, it broke the Terminus font for KDE Plasma. - QT (or more specifically, KDE) applications seem to be handling this better. All my KDE apps still look fine, and the font selection dialog does not suggest the italics version of Terminus, and labels it Terminus [xos4]. I'll attach some related screenshots. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 23 May '20

23 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #36 from Alan <alan.g12r(a)outlook.com> --- Yeah, it's based on Latin proportions. Maybe this type of fonts are more compatible for mobile screens. https://i.imgur.com/Qb8rFah.png Besarion has made a comparison of them here: https://bpgfonts.wordpress.com/2009/01/31/%E1%83%9E%E1%83%A0%E1%83%9D%E1%83… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 23 May '20

23 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #35 from George Machitidze <giomac(a)gmail.com> --- Good, that's Akaki But font is large: https://drive.google.com/file/d/1rUsmuLRyLCqfenjFMsc73SPe-ZBfSv-C/view?usp=… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 23 May '20

23 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #34 from Alan <alan.g12r(a)outlook.com> --- @George Machitidze The author of Google Noto Georgian is Akaki Razmadze. More info - https://www.marketer.ge/akaki-razmadze-ios13-android-10/ He also designed FiraGO Georgian, which is publicly available under FOSS license. So, I think, you can feel free to contact him. It's a modern-style typeface. Please see Besarion's post on FB https://www.facebook.com/groups/geotypography/permalink/1499502893517216/?c… Yes, I know who you are (from Tbilisi forum), I am Georgian too. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 23 May '20

23 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #33 from George Machitidze <giomac(a)gmail.com> --- @Nicolas Mailhot Thanks for details 1. If we should ditch DejaVu for legal issues - definitely, it must be done 2. Easy way - so far, only non-DejaVU font I can recommend to be GPL licensed (verified author and font) are from BPG family (https://bpgfonts.wordpress.com/2009/02/03/gpl-gnu-license-bpg-fonts/) If we need any clarification on that - I can contact him. 3. Long way - I can ask all major designers to create a font for us so we can include it somewhere, one of them already responded to my FB post regarding this issue (we have a discussion there). We can request any legal document if there is a concern - they can sign it. 4. I am not really sure about Google Noto - we don't know who is the author, but fonts are terrible and oversized (that's clearly visible) @ALAN I am Georgian, I've founded Georgian linux user group with my friends, I work on localization projects since 2004 (Ministry of Education and Science of Georgia), I am not a Fedora ambassador right now, just because I'm busy and lazy. I know what I am talking about, I'm not arguing. We've faced all these issues in 2004 and the result our work is: 0. Established relation with each-other, which was pretty hard because of different countries authors live (Georgia, Finland), differences in interests (Linux, Mac, Windows fans), difference in directions (RH fans, Canonical fans, KDE fans, GNOME fans), age gap (18 to 60 yo). We've all sat and decided to do the job the right way, usually we fight 1. Created new Georgian keyboard (MESS), included with other four keyboards in OSS XKB etc 2. BPG published fonts in GPL, while other his fonts and fonts from other people (including GEO series from Gia Shervashidze and fonts from Reno Siradze) are also available for free and virtually without limitations 3. Localization of KDE, GNOME, Fedora, Ubuntu, Windows Regarding Google Noto: Google NEVER asked anyone anything, they've even included Keyboard only few years ago, they don't know whom to ask and what to do - they've never reached us or government. Same applies to all their products and all l10n/i18n parts. We've tried, but they don't care. Same applies to Apple and both are now under heavy criticism from users as we are hardly to reading the texts and glyphs. Virtual keyboards also look ugly and are not proportional. We get no response - tried to push issues though representative officials, via government, via Georgian Mac's User Group (some of us are founding members there too) - nothing works. We were able to solve issues only with OSS software and M$. These Google fonts look REALLY BAD. It's hard to see whole picture if you haven't studied Georgian, but one thing you can easily find out - Georgian glyphs in Google Noto are HUGE. proportions are inadequate. Try to write few letters in latin Goto and then the same with Georgian, size is about 1.5 bigger. It's elementary and offensive. Who else are we looking for? If I will ask something like that to Besarioni, definitely, he'll laugh at me and never talk again (he's a man of character). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 23 May '20

23 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #32 from Alan <alan.g12r(a)outlook.com> --- @George Machitidze > You can read it in attached document "Mtavruli-style letters are never used as “capitals”; a word is always entirely presented in mtavruli or not" And you can also read the answer: > This statement was not correct. A number of documents from the late 19th century and early 20thcentury make use of mtavruli > characters in initial position in sentences, lines of verse, and for propernames and place-names. For example: https://ka.wikipedia.org/wiki/%E1%83%A5%E1%83%90%E1%83%A0%E1%83%97%E1%83%A3… Google Noto fonts are used as default for Georgian in Android and Arch-based distributions. They look nice. You can read here what Besarion thinks about Mtavruli (or ask him, if you have a direct communication) https://bpgfonts.wordpress.com/2016/02/24/mtavruli-for-perfection/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 23 May '20

23 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #31 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- @George Machitidze ### Legal aspects Much as I love the GPL and use it for my own projects it does not translate well to font files. From a legal point of view, software is derived into other software, so a license that propagates to derived works like the GPL does, works well. It’s software both parts of the equation. However, fonts can be derived into documents due to how document formats embed fonts (fully or via subsetting). Therefore, the GPL and software licenses in general are completely inadequate for font files. Most people do not want their documents GPLed just because they used a Free and Open font in them. Because the GPL is inadequate, there was quite a lot of experimenting at the start of the century to find a working license for Free and Open fonts. Some proposed font-specific GPL legal extensions. Others wrote brand new experimental licenses. In the end most everyone agreed to use the OFL, which is the font license of most Google fonts today, and the font license Fedora recommends for new font projects. DejaVu antedates all of this however. It is a direct derivative of Bitstream Vera, which was released under one of licenses people experimented with before settling on the OFL. Vera/DejaVu licensing is unlikely to change today because that would require Bitstream cooperation and probably quite a lot of money to motivate the Bistream legal department to look at it. When adding to or modifying Vera or DejaVu, you should strive to keep things simple and integrate the original Vera/DejaVu legal framework. DejaVu licensing is complex and one-of-a-kind due to the inadequacies of the original experimental Bitstream licensing. It’s not as simple as using vanilla GPL for software or the OFL for new font projects. https://github.com/dejavu-fonts/dejavu-fonts/blob/master/LICENSE When the DejaVu project was active it served as legal clearing house and made sure contributors understood and and agreed with those legal clauses. Now it is dormant, people that release DejaVu derivatives must do this work themselves. ### Font coverage aspect From a font file point of view the only thing we can do is try to integrate fonts with correct opentype metadata and correct unicode coverage. It is no use, as you wrote, to remove coverage from font files. Software that wants to use specific code-points will just fall back to fonts that include this coverage. If you want to prevent those fallbacks the only reliable way is to integrate good coverage in your font file so the fallback need not happen. If things still do not work after a font with good unicode coverage was deployed, then that means: 1. some piece or text rendering is making mistakes when applying the unicode standard. No use work-arrounding the standard by using incomplete or non-compliant font files here, you need to identify which part is misapplying the standard and get it fixed 2. the Unicode standard is wrong. Well, I sort of doubt this is the case here, but human creations are imperfect by nature. If the standard is wrong then you need to get it fixed because software implementers are applying the standard and do not have time to waste sifting through all the pseudo-standards people keep inventing all over the world. That’s the sole reason people use Unicode today. It is horribly complex, and not ideal, but having to deal with multiple conflicting encoding rules would be way worse. Chinese/Japanese/Korean people yelled for a decade Unicode made the wrong decisions for their scripts. They are using Unicode like everyone else today anyway, because the alternative to Unicode, are way worse from a software interoperability point of view. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 23 May '20

23 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #30 from George Machitidze <giomac(a)gmail.com> --- + Georgian glyphs in Google Noto are terrible and inadequately large when compared to other fonts containing Georgian glyphs and VERY large compared to glyphs written in Latin with the same Google Noto. Probably, that's the reason why nobody uses it here :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 23 May '20

23 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #29 from George Machitidze <giomac(a)gmail.com> --- Not that we just don't use them, WE DON'T HAVE THEM, therefore, we don't have mixed casing at all. There are no capital letters. "Mtavruli" is just a representation, it's not a case or capitalization. You can read it in attached document "Mtavruli-style letters are never used as “capitals”; a word is always entirely presented in mtavruli or not" -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 22 May '20

22 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bug 1806272 depends on bug 1835503, which changed state. Bug 1835503 Summary: DejaVu font issue https://bugzilla.redhat.com/show_bug.cgi?id=1835503 What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Resolution|--- |ERRATA -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 22 May '20

22 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bug 1806272 depends on bug 1835509, which changed state. Bug 1835509 Summary: DejaVu font issue https://bugzilla.redhat.com/show_bug.cgi?id=1835509 What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Resolution|--- |ERRATA -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 22 May '20

22 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bug 1806272 depends on bug 1835510, which changed state. Bug 1835510 Summary: DejaVu font issue https://bugzilla.redhat.com/show_bug.cgi?id=1835510 What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Resolution|--- |ERRATA -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 22 May '20

22 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bug 1806272 depends on bug 1835507, which changed state. Bug 1835507 Summary: DejaVu font issue https://bugzilla.redhat.com/show_bug.cgi?id=1835507 What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Resolution|--- |ERRATA -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1689037] anaconda sometimes crashes with a signal 11 quite early in install process
by bugzilla＠redhat.com 22 May '20

22 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1689037 --- Comment #47 from Adam Williamson <awilliam(a)redhat.com> --- So I gave this a preliminary shot, but it's not flying. I tried both this: -new-session -d -s anaconda -n main "LD_PRELOAD=libgomp.so.1 anaconda" +new-session -d -s anaconda -n main "LD_PRELOAD=libgomp.so.1 valgrind --tool=memcheck --leak-check=full --leak-resolution=high --num-callers=20 --log-file=/tmp/vgdump.log anaconda" and this: -new-session -d -s anaconda -n main "LD_PRELOAD=libgomp.so.1 anaconda" +new-session -d -s anaconda -n main "valgrind --tool=memcheck --leak-check=full --leak-resolution=high --num-callers=20 --log-file=/tmp/vgdump.log anaconda" but neither makes it to the installer within 50 minutes of booting (on an aarch64 VM), which means they're either not working at all or running so slow as to be useless. Didn't get any logs so can't tell which. I took those valgrind args from the GNOME docs, I am no expert on valgrind so didn't know what else to try. Anyone have any other suggestions? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 22 May '20

22 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #28 from Alan <alan.g12r(a)outlook.com> --- It's a good idea to switched to Google Noto as a default font for Georgian, or use it as an alternative to BPG. P.S. We use Mtavruli characters almost everywhere and we definitely need them. You can see a lot of examples at the end of this document: https://www.unicode.org/L2/L2016/16034-n4707-georgian.pdf See also this Q&A: https://www.unicode.org/L2/L2017/17045-georgian-resp.pdf In modern Georgian, Mtavruli is not used for mixed/title casing, only with the All Caps function, but it does NOT mean, that we don't have uppercase or they are not capital letters. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 22 May '20

22 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #27 from George Machitidze <giomac(a)gmail.com> --- direct answer to this issue is to have all characters in lowercase, because this is how Georgian language works - WE DON"T HAVE UPPERCASE characters, don't use them. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 22 May '20

22 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 George Machitidze <giomac(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |giomac(a)gmail.com --- Comment #26 from George Machitidze <giomac(a)gmail.com> --- Hello, One thing I can tell - we don't have a case in Georgian alphabet, some fonts include uppercase characters, some don't, but they are not really uppercase, they're just another set of glyphs or fonts inserted in the collection. They never should be mixed - we don't do that. Georgian devs are not clueless about licensing, we've been in quite long strict discussions about it since 2004. I have direct contact with all original font developers (Including mentioned BPG), so, I can check anything we need. Dejavu family includes fonts originally created by BPG, and Georgian LUG members were quite careful when we've asked him to include his works and release them as GPL licensed so we could include it in Linux distributions. Same applies to the keyboard layouts - that was done at the same time... What exactly is the case? How can I help? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 22 May '20

22 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1839164 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1839164 [Bug 1839164] DejaVu font issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 22 May '20

22 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #25 from Jens Petersen <petersen(a)redhat.com> --- (In reply to Nicolas Mailhot from comment #24) > No, because bpg-dejavu-sans-fonts is not a complete fork of dejavu, it is > missing other parts. > > Also, bpg-dejavu-sans-fonts is quite shaky legal-wise, the Georgian dev is > completely clueless about licensing, I’m not sure its GPL use is compatible > with the licensing in the other parts of dejavu, and even if it is, there > are good reason we are not using the GPL for font files (it would make > documents, that embed font parts, such as ODF or PDF, GPL, which is > definitely not what our users need). Sounds like Noto Georgian may be a better bet then. Not to mention the BPG family names typos. > We really need someone to revive the upstream dejavu project and restart > merging fixes and enhancements, since the original authors lost the drive. That would be great indeed. > (Can’t really blame them when downstreams like Fedora Workstation removed > DejaVu as default font just because it was steady and “boring”). That is not completely accurate, Dejavu is still default, just not for Gnome UI chrome. (And that was encouraged by Gnome, not particularly Fedora Workstation.) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 22 May '20

22 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bug 1806272 depends on bug 1835195, which changed state. Bug 1835195 Summary: scorched3d affected by font move https://bugzilla.redhat.com/show_bug.cgi?id=1835195 What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Resolution|--- |ERRATA -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 22 May '20

22 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bug 1806272 depends on bug 1835134, which changed state. Bug 1835134 Summary: Font move broke glob2 https://bugzilla.redhat.com/show_bug.cgi?id=1835134 What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Resolution|--- |ERRATA -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 21 May '20

21 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment|0 |1 #1685173 is| | obsolete| | --- Comment #16 from Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> --- Created attachment 1690664 --> https://bugzilla.redhat.com/attachment.cgi?id=1690664&action=edit OP gnome-terminal font selection dialog only with empty rectangles -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 21 May '20

21 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #24 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- No, because bpg-dejavu-sans-fonts is not a complete fork of dejavu, it is missing other parts. Also, bpg-dejavu-sans-fonts is quite shaky legal-wise, the Georgian dev is completely clueless about licensing, I’m not sure its GPL use is compatible with the licensing in the other parts of dejavu, and even if it is, there are good reason we are not using the GPL for font files (it would make documents, that embed font parts, such as ODF or PDF, GPL, which is definitely not what our users need). We really need someone to revive the upstream dejavu project and restart merging fixes and enhancements, since the original authors lost the drive. (Can’t really blame them when downstreams like Fedora Workstation removed DejaVu as default font just because it was steady and “boring”). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 21 May '20

21 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 Jens Petersen <petersen(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tagoh(a)redhat.com Version|32 |rawhide --- Comment #23 from Jens Petersen <petersen(a)redhat.com> --- Will making bpg-dejavu-sans-fonts default in the @fonts group cause any problems? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1619530] Replacement character shown in Georgian (ქართული) on the “Welcome to Fedora 29” page
by bugzilla＠redhat.com 21 May '20

21 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1619530 --- Comment #22 from Jens Petersen <petersen(a)redhat.com> --- Is there a python library that provides an appropriate title case function? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1797726] New: [abrt] ibus: bus_engine_proxy_new_internal(): ibus-daemon killed by SIGTRAP
by bugzilla＠redhat.com 19 May '20

19 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1797726 Bug ID: 1797726 Summary: [abrt] ibus: bus_engine_proxy_new_internal(): ibus-daemon killed by SIGTRAP Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:d076161e787366707e150ed08ee1047c19bf3e31;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: rahbcca(a)gmail.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: Updated system Version-Release number of selected component: ibus-1.5.21-7.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/gnome-shell-wayland.service cmdline: ibus-daemon --panel disable crash_function: bus_engine_proxy_new_internal executable: /usr/bin/ibus-daemon journald_cursor: s=37128e79df9d48caa3abdfe6206063ed;i=be8a3;b=bc325447c2514385a5a4c291258febe6;m=2022223;t=59dafda3d32f9;x=3c84cce56b66d985 kernel: 5.4.15-200.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1579076 -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Fedora-i18n-bugs] [Bug 1837748] New: iso-codes-4.5.0 is available
by bugzilla＠redhat.com 19 May '20

19 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1837748 Bug ID: 1837748 Summary: iso-codes-4.5.0 is available Product: Fedora Version: rawhide Status: NEW Component: iso-codes Keywords: FutureFeature, Triaged Assignee: pnemade(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: caillon+fedoraproject(a)gmail.com, 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 Target Milestone: --- Classification: Fedora Latest upstream release: 4.5.0 Current version/release in rawhide: 4.4-2.fc32 URL: https://salsa.debian.org/iso-codes-team/iso-codes 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/1406/ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Fedora-i18n-bugs] [Bug 1833858] Droid Hangul Jamo is separated and printed respectively
by bugzilla＠redhat.com 19 May '20

19 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #20 from Akira TAGOH <tagoh(a)redhat.com> --- Sure. but please be aware that what we need to fix at the end is apps (or rendering/layout libarary requriing a font to draw) since they do query to fontconfig what the best font is for. lang property represents the glyph coverage. precomposed glyphs aren't necessarily needed to represent Hangul if they have hang script tag as supported OpenType layout. in that sense, they don't meet criteria as "minimal" requirement to add them into orth. so if those libraries requires it to render Hangul properly, they should make sure if fonts has otlayout:hang otherwise blacklist them. Unfortunately capability property isn't supposed to affect score in fontconfig to find out the best font. if this is really needed, it should be implemented indeed. but it isn't the sort of one-stop, anyway. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Droid Hangul Jamo is separated and printed respectively
by bugzilla＠redhat.com 19 May '20

19 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #19 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- Jens, F32 droid is a huge refresh over F31 droid: 1. the fontconfig file was completely rewritten and revised, using what we learnt in the past decade 2. the font files were switched to the latest upstream version. That required writing a script to dig in the 2 GiB of upstream android repository So both 1. and 2.can create changes, independent of generic changes in our font processing stack. And 1. and 2. can not be easily untangled, the fontconfig rewrite was triggered by the fact the git trawling script was finding new font file splits in the android upstream repo. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Droid Hangul Jamo is separated and printed respectively
by bugzilla＠redhat.com 19 May '20

19 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #18 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- Akira, after removing the locale in the font specific setup I did intend to look at the generic orth part. I did not want to imply the korean orth was broken before checking it myself. You did it, thank you very much, that confirms other Droid-like fonts may be matched fontconfig-side for Hangul even though are too incomplete for the shaper to make use of them. Anyway, given what harfbuzz upstream wrote, fontconfig should probably either only match a Korean locale for fonts that include precomposed Korean glyphs, or for fonts that include decomposed glyphs and otlayout:hang. I’m quite sure apps don’t want to get into the business of comparing langs to otlayouts, for every lang that relies on an otlayout, that would require separate matching lists in every single app for every locale that does this, which would be insane. This kind of filtering belongs in fontconfig. However, even if we fix font filtering for hangul in a generic way in fontconfig, there still remains the need to explicitly blacklist Droid if selected by the user. We don’t have a good mechanism for that, that’s the key difference between https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/197 and just hiding the lang for Droid. Anyway I will keep this bug open for the local partial fix (hiding korean lang for droid in the droid package). But you probably need to open some generic issues fontconfig side. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Droid Hangul Jamo is separated and printed respectively
by bugzilla＠redhat.com 19 May '20

19 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #17 from Akira TAGOH <tagoh(a)redhat.com> --- My bad. please ignore my comment in the second half. totally misread comments. What exactly apps really needs to do may be to check capability if they have otlayout:hang and/or otlayout:jamo perhaps. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Droid Hangul Jamo is separated and printed respectively
by bugzilla＠redhat.com 19 May '20

19 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #16 from Akira TAGOH <tagoh(a)redhat.com> --- We do. <fontconfig> <match target="scan"> <test name="family"> <string>Droid Sans Fallback</string> </test> <edit name="lang" mode="assign">  <minus>  <name>lang</name> <langset>  <string>ko</string> </langset> </minus> </edit> </match> </fontconfig> If the decomposed glyphs are really required to satisfy Hangul rendering, it should be reflected to ko.orth instead of the sort of this workaround. Though, needing some feedback about it from native speakers or hangul experts. Please note that constructing strict and complicated orthograhy file isn't what it is intended for. it should be enumerated for minimal requirements. Current ko.orth was built based on KS X 1001 character set. that would means Droid Sans Fallback satisfies KS X 1001 but not good enough somehow, for harfbuzz. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 18 May '20

18 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bug 1806272 depends on bug 1835493, which changed state. Bug 1835493 Summary: DejaVu fonts issue https://bugzilla.redhat.com/show_bug.cgi?id=1835493 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |RAWHIDE -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 18 May '20

18 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bug 1806272 depends on bug 1835498, which changed state. Bug 1835498 Summary: DejaVu font issue https://bugzilla.redhat.com/show_bug.cgi?id=1835498 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |RAWHIDE -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 18 May '20

18 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bug 1806272 depends on bug 1835499, which changed state. Bug 1835499 Summary: DejaVu font issue https://bugzilla.redhat.com/show_bug.cgi?id=1835499 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |RAWHIDE -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 18 May '20

18 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bug 1806272 depends on bug 1835502, which changed state. Bug 1835502 Summary: DejaVu font issue https://bugzilla.redhat.com/show_bug.cgi?id=1835502 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |RAWHIDE -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Droid Hangul Jamo is separated and printed respectively
by bugzilla＠redhat.com 18 May '20

18 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #15 from Jens Petersen <petersen(a)redhat.com> --- So far I could only reproduce this in Fedora 32 (ie not Fedora 31). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Droid Hangul Jamo is separated and printed respectively
by bugzilla＠redhat.com 18 May '20

18 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #14 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- Upstream confirms the font is missing information to assemble the decomposed glyphs. Therefore, I will ensure it does not match Korean locales in fontconfig. If something explicitly sets Droid for an Hangul run of text, it will still use the font file however. I don’t think we have a technical mechanism to blacklist in that case. That, would probably require implementing https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/200 and https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/197 Not much point making packaging the fallback font file separately, gh will require it, so it will be present on any system that prints. It really needs handling at the fontconfig level to blacklist reliably. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Droid Hangul Jamo is separated and printed respectively
by bugzilla＠redhat.com 18 May '20

18 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 Jens Petersen <petersen(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Hangul Jamo is seperated |Droid Hangul Jamo is |and printed respectively |separated and printed | |respectively -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835510 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835510 [Bug 1835510] DejaVu font issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835509 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835509 [Bug 1835509] DejaVu font issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835507 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835507 [Bug 1835507] DejaVu font issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835506 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835506 [Bug 1835506] DejaVu font issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835504 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835504 [Bug 1835504] DejaVu font issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835503 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835503 [Bug 1835503] DejaVu font issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835502 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835502 [Bug 1835502] DejaVu font issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835499 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835499 [Bug 1835499] DejaVu font issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835498 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835498 [Bug 1835498] DejaVu font issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835495 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835495 [Bug 1835495] DejaVu font issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835493 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835493 [Bug 1835493] DejaVu fonts issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835491 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835491 [Bug 1835491] DejaVu fonts issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835489 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835489 [Bug 1835489] DejaVu fonts issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bug 1806272 depends on bug 1835486, which changed state. Bug 1835486 Summary: DejaVu font issue https://bugzilla.redhat.com/show_bug.cgi?id=1835486 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |RAWHIDE -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835486 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835486 [Bug 1835486] DejaVu font issue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835195 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835195 [Bug 1835195] scorched3d affected by font move -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1835134 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1835134 [Bug 1835134] Font move broke glob2 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1806272] DejaVu has been repackaged in F32+ using new fonts packaging macros; those macros use an srpm-independent file layout and remove srpm-level sharing like the previous -common subpackage
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1806272 Bruno Wolff III <bruno(a)wolff.to> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends On| |1823360 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1823360 [Bug 1823360] FTBFS - Unpacked font file not excluded -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1815128] Degree sign and other symbols not showing correctly in R graphics on Fedora 31/32
by bugzilla＠redhat.com 13 May '20

13 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1815128 Fedora Update System <updates(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ON_QA |CLOSED Fixed In Version| |R-3.6.3-2.fc31 Resolution|--- |ERRATA Last Closed| |2020-05-13 07:37:11 --- Comment #7 from Fedora Update System <updates(a)fedoraproject.org> --- FEDORA-2020-4463b97145 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Hangul Jamo is seperated and printed respectively
by bugzilla＠redhat.com 12 May '20

12 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 Parag Nemade <pnemade(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Link ID| |Github | |harfbuzz/harfbuzz/issues/24 | |00 --- Comment #13 from Parag Nemade <pnemade(a)redhat.com> --- I have reported this issue upstream at https://github.com/harfbuzz/harfbuzz/issues/2400 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1834887] New: harfbuzz-2.6.6 is available
by bugzilla＠redhat.com 12 May '20

12 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1834887 Bug ID: 1834887 Summary: harfbuzz-2.6.6 is available Product: Fedora Version: rawhide Status: NEW Component: harfbuzz Keywords: FutureFeature, Triaged Assignee: pnemade(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, klember(a)redhat.com, moceap(a)hotmail.com, pnemade(a)redhat.com, psatpute(a)redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 2.6.6 Current version/release in rawhide: 2.6.4-4.fc33 URL: https://harfbuzz.github.io/ 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/1299/ -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1833858] Hangul Jamo is seperated and printed respectively
by bugzilla＠redhat.com 12 May '20

12 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #12 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- Probably, harfbuzz upstream, but maybe they’ll tell you this is handled at another level of the stack. I know that Hangul is a very regular writing system so what Droid does here does not surprise me, the script has been designed to make this kind of decomposition possible. What I would like to know (and that’s pure shaping IMHO) is whether the composition of individual shapes in the font files relies on some dark corner or OpenType Harfbuzz is not supporting yet, of if it uses pre-Unicode composition mecanisms that never made it to the spec and won’t ever be supported -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Hangul Jamo is seperated and printed respectively
by bugzilla＠redhat.com 12 May '20

12 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #11 from Parag Nemade <pnemade(a)redhat.com> --- Let me not be in confused state here. Can you please tell me who are you looking at when you say shaper guys? I can try to ask those people to comment here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Hangul Jamo is seperated and printed respectively
by bugzilla＠redhat.com 12 May '20

12 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 Nicolas Mailhot <nicolas.mailhot(a)laposte.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|google-droid-fonts |harfbuzz Assignee|nicolas.mailhot(a)laposte.net |pnemade(a)redhat.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Hangul Jamo is seperated and printed respectively
by bugzilla＠redhat.com 12 May '20

12 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #10 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- Hi Parag, There are many ways to compose the same symbols in OpenType and Unicode, and gh will use it as generic fallback no matter what we do fontconfig side. Therefore, I would really like the shaper guys to state if the files are totally broken for Hangul, or if it’s just a composition method they didn't implement fully yet. That matters for the long term directions of this package and the other packages that depend on it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Hangul Jamo is seperated and printed respectively
by bugzilla＠redhat.com 12 May '20

12 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 Parag Nemade <pnemade(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|harfbuzz |google-droid-fonts Assignee|pnemade(a)redhat.com |nicolas.mailhot(a)laposte.net --- Comment #9 from Parag Nemade <pnemade(a)redhat.com> --- In LibreOffice Writer, text "가속도" gets rendered as "가속도" using Noto Sans CJK KR font but same rendered as "가ㅅㅗㄱㄷㅗ" if Droid Sans Fallback font is used. I also checked with UnDotum font, font family provided by un-core-dotum-fonts. I think as other Korean fonts proved that text rendering is working fine and same, this is not a shaper issue but issue in DroidSansFallbackFull.ttf font file. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Hangul Jamo is seperated and printed respectively
by bugzilla＠redhat.com 12 May '20

12 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #8 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- If part of DroidSansFallbackFull is bad we have mecanisms to blacklist those parts but before doing that it would be nice if the shaper guys could tell us if the problem is font file or shaper side, and what locales need blacklisting) Given that we are talking about a font family that was the default Android font family for years, that the biggest Android seller is Samsung, and Samsung is a Korean company, hitting problems on Hangul font file side would be rather surprising -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Hangul Jamo is seperated and printed respectively
by bugzilla＠redhat.com 12 May '20

12 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #7 from Parag Nemade <pnemade(a)redhat.com> --- Seems some problem in DroidSansFallbackFull.ttf font. I think better we make it optional font installed on the Fedora system? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Hangul Jamo is seperated and printed respectively
by bugzilla＠redhat.com 11 May '20

11 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #6 from hyunwoo.park(a)gmail.com --- @Jens Petersen, "Noto Sans CJK *" fonts at google chrome works fine at google chrome browser. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Hangul Jamo is seperated and printed respectively
by bugzilla＠redhat.com 11 May '20

11 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #5 from hyunwoo.park(a)gmail.com --- Created attachment 1687495 --> https://bugzilla.redhat.com/attachment.cgi?id=1687495&action=edit LibreOffice Writer, Noto Sans CJK KR/Droid Sans Fallback @Jens Petersen, "Noto Sans CJK" works Okey. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Hangul Jamo is seperated and printed respectively
by bugzilla＠redhat.com 11 May '20

11 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #4 from Jens Petersen <petersen(a)redhat.com> --- Have you tried with google-noto-sans-cjk-ttc-fonts (Noto Sans CJK)? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Hangul Jamo is seperated and printed respectively
by bugzilla＠redhat.com 11 May '20

11 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 --- Comment #3 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- If Droid *is* broken for Hangul guess it will need blacklisting for the corresponding locales -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833858] Hangul Jamo is seperated and printed respectively
by bugzilla＠redhat.com 11 May '20

11 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833858 Nicolas Mailhot <nicolas.mailhot(a)laposte.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |i18n-bugs(a)lists.fedoraproje | |ct.org, klember(a)redhat.com, | |moceap(a)hotmail.com, | |pnemade(a)redhat.com, | |psatpute(a)redhat.com Component|google-droid-fonts |harfbuzz Assignee|nicolas.mailhot(a)laposte.net |pnemade(a)redhat.com Doc Type|--- |If docs needed, set a value --- Comment #2 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- Since I doubt Google would have published Droid for more than a decade with borken Hangul, probably a problem shaper side -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 10 May '20

10 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 Akira TAGOH <tagoh(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tagoh(a)redhat.com) | --- Comment #15 from Akira TAGOH <tagoh(a)redhat.com> --- Sorry for late response, I was away from my computer for a while. (In reply to Hans Ulrich Niedermann from comment #14) > Let me try to summarize this bug's discussions with my limited understanding > of the font software stack: > > 1. The original poster mainly had an issue with fontconfig/ostree which > resulted in his gnome-terminal dialog showing only small rectangular glyphs > instead of "Terminus Medium", "Terminus Bold", and the > invented-by-the-software-stack "Terminus Bold Italic". This appears to have > been solved over in fontconfig/ostree land, so the main part of this bug > looks like a duplicate of > https://bugzilla.redhat.com/show_bug.cgi?id=1750891 to me, and definitively > outside the scope of what the terminus-fonts package is responsible for. Not exactly. this isn't ostree specific. when system has same font families in different formats, fontconfig prioritize them from various aspects though, FC_FONTFORMAT which is a priperty in cacche containing the font format is one of factors. but it do compare strings so far. so there are the case that fontconfig returns a bitmap font as the best font instead of OpenType and applications didn't just support the synthethic emboldening for such fonts. I thought so far fontconfig could intentionally gives a lower priority to bitmap fonts than OpenType fonts though, someone may also intentionally wants to use bitmap fonts rather than OpenType fonts. I need to think about how to implement it. thus, conditionally installing one of them in the packaging level was a workaround. > 2. The original poster also had a completely different issue with what > Akira TAGOH calls Pango/freetype in which the presence of *.pcf.gz files > breaks the "Terminus Italic" invented by what appears to be pango/freetype. > As this issue has been reappearing and is going to reappear until the last > piece of software using pre-pango font rendering has disappeared from at > least Fedora, if not the planet, I have created > https://bugzilla.redhat.com/show_bug.cgi?id=1827905 to track that part. So > the secondary part of this bug looks like a duplicate of 1827905 to me. Right. but that "the secondary part" is actually main thing for this. the comment#1 and relevant comments were the off-topic for this. > Akira TAGOH, sorry to bother you again here, but you appear to be the one > with the knowledge to actually help with this. I would not even know where > to start reading documentation. Sorry for that. that is one of my tasks I need to improve fontconfig documentation. > You have mentioned above "Disable embolden flag for certain apps". Where > would this flag be located? And in this case, terminus-fonts already > provides "Terminus Medium" and "Terminus Bold", so I cannot se where > "embolden" should play a part here, but might there be a "italicize" flag > somewhere? Maybe an "italicizes flag for certain fonts"? That could prevent > the secondary issue number 2. Well, enumerating everything in config isn't actually realistic but one could do for example (not tested): <match> <test name="family"><string>Terminus</string></test> <test name="prgname"><string>gnome-terminal</string></test> <edit name="fontformat" mode="prepend"><string>TrueType</string></edit> </match> As I commented for 1., this should be fixed/improved in fontconfig as well... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1833719] New: Please consider adding Monoid font
by bugzilla＠redhat.com 10 May '20

10 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1833719 Bug ID: 1833719 Summary: Please consider adding Monoid font Product: Fedora Version: 32 Status: NEW Component: liberation-fonts Assignee: vishalvijayraghavan(a)gmail.com Reporter: luke.hutch(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, petersen(a)redhat.com, psatpute(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, vishalvijayraghavan(a)gmail.com Target Milestone: --- Classification: Fedora Please consider adding the MIT/SIL-licensed monospace font Monoid to Fedora: https://github.com/larsenwork/monoid (I don't see a relevant component to add this bug to -- sorry to file it against liberation-fonts) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1767499] New: Very bad kerning for Tahoma in Fedora 31
by bugzilla＠redhat.com 09 May '20

09 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1767499 Bug ID: 1767499 Summary: Very bad kerning for Tahoma in Fedora 31 Product: Fedora Version: 31 Status: NEW Component: pango Assignee: tagoh(a)redhat.com Reporter: aros(a)gmx.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 Created attachment 1631087 --> https://bugzilla.redhat.com/attachment.cgi?id=1631087&action=edit Tahoma as rendered by Pango 1.44 in Fedora 31 This is how Tahoma font is rendered in Fedora 31. After downgrading to pango-1.43.0-4.fc30.x86_64.rpm the issue disappears. -- You are receiving this mail because: You are on the CC list for the bug.

1 31

[Fedora-i18n-bugs] [Bug 1155251] After opening my laptop I am unable to do an input via the keyboard
by bugzilla＠redhat.com 07 May '20

07 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1155251 alexander.mark(a)aon.at changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(alexander.mark@ao |needinfo- |n.at) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1830200] New: thai-scalable-fonts-0.7.2 is available
by bugzilla＠redhat.com 07 May '20

07 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1830200 Bug ID: 1830200 Summary: thai-scalable-fonts-0.7.2 is available Product: Fedora Version: rawhide Status: NEW Component: thai-scalable-fonts Keywords: FutureFeature, Triaged Assignee: pwu(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org 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 Latest upstream release: 0.7.2 Current version/release in rawhide: 0.6.5-7.fc32 URL: http://linux.thai.net/pub/thailinux/software/fonts-tlwg/ 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/4963/ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Fedora-i18n-bugs] [Bug 1762455] IBUS input methods don't work in QT5-based applications
by bugzilla＠redhat.com 05 May '20

05 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1762455 --- Comment #25 from Jens Petersen <petersen(a)redhat.com> --- I filed a qt5-qtbase bug 1832086 for this now for F32. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1827961] New: translate-toolkit-2.5.1 is available
by bugzilla＠redhat.com 05 May '20

05 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1827961 Bug ID: 1827961 Summary: translate-toolkit-2.5.1 is available Product: Fedora Version: rawhide Status: NEW Component: translate-toolkit Keywords: FutureFeature, Triaged Assignee: petersen(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: dwayne(a)translate.org.za, i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com, mmraka(a)redhat.com, petersen(a)redhat.com, suanand(a)redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 2.5.1 Current version/release in rawhide: 2.5.0-1.fc33 URL: http://toolkit.translatehouse.org/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://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/3685/ -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1762455] IBUS input methods don't work in QT5-based applications
by bugzilla＠redhat.com 05 May '20

05 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1762455 fujiwara <tfujiwar(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|Reopened | Status|NEW |CLOSED Resolution|--- |ERRATA Last Closed|2019-11-27 00:23:49 |2020-05-06 04:07:25 --- Comment #24 from fujiwara <tfujiwar(a)redhat.com> --- (In reply to Stefan Haan from comment #21) > After upgrading to Fedora 32 the same problem (as described in my original > comment https://bugzilla.redhat.com/show_bug.cgi?id=1762455#c0) reappears. > Affected versions are: > * anki-2.1.15-2.fc32 > * telegram-desktop-2.0.1-1.fc32 It's a different issue completely. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 05 May '20

05 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(tagoh(a)redhat.com) --- Comment #14 from Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> --- Let me try to summarize this bug's discussions with my limited understanding of the font software stack: 1. The original poster mainly had an issue with fontconfig/ostree which resulted in his gnome-terminal dialog showing only small rectangular glyphs instead of "Terminus Medium", "Terminus Bold", and the invented-by-the-software-stack "Terminus Bold Italic". This appears to have been solved over in fontconfig/ostree land, so the main part of this bug looks like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1750891 to me, and definitively outside the scope of what the terminus-fonts package is responsible for. 2. The original poster also had a completely different issue with what Akira TAGOH calls Pango/freetype in which the presence of *.pcf.gz files breaks the "Terminus Italic" invented by what appears to be pango/freetype. As this issue has been reappearing and is going to reappear until the last piece of software using pre-pango font rendering has disappeared from at least Fedora, if not the planet, I have created https://bugzilla.redhat.com/show_bug.cgi?id=1827905 to track that part. So the secondary part of this bug looks like a duplicate of 1827905 to me. Akira TAGOH, sorry to bother you again here, but you appear to be the one with the knowledge to actually help with this. I would not even know where to start reading documentation. You have mentioned above "Disable embolden flag for certain apps". Where would this flag be located? And in this case, terminus-fonts already provides "Terminus Medium" and "Terminus Bold", so I cannot se where "embolden" should play a part here, but might there be a "italicize" flag somewhere? Maybe an "italicizes flag for certain fonts"? That could prevent the secondary issue number 2. Also, is there a third issue discussed in this bug which I have completely overlooked? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 05 May '20

05 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 --- Comment #13 from Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> --- Created attachment 1685173 --> https://bugzilla.redhat.com/attachment.cgi?id=1685173&action=edit The original poster -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1815128] Degree sign and other symbols not showing correctly in R graphics on Fedora 31/32
by bugzilla＠redhat.com 04 May '20

04 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1815128 Fedora Update System <updates(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |ON_QA --- Comment #6 from Fedora Update System <updates(a)fedoraproject.org> --- FEDORA-2020-4463b97145 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-4463b97145` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-4463b97145 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1815128] Degree sign and other symbols not showing correctly in R graphics on Fedora 31/32
by bugzilla＠redhat.com 04 May '20

04 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1815128 Fedora Update System <updates(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |MODIFIED --- Comment #5 from Fedora Update System <updates(a)fedoraproject.org> --- FEDORA-2020-4463b97145 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-4463b97145 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1762455] IBUS input methods don't work in QT5-based applications
by bugzilla＠redhat.com 04 May '20

04 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1762455 --- Comment #23 from Jens Petersen <petersen(a)redhat.com> --- (This seems to have already affected Beta AFAICT. Also I can't seem to get XIM working either under Qt.) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1762455] IBUS input methods don't work in QT5-based applications
by bugzilla＠redhat.com 04 May '20

04 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1762455 --- Comment #22 from Jens Petersen <petersen(a)redhat.com> --- I think it would be better actually to open a new bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 04 May '20

04 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 Tomas Popela <tpopela(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(tpopela(a)redhat.co | |m) | --- Comment #12 from Tomas Popela <tpopela(a)redhat.com> --- No problems at all Hans. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla＠redhat.com 03 May '20

03 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1823637 Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(tpopela(a)redhat.co | |m) --- Comment #11 from Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> --- Tomas, would you mind if I attached your screenshot from https://tpopela.fedorapeople.org/terminus-broken.png to this bug? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Fedora-i18n-bugs] [Bug 1762455] IBUS input methods don't work in QT5-based applications
by bugzilla＠redhat.com 01 May '20

01 May '20

https://bugzilla.redhat.com/show_bug.cgi?id=1762455 Stefan Haan <stefanhaan08(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |NEW Resolution|ERRATA |--- --- Comment #21 from Stefan Haan <stefanhaan08(a)gmail.com> --- After upgrading to Fedora 32 the same problem (as described in my original comment https://bugzilla.redhat.com/show_bug.cgi?id=1762455#c0) reappears. Affected versions are: * anki-2.1.15-2.fc32 * telegram-desktop-2.0.1-1.fc32 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs May 2020