i18n-bugs March 2020

i18n-bugs@lists.fedoraproject.org

1 participants
135 discussions

[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 03 Jun '23

03 Jun '23

https://bugzilla.redhat.com/show_bug.cgi?id=1813728 Bug ID: 1813728 Summary: Square four dot Unicode character has incorrect glyph Product: Fedora Version: 31 Hardware: x86_64 OS: Linux Status: NEW Component: pango Severity: low Assignee: pwu(a)redhat.com Reporter: guillaumepoiriermorency(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: caillon+fedoraproject(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, john.j5live(a)gmail.com, mclasen(a)redhat.com, pwu(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: The glyph for the Unicode "square four dot" character is incorrect. Version-Release number of selected component (if applicable): I think this problem arose when upgrading from Fedora 30 to Fedora 31. How reproducible: The simplest way is to start GNOME Characters Map and search for "square four dot". -- You are receiving this mail because: You are on the CC list for the bug.

1 20

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

26 Apr '23

https://bugzilla.redhat.com/show_bug.cgi?id=1779123 Bug ID: 1779123 Summary: Pango no longer supports type1 fonts Product: Fedora Version: rawhide Status: NEW Component: pango Assignee: pwu(a)redhat.com Reporter: mjg(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: caillon+fedoraproject(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, john.j5live(a)gmail.com, mclasen(a)redhat.com, pwu(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: In pango 1.44, pango dropped support for type1 fonts. Therefore, no application which uses pango for font loading can use type1 fonts any more. Version-Release number of selected component (if applicable): pango-1.44.6-1.fc31.x86_64 (and later) How reproducible: always Steps to Reproduce: 1. Upgrade F31 or rawhide 2. Open any pango-using application 3. Try to use type1 font Actual results: No type1 font is usable Expected results: Type1 font is usable Additional info: bug 1753295 is the same bug for dropped bitmap font support. Over there, workarounds specific for bitmap fonts (conversion to opentype bitmap fonts) are discussed. An attempt to discuss type1 there failed. This bug here is specifically about type1 fonts to discuss ways (or their absence) to deal with pangos dropped type 1 support. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

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

14 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1767976 Bug ID: 1767976 Summary: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT Product: Fedora Version: 31 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:b24defc317ee932c47b15b9c24c231f607dad274;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: rauch.christian(a)gmx.de QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-1.5.21-3.fc31 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1001.slice/user@1001.service/gnome-shell-wayland.service cmdline: ibus-daemon --panel disable -r --xim crash_function: bus_dbus_impl_connection_filter_cb executable: /usr/bin/ibus-daemon journald_cursor: s=3ad93f33cf144f27b2bc4f480d8f3f2e;i=4b9e;b=9037b22bbad44adc83ebb6c1be09e1fc;m=1975f869;t=594e3ce75700c;x=34f5463c97ecc8bd kernel: 5.3.5-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001 Potential duplicate: bug 1475710 -- You are receiving this mail because: You are on the CC list for the bug.

1 17

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

13 Dec '22

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

1 15

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

13 Dec '22

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

1 9

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

01 Dec '22

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

1 7

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

07 Jun '22

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

1 6

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

16 May '22

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

1 15

[Fedora-i18n-bugs] [Bug 1809989] New: By default install Noto fonts for Unicode scripts not already covered by default
by bugzilla＠redhat.com 02 Apr '22

02 Apr '22

https://bugzilla.redhat.com/show_bug.cgi?id=1809989 Bug ID: 1809989 Summary: By default install Noto fonts for Unicode scripts not already covered by default Product: Fedora Version: 31 Status: NEW Component: google-noto-fonts Assignee: petersen(a)redhat.com Reporter: hsivonen(a)hsivonen.fi QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, psatpute(a)redhat.com, pwu(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora There is currently movement towards protecting browser users from font fingerprinting. This means refusing, by default, to load user-installed fonts, which makes the set of fonts that each OS installs by default even more important than before. Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1582687 W3C CSS WG issue: https://github.com/w3c/csswg-drafts/issues/4497 Currently, Windows 10, macOS, Android, and Chrome OS provide broader installed-by-default Unicode coverage than Fedora. Examples of living scripts that have enough active users to make it to the list at https://en.wikipedia.org/wiki/List_of_writing_systems#List_of_writing_scrip… but are not supported by default in Fedora 31 include Javanese, Sundanese, Batak, Balinese, Mongolian, and New Tai Lue. Egyptian hieroglyphs is an example of a dead script the Fedora 31 doesn't support out of the box but Windows 10, macOS, Chrome OS, and Android do. To remedy this with minimal disk space impact, I suggest the same approach that Apple took. Apple bundles with macOS those Noto fonts that cover scripts that were not already covered by the previous installed-by-default set of fonts on macOS. In the macOS case, the on-disk footprint of the Noto fonts that were required to take macOS to Android/Chrome OS-competitive Unicode coverage was only a couple of megabytes. (The fonts are hidden in /Library/Application Support/Apple/Fonts/Language Support/.) In the case of Fedora, the set of Noto fonts required to reach the Chrome OS / Android level of script coverage is a bit larger than in the macOS case but should still be manageable. Please install, by default, those Noto fonts that provide support for scripts that are not properly supported by the fonts that Fedora already installs by default. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs March 2020