i18n-bugs January 2023

i18n-bugs@lists.fedoraproject.org

1 participants
111 discussions

[Bug 2013323] New: Cursor position and conversion regioni of ibus-anthy are invisible in Google Documents (both in firefox and google-chrome)
by bugzilla＠redhat.com 27 Apr '23

27 Apr '23

https://bugzilla.redhat.com/show_bug.cgi?id=2013323 Bug ID: 2013323 Summary: Cursor position and conversion regioni of ibus-anthy are invisible in Google Documents (both in firefox and google-chrome) Product: Fedora Version: 34 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 Created attachment 1832255 --> https://bugzilla.redhat.com/attachment.cgi?id=1832255&action=edit Video showing the wrongly displayed cursor position using ibus-anthy in Google Documents I did choose component ibus, although this is likely not an ibus bug but a problem in google docs, but I wanted to report it somehow, maybe something can be done to improve this: Fedora-Workstation-Live-x86_64-35-20210829.n.0.iso installed in qemu-kvm with all current updates. firefox-93.0-2.fc35.x86_64 google-chrome-unstable-96.0.4662.6-1.x86_64 ibus-1.5.25-4.fc35.x86_64 ibus-anthy-1.5.13-1.fc35.x86_64 See the attached video. In the video I type わたしのなまえはやまだです　first in gedit to show how it should work. After typing that hiragana, I type space to start conversion. The current conversion region is indicated by the cursor position and a purple background color. When the conversion to kanji is startet, at first the cursor position is at the left of the preedit and the conversion region is わたしの. I can then move the conversion region right with arrow-right and see that it moves because the blue background and the cursor position moves. Then I do the same in Google Documents (both in firefox and google-chrome, that makes no difference): - The cursor position is *always* shown at the right end of the preedit - The purple background color of the conversion region is not there One can move the conversion region around using the arrow keys, one just cannot see where the conversion region currently is the purple background is missing *and* the cursor position is *always* at the right end of the preedit. The same problem happens when trying to use ibus-typing-booster with the "inline completion" option in Google Documents. The color of the inline completion is missing *and* the cursor position is always at the end of the preedit, so one cannot see where the inline completion is and whether it has been accepted or not. In gedit in wayland, the colors don't work either, but at least the cursor position is shown correctly. When only the cursor position is shown but no color, it is not great at least somewhat usable. By carefully watching the cursor one can still see what is going on. But when the cursor positon is always at the right of preedit *and* there is no colour, this is completely unusable. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2013323

1 15

[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

[Bug 1993618] New: [abrt] ibus-libpinyin: PY::PunctEditor::moveCursorToBegin(): ibus-engine-libpinyin killed by SIGABRT
by bugzilla＠redhat.com 25 Apr '23

25 Apr '23

https://bugzilla.redhat.com/show_bug.cgi?id=1993618 Bug ID: 1993618 Summary: [abrt] ibus-libpinyin: PY::PunctEditor::moveCursorToBegin(): ibus-engine-libpinyin killed by SIGABRT Product: Fedora Version: 34 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:e41f218ee5601bc1377bb63d92ea7cfafa49f6df;VAR IANT_ID=workstation; Component: ibus-libpinyin Assignee: pwu(a)redhat.com Reporter: tcfxfzoi(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.12.0-3.fc34 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: PY::PunctEditor::moveCursorToBegin executable: /usr/libexec/ibus-engine-libpinyin journald_cursor: s=b843de467070413eac4da2bc5d966ff5;i=701f;b=c1ce31806f0448d2826bedd20c47fa6b;m=99564a78;t=5c986a4580fd5;x=bf2d4d76d0a056b9 kernel: 5.13.9-200.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #4 PY::PunctEditor::moveCursorToBegin at /usr/src/debug/ibus-libpinyin-1.12.0-3.fc34.x86_64/src/PYPunctEditor.cc:317 #5 PY::PunctEditor::processKeyEvent at /usr/src/debug/ibus-libpinyin-1.12.0-3.fc34.x86_64/src/PYPunctEditor.cc:190 #6 PY::BopomofoEngine::processKeyEvent at /usr/src/debug/ibus-libpinyin-1.12.0-3.fc34.x86_64/src/PYPBopomofoEngine.cc:198 #8 _ibus_marshal_BOOLEAN__UINT_UINT_UINT at /usr/src/debug/ibus-1.5.24-5.fc34.x86_64/src/ibusmarshalers.c:280 #13 ibus_engine_service_method_call at /usr/src/debug/ibus-1.5.24-5.fc34.x86_64/src/ibusengine.c:1107 #14 call_in_idle_cb at ../gio/gdbusconnection.c:4913 #18 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4131 #20 ibus_main at /usr/src/debug/ibus-1.5.24-5.fc34.x86_64/src/ibusshare.c:322 #21 start_component at /usr/src/debug/ibus-libpinyin-1.12.0-3.fc34.x86_64/src/PYMain.cc:141 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 2164233] New: FcCacheFini: Assertion `fcCacheChains[i] == NULL' failed.
by bugzilla＠redhat.com 21 Apr '23

21 Apr '23

https://bugzilla.redhat.com/show_bug.cgi?id=2164233 Bug ID: 2164233 Summary: FcCacheFini: Assertion `fcCacheChains[i] == NULL' failed. Product: Fedora Version: 37 Status: NEW Component: fontconfig Assignee: tagoh(a)redhat.com Reporter: byoungchan.lee(a)gmx.com QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com, pnemade(a)redhat.com, rstrode(a)redhat.com, sandmann(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: When I try to run openttd, fontconfig crashes due to an assertion. https://github.com/freedesktop/fontconfig/blob/2.14.1/src/fccache.c#L808 Version-Release number of selected component (if applicable): $ rpm -qa | grep fontconfig fontconfig-2.14.1-2.fc37.x86_64 fontconfig-2.14.1-2.fc37.i686 fontconfig-devel-2.14.1-2.fc37.x86_64 fontconfig-debugsource-2.14.1-2.fc37.x86_64 $ rpm -qa | grep openttd openttd-opengfx-7.1-3.fc37.noarch openttd-12.2-4.fc37.x86_64 How reproducible: Run openttd Steps to Reproduce: 1. 2. 3. Actual results: Crash Expected results: Game runs. Additional info: I'm not sure why assertions are enabled in fontconfig. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2164233

1 19

[Bug 2124007] New: Keyboard disappears from list of installed keyboards
by bugzilla＠redhat.com 17 Apr '23

17 Apr '23

https://bugzilla.redhat.com/show_bug.cgi?id=2124007 Bug ID: 2124007 Summary: Keyboard disappears from list of installed keyboards Product: Fedora Version: 36 Hardware: x86_64 OS: Linux Status: NEW Component: anthy Assignee: tagoh(a)redhat.com Reporter: Ben.Engbers(a)Be-Logical.nl QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: I have installed 3 keyboards (English VS, English International and Anthy). Anthy is mostly used in Libre Office Writer 7.3.4.2. I can switch the keyboard either by selecting one in the upper right corner of the screen or by cycling through te list of installed keyboards with Windows key/spacebar. After a few minutes my Lenovo laptop goes to sleep automatically. When I wake it up again, the Anthy keyboard has disappeared from the list of keyboards. Only the 2 English keyboards can be selected. In the settings dialog however, the Anthy keyboard is still visible. It is only after a new logon that the Japanese keyboard shows up again. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Logon after boot 2. Wait till the laptop goes to sleep 3. Wake up. Actual results: Anthy keyboard is no longer visible Expected results: Anthy keyboard can not be selected Additional info: -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2124007

1 2

[Bug 2062619] New: IBus stop working after locking screen
by bugzilla＠redhat.com 17 Apr '23

17 Apr '23

https://bugzilla.redhat.com/show_bug.cgi?id=2062619 Bug ID: 2062619 Summary: IBus stop working after locking screen Product: Fedora Version: rawhide Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: tagoh(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: When I keep preediting on apps and the screen is locked by idle, IBus stop working after unlocking. Version-Release number of selected component (if applicable): ibus-1.5.25-13.fc36.x86_64 How reproducible: always Steps to Reproduce: 1.Install Workstation from Live 2.Setup with ja 3.Open LibreOffice Writer 4.Type something on preedit and wait for locking the screen 5.Unlock the screen Actual results: Unable to input through IBus on apps Expected results: Able to input through IBus Additional info: IBus get back after changing the focus for example. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2062619

1 26

[Fedora-i18n-bugs] [Bug 1895482] New: Liberation Fonts Support For Serbian locl Glyphs Incomplete
by bugzilla＠redhat.com 04 Apr '23

04 Apr '23

https://bugzilla.redhat.com/show_bug.cgi?id=1895482 Bug ID: 1895482 Summary: Liberation Fonts Support For Serbian locl Glyphs Incomplete Product: Fedora Version: rawhide Hardware: x86_64 OS: Linux Status: NEW Component: liberation-fonts Assignee: vishalvijayraghavan(a)gmail.com Reporter: aleslavista(a)outlook.it QA Contact: extras-qa(a)fedoraproject.org CC: caillon+fedoraproject(a)gmail.com, fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com, 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 Created attachment 1727218 --> https://bugzilla.redhat.com/attachment.cgi?id=1727218&action=edit Correctly Localized Glyphs Description of problem: Liberation Fonts do NOT provide full support for Serbian localized glyphs. Version-Release number of selected component (if applicable): Liberation-Fonts 2.1-1-1 How reproducible: You need a program that is able to access the font's localized glyphs: usually that's LibreOffice Writer. Steps to Reproduce: 1. Open LibreOffice Writer 2. Type бгдпт, then бгдпт in Italic, бгдпт in Bold and finally бгдпт in Italic Bold with Liberation Serif, and do the same with Liberation Sans 3. Set the language to "Serbian Cyrillic" Actual results: Not all glyphs are correctly localized Expected results: See attachment for correctly localized glyphs Additional info: Liberation Mono has slanted Italic, therefore only the first glyph should be localized: CYRILLIC LETTER SMALL BE. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 2062407] New: msgfmt cannot invoke javac
by bugzilla＠redhat.com 29 Mar '23

29 Mar '23

https://bugzilla.redhat.com/show_bug.cgi?id=2062407 Bug ID: 2062407 Summary: msgfmt cannot invoke javac Product: Fedora Version: rawhide Hardware: All OS: Linux Status: NEW Component: gettext Severity: low Assignee: suanand(a)redhat.com Reporter: loganjerry(a)gmail.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, petersen(a)redhat.com, praiskup(a)redhat.com, suanand(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: I noticed while building jmol that every invocation of msgfmt failed, e.g.: update-application-catalog-lang: [echo] msgfmt Updating messages_ar.class file for Jmol ... [exec] msgfmt: Java compiler not found, try installing gcj or set $JAVAC [exec] msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC [exec] 65 translated messages, 3 fuzzy translations, 380 untranslated messages. [exec] Result: 1 Setting JAVAC does *not* help. I used strace to see how javac is invoked and found the problem: msgfmt passes -target 1.6, and sometimes -source 1.6, to javac. Now that OpenJDK 17 is the default in Fedora, those arguments are no longer valid. I don't remember if the minimum allowed is 1.7 or 1.8, but it is one of the two. Since Fedora doesn't ship a JDK lower than 1.8, then 1.8 might as well be used. Version-Release number of selected component (if applicable): gettext-0.21-11.fc37.0.20220228 How reproducible: Always Steps to Reproduce: 1. fedpkg clone jmol 2. cd jmol 3. fedpkg srpm 4. mock -r fedora-rawhide-x86_64 --rebuild jmol-14.32.22-1.fc37.src.rpm Actual results: The msgfmt invocations all fail. Expected results: The msgfmt invocations should succeed. Additional info: -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2062407

1 12

[Bug 2157582] New: Environment variables are no longer set in Wayland session after systemd subpackage was removed
by bugzilla＠redhat.com 28 Mar '23

28 Mar '23

https://bugzilla.redhat.com/show_bug.cgi?id=2157582 Bug ID: 2157582 Summary: Environment variables are no longer set in Wayland session after systemd subpackage was removed Product: Fedora Version: 37 Status: NEW Component: imsettings Assignee: tagoh(a)redhat.com Reporter: accounts+fedora(a)chiller3.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: After the removal of the imsettings-systemd subpackage, the IM-related environment variables (eg. QT_IM_MODULE) are no longer set in Wayland sessions (as least for KDE). I believe this is because none of the xinput scripts are read during Wayland session initialization and things previously relied on systemd's ~/.config/environment.d/. Version-Release number of selected component (if applicable): imsettings-1.8.3-6.fc37.x86_64 How reproducible: Always Steps to Reproduce: 1. Install Fedora 37 KDE spin 2. Log into Wayland session 3. Install an input method, like fcitx5 4. Select fcitx5 with im-chooser 5. Log out and log back in (still Wayland session) 6. $ echo $QT_IM_MODULE Actual results: Environment variables like QT_IM_MODULE are not set. Expected results: The IM-related environment variables should be set. (Manually setting them allows input methods to work properly in KDE Wayland.) Additional info: n/a -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2157582

1 23

[Bug 2156108] New: [abrt] ibus: XFree(): ibus-x11 killed by SIGABRT
by bugzilla＠redhat.com 19 Mar '23

19 Mar '23

https://bugzilla.redhat.com/show_bug.cgi?id=2156108 Bug ID: 2156108 Summary: [abrt] ibus: XFree(): ibus-x11 killed by SIGABRT Product: Fedora Version: rawhide Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:0385d31cccb3ffe2c784112a5c2060eeaac62698;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: mikhail.v.gavrilov(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.27-8.fc38 Additional info: reporter: libreport-2.17.6 type: CCpp reason: ibus-x11 killed by SIGABRT journald_cursor: s=32500b5f39e6467e9ccddd56700852eb;i=43e8f3;b=f22e26d260164e228db6c4bc7b4ef7db;m=869ce7646;t=5f017821d96fc;x=29a8c76b08f7f956 executable: /usr/libexec/ibus-x11 cmdline: /usr/libexec/ibus-x11 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.SettingsDaemon.XSettings.service rootdir: / uid: 1000 kernel: 6.1.0-65.fc38.x86_64+debug package: ibus-1.5.27-8.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: XFree Truncated backtrace: Thread no. 1 (19 frames) #8 XFree at /usr/src/debug/libX11-1.8.1-2.fc38.x86_64/src/XlibInt.c:1633 #9 ProcessQueue at ../../util/IMdkit/i18nPtHdr.c:1762 #10 _Xi18nMessageHandler at ../../util/IMdkit/i18nPtHdr.c:1923 #11 WaitXIMProtocol at ../../util/IMdkit/i18nX.c:524 #12 _gdk_x11_display_queue_events at ../gdk/x11/gdkeventsource.c:337 #13 gdk_display_get_event at ../gdk/gdkdisplay.c:442 #14 gdk_event_source_dispatch.lto_priv at ../gdk/x11/gdkeventsource.c:354 #17 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4238 #18 g_main_context_iteration at ../glib/gmain.c:4303 #19 xim_forward_event.constprop.0 at /usr/src/debug/ibus-1.5.27-8.fc38.x86_64/client/x11/main.c:631 #20 ForwardEventMessageProc at ../../util/IMdkit/i18nPtHdr.c:1224 #21 ProcessQueue at ../../util/IMdkit/i18nPtHdr.c:1758 #22 _Xi18nMessageHandler at ../../util/IMdkit/i18nPtHdr.c:1923 #23 WaitXIMProtocol at ../../util/IMdkit/i18nX.c:524 #24 _gdk_x11_display_queue_events at ../gdk/x11/gdkeventsource.c:337 #25 gdk_display_get_event at ../gdk/gdkdisplay.c:442 #26 gdk_event_source_dispatch.lto_priv at ../gdk/x11/gdkeventsource.c:354 #29 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4238 #31 ibus_main at /usr/src/debug/ibus-1.5.27-8.fc38.x86_64/src/ibusshare.c:325 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2156108

1 28

← Newer
1
...
5
6
7
8
9
10
11
12
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs January 2023