i18n-bugs April 2023

i18n-bugs@lists.fedoraproject.org

1 participants
161 discussions

[Bug 2076596] New: The KDE ibus panel does not work as expected.
by bugzilla＠redhat.com 29 May '24

29 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=2076596 Bug ID: 2076596 Summary: The KDE ibus panel does not work as expected. Product: Fedora Version: 36 Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: lruzicka(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 1873514 --> https://bugzilla.redhat.com/attachment.cgi?id=1873514&action=edit The ibus panel with incorrect layout. Description of problem: I have freshly installed KDE Live 20220418 and made following settings during the installation: * System language is English. * Keyboard layout is Czech. After the installation, the keyboard is correctly laid out to "czech" and uses the correct czech mappings. When I check for the system settings using `localectl status`, I get the same result: === System Locale: LANG=en_US.UTF-8 VC Keymap: cz X11 Layout: cz === However, when I log into the KDE session, the IBUS-panel shows incorrectly "EN", but the layout is not English and even when I specifically select it using the panel, it does not have any influence. Also, when I use the panel to add other languages, it does not affect the system layout which is used for the KDE session, as well as for applications (kwrite, konsole), which remains "czech" all the time. Version-Release number of selected component (if applicable): ibus-1.5.26-3 KDE Plasma 5.24.4 How reproducible: Always Steps to Reproduce: 1. Install KDE Live with non-english layout (as the only one) 2. Log into the newly installed session. 3. See if ibus-panel shows the correct layout. 4. Try using ibus-panel to modify keyboard layout in the KDE session. Actual results: ibus-panel cannot modify keyboard layout Expected results: ibus-panel should be able to modify keyboard layout or should not be the default method to do so. Additional info: See screenshot -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2076596

1 41

[Bug 2095164] New: Conversion region of ibus-anthy is invisible in konsole, kwrite, kate
by bugzilla＠redhat.com 22 May '24

22 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=2095164 Bug ID: 2095164 Summary: Conversion region of ibus-anthy is invisible in konsole, kwrite, kate Product: Fedora Version: 36 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 1888253 --> https://bugzilla.redhat.com/attachment.cgi?id=1888253&action=edit Video showing the the conversion region is visible in some places but invisible in konsole, kwrite, kate Using Fedora-Workstation-Live-x86_64-36-1.2.iso installed in qemu-kvm with all current updates. kwrite, kate, and konsole, do not show the conversion region when using ibus-anthy konsole5-22.04.1-1.fc36.x86_64 kwrite-22.04.1-1.fc36.x86_64 kate-21.12.2-1.fc36.x86_64 It does not matter whether these programs are used in Plasma(X11), Plasma(Wayland), Gnome(Xorg), Gnome(Wayland), the behaviour is always the same, the conversion region is never visible. In konsole the behaviour is even worse because not even the cursor is shown at the start of the conversion region. When testing in Plasma(Wayland) or Plasma(X11) and typing with ibus-anthy into the search field of the KDE control center, the conversion region is coloured and thus visible. It is also visible when typing into the entry field for a command which opens with Alt+F2. So there are only some programs in KDE where it does not work like konsole, kwrite, kate, ... whereas it works in other places. See the attached video. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2095164

1 14

[Bug 2090204] New: [abrt] ibus: __strndup(): ibus-extension-gtk3 killed by SIGSEGV
by bugzilla＠redhat.com 22 May '24

22 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=2090204 Bug ID: 2090204 Summary: [abrt] ibus: __strndup(): ibus-extension-gtk3 killed by SIGSEGV Product: Fedora Version: 36 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:8c2b2d109d6c6600cfdf1e41632f3398d6d21e15;VAR IANT_ID=workstation; 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 Description of problem: Version-Release number of selected component: ibus-1.5.26-6.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service cmdline: /usr/libexec/ibus-extension-gtk3 crash_function: __strndup dso_list: /usr/libexec/ibus-extension-gtk3 ibus-1.5.26-6.fc36.x86_64 (Fedora Project) 1653401127 executable: /usr/libexec/ibus-extension-gtk3 journald_cursor: s=3da4198b50ed40bb8e39aac19c44f062;i=15b44;b=4f87f45459b64f7299ca0a57d8a15df6;m=51ec68d6;t=5dfc2daddfca9;x=e27b7bc9d78e7740 kernel: 5.17.9-300.fc36.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. https://bugzilla.redhat.com/show_bug.cgi?id=2090204

1 6

[Bug 2070187] New: please branch ibus-kkc for epel9
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=2070187 Bug ID: 2070187 Summary: please branch ibus-kkc for epel9 Product: Fedora Version: rawhide Status: NEW Component: ibus-kkc Assignee: dueno(a)redhat.com Reporter: petersen(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: I would like to have ibus-kkc with libkkc in epel9 and would be happy to help build it if you like. Could you please request an epel9 branch? If you don't mind to make me comaintainer that would be fine too. (libkkc got orphaned during the F35 cycle, I think so I was able to branch that already.) Thanks -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2070187

1 5

[Bug 2185830] New: [abrt] ibus-typing-booster: Py_Exit(): python3.11 killed by SIGABRT
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=2185830 Bug ID: 2185830 Summary: [abrt] ibus-typing-booster: Py_Exit(): python3.11 killed by SIGABRT Product: Fedora Version: 38 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:1016fbf3f898a8e267bb35897e7a7417c6d30f73;VAR IANT_ID=workstation; Component: ibus-typing-booster Assignee: mfabian(a)redhat.com Reporter: vladislav.inu(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: anish.developer(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-typing-booster-2.22.2-1.fc38 Additional info: reporter: libreport-2.17.9 type: CCpp reason: python3.11 killed by SIGABRT journald_cursor: s=ea8f1ea7412e46b6a5353afa22fa7be4;i=e85a;b=d3999bf12e7d45efa833e6ddcd5e4ab9;m=1669657280;t=5f8fe63f93bb0;x=8989452a1e24b345 executable: /usr/bin/python3.11 cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py --ibus cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service rootdir: / uid: 1000 kernel: 6.2.9-300.fc38.x86_64 package: ibus-typing-booster-2.22.2-1.fc38 runlevel: N 5 dso_list: /usr/bin/python3.11 python3-3.11.3-1.fc38.x86_64 (Fedora Project) 1680959302 backtrace_rating: 4 crash_function: Py_Exit Truncated backtrace: Thread no. 1 (34 frames) #5 Py_Exit at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pylifecycle.c:2944 #6 handle_system_exit at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:771 #7 _PyErr_PrintEx at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:781 #8 PyErr_PrintEx at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:876 #9 pygi_signal_closure_marshal at ../gi/pygi-signal-closure.c:202 #11 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3802 #18 emit_closed_in_idle at ../gio/gdbusconnection.c:1375 #22 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276 #24 ffi_call_unix64 at ../src/x86/unix64.S:104 #25 ffi_call_int at ../src/x86/ffi64.c:673 #26 ffi_call at ../src/x86/ffi64.c:710 #27 pygi_invoke_c_callable at ../gi/pygi-invoke.c:684 #28 pygi_function_cache_invoke at ../gi/pygi-cache.c:862 #29 pygi_callable_info_invoke at ../gi/pygi-invoke.c:727 #30 _wrap_g_callable_info_invoke at ../gi/pygi-invoke.c:764 #31 _callable_info_call at ../gi/pygi-info.c:548 #32 _PyObject_MakeTpCall at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Objects/call.c:214 #33 _PyEval_EvalFrameDefault at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/ceval.c:4773 #34 _PyEval_EvalFrame at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Include/internal/pycore_ceval.h:73 #35 _PyEval_Vector at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/ceval.c:6438 #36 PyEval_EvalCode at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/ceval.c:1154 #37 run_eval_code_obj at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:1714 #38 run_mod at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:1735 #39 pyrun_file at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:1630 #40 _PyRun_SimpleFileObject at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:440 #41 _PyRun_AnyFileObject at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Python/pythonrun.c:79 #42 pymain_run_file_obj at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Modules/main.c:360 #43 pymain_run_file at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Modules/main.c:379 #44 pymain_run_python at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Modules/main.c:601 #45 Py_RunMain at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Modules/main.c:680 #46 Py_BytesMain at /usr/src/debug/python3.11-3.11.3-1.fc38.x86_64/Modules/main.c:734 #47 __libc_start_call_main at ../sysdeps/nptl/libc_start_call_main.h:58 #48 __libc_start_main_impl at ../csu/libc-start.c:360 #49 _start -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2185830

1 18

[Fedora-i18n-bugs] [Bug 1897782] New: ibus pinyin input with special characters like '/' will repeat itself non-stop and cause strange behaviours with background applications
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=1897782 Bug ID: 1897782 Summary: ibus pinyin input with special characters like '/' will repeat itself non-stop and cause strange behaviours with background applications Product: Fedora Version: 33 Status: NEW Component: ibus-libpinyin Assignee: pwu(a)redhat.com Reporter: yemoran-2020(a)outlook.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: In Fedora 33 Workstation, with a Chinese system language, when I try to input with the ibus input (intelligent pinyin), and I pressed the slash key'/', then the slash character '/' will automatically keep repeating itself, even if I only pressed the slash key '/' once. Not only this caused unwanted '/' to spam, but: 1. Also prevents me from pressing alphabetical characters to use pinyin input normally, unless I delete all my remaining characters to exit pinyin prompt and start over; 2. Can possibly delete my already-saved text, in combination with <Ctrl-Backspace>. It seems that I have completely lost control within the pinyin prompt. I have met with other surprising conditions, though cannot be immediately reproduced now, but I believe more combinations of inputs triggering different bugs will be confirmed later. Version-Release number of selected component (if applicable): Any kind of version. I also tested with Fedora 32 Workstation, still have this bug. How reproducible: Always Steps to Reproduce: 1. Fetch any Fedora Workstation version, be it 32 or 33 or any updates applied. 2. Add Chinese input method 'Intelligent Pinyin' and switch to it 3. In GNOME(Wayland), open any GTK-based application, be it Firefox, GNOME Terminal, gedit, Libreoffice, ... (take gedit as an example) 4. Input 你好，今天天气 (keypress: nihao<1>，jintian<1>) as a start up example, confirm input use number key '1'. or keys like <Enter> or <Space>. 5. Input 怎么样/ (keypress: zenmy/）. Do not confirm immediately after 'zenmy', but press '/' exactly once. 6. The '/' character is repeating itself within several hundred milliseconds. 7. Press <Ctrl-Backspace>. gedit will highlight "你好，今天天气" (with a lot of trailing '/'). 8. Press <Backspace> to delete these Chinese characters. Actual results: Not only '/' is repeating itself, but also I lost control to gedit and gedit thinks you want to press '/' forever or even wants to delete my already-confirmed characters before this input. Expected results: 1. '/' Should not trigger anything, unless I have pressed this key and did not release this key press (but I always release keys) 2. '/' Should not make me lost control over pinyin prompt to gedit 3. <Backspace> Should only delete pinyin alphabets in pinyin prompt panel, and should not do anything to the background gedit texts, unless I have exited the pinyin prompt panel (because I confirmed my input or have deleted every pinyin alphabet in it) Additional info: 1. I did not found this bug on Debian buster or Arch with latest updates. Additionally, '/' did not even input a single character '/' in these distributions, but I cannot confirm if this is the expected behaviour. In Fedora 33 KDE, '/' did input a single character '/', but immediately stopped. 2. I didn't find this behaviour in qt-based applications (like Fedora Image Writer or Octave) in GNOME, or any application in other desktop environments (including KDE, or even GTK-based Cinnamon Desktop). This bug seems to only occur on GTK-based applications on GNOME. 3. I can be very sure that this is not caused by something wrong with my specific keyboard, because (a) Other distributions worked very well (b) Other Fedora spins worked very well (c) Qt-based applications in GNOME worked very well (d) GNOME X11 session worked very well (e) I replicated this bug on a fresh install of Fedora 32 Workstation in another laptop of mine. 4. I guess other special characters (or keys) like '[', ']', '\', '<Esc>', '<Backspace>', etc. may trigger similar bugs, but I cannot confirm. '/' will surely trigger this. ',' and '.' are used in pinyin input method to flip candidate characters pages, so they doesn't trigger this bug. ' does not trigger this bug (used in xi'an for 西安) -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Fedora-i18n-bugs] [Bug 1847347] New: gnome-terminal and xfce4-terminal get surrounding text from previous application
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=1847347 Bug ID: 1847347 Summary: gnome-terminal and xfce4-terminal get surrounding text from previous application Product: Fedora Version: 32 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 made the following screenshots and video by testing on Gnome-Xorg, but the problem occurs on Gnome-Wayland as well. How to reproduce (see also attached screenshots and video): - To show what happens with the surrounding text, I first opened the setup tool of ibus-typing-booster and set the debug level in the options tab to 3. When the debug level is high, the auxiliary text above the candidate list shows what context has been obtained by using surrounding text (if surrounding text is available, if it is not available like when using xterm, the context is just remembered from what was typed last). - I opened 3 windows: gedit, firefox, and gnome-terminal. - I focus on gedit and type "a b c d e" On top of the candidate list one can see: "Context: b c d" This is because when the letter "e" was typed, ibus-typing-booster got the surrounding text at the cursor position and parsed the last 3 tokens left of the cursor out of the result. And these last 3 tokens left of the cursor are "b c d". - Now I focus on firefox and type "f g h i j" On top of the candidate list one can see: "Context: g h i" I.e. the correct context "g h i" to the left of the just typed "j" (which is still in preedit) has been found using surrounding text. - Now I focus on gnome-terminal and type "k l m" On top of the candidate list one can see: "Context h i j" This comes from the surrounding text left of the cursor in *firefox*, *not* from gnome-terminal. Although gnome-terminal reports that surrounding text is supported, i.e. self.client_capabilities & IBus.Capabilite.SURROUNDING_TEXT is True (see the code to get the context at: https://github.com/mike-fabian/ibus-typing-booster/blob/master/engine/hunsp… ) gnome-terminal does not really seem to support surrounding text. The surrounding text comes from the previous client which really supported surrounding text. If the previous client was firefox, one still gets the surrounding text from firefox while typing in gnome-terminal. Same with gedit, if the previous client before focussing on gnome-terminal was gedit, one still gets the surrounding text from gedit while typing in gnome-terminal. - The same problem occurs when using xfce4-terminal instead of gnome-terminal. - When using xterm, the problem does *not* occur because when using xterm self.client_capabilities & IBus.Capabilite.SURROUNDING_TEXT is False and then the get_context() immediately returns and the context remembered from the last text typed is used as a fallback. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 2178174] New: Status indicator doesn't show proper current status on Flatpak app
by bugzilla＠redhat.com 13 May '24

13 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=2178174 Bug ID: 2178174 Summary: Status indicator doesn't show proper current status on Flatpak app Product: Fedora Version: 38 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 typing something through IBus on Flatpak on Silverblue and changing the input mode by Zenkaku_Hankaku key, current input mode isn't reflected to the status indicator at gnome-shell. Version-Release number of selected component (if applicable): Fedora-Silverblue-ostree-x86_64-38-20230314.n.0.iso How reproducible: always Steps to Reproduce: 1.Install SB and setup as usual 2.Install LibreOffice from 'Fedora Linux' on gnome-software 3.Run LibreOffice and type something and Zenkaku_Hankaku key Actual results: The status indicator keeps 'あ' and no changes after pressing Zenkaku_Hankaku key. also no ibus-related menu isn't available during flatpak app is active. Expected results: should works as usual 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=2178174

1 4

[Bug 2093313] New: Too many ibus warnings, "no capability of surrounding-text feature"
by bugzilla＠redhat.com 08 May '24

08 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=2093313 Bug ID: 2093313 Summary: Too many ibus warnings, "no capability of surrounding-text feature" 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: I know this is an application bug, flooding same warnings looks not good to me. this affects UX. applications and desktop is often freezing. $ journalctl -S 2022-06-03 | grep IBUS-WARNING | wc -l 15974 That is quite bad. Too many warnings should be omitted. Version-Release number of selected component (if applicable): ibus-1.5.26-4.fc36.x86_64 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2093313

1 13

[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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs April 2023