September 2022 - i18n-bugs - Fedora Mailing-Lists

[Bug 2097613] New: update/install/reinstall of ibus - ibus scriplet - restart gnome shell esession

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2097613 Bug ID: 2097613 Summary: update/install/reinstall of ibus - ibus scriplet - restart gnome shell esession Product: Fedora Version: 36 Status: NEW Component: ibus Severity: high Assignee: tfujiwar(a)redhat.com Reporter: jvanek(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 update of system contains ibus, during run of ibus scriplet, gnome shell session is killed or logged forcibly out, looisn g all his work unexpectedly Version-Release number of selected component (if applicable): Steps to Reproduce: 1. log into gnome-shell gui 2. open some terminal emulator or switch to anohter console 3. sudo dnf reinstall ibus Actual results: gnome shell session kick you out no metter what you were doing Expected results: gnomeshell session will remian live -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2097613

10 months, 4 weeks

1
6
0 / 0

[Fedora-i18n-bugs] [Bug 1937235] New: [abrt] ibus-hangul: hangul_ic_select_keyboard(): ibus-engine-hangul killed by SIGSEGV

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1937235 Bug ID: 1937235 Summary: [abrt] ibus-hangul: hangul_ic_select_keyboard(): ibus-engine-hangul killed by SIGSEGV Product: Fedora Version: 34 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:2c789cb882f05d089b3d896c3bf215104523de34;VAR IANT_ID=workstation; Component: ibus-hangul Assignee: pwu(a)redhat.com Reporter: mfabian(a)redhat.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.4-4.fc34 Additional info: reporter: libreport-2.14.0 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-hangul --ibus crash_function: hangul_ic_select_keyboard executable: /usr/libexec/ibus-engine-hangul journald_cursor: s=aeb2461fa27a41febb2b69e0c1f19a49;i=2a21e;b=02ae636d7bd94d8399fe1a589a2cc54d;m=de67d05db;t=5bd2a055e55b4;x=f89bc2f41f604a4d kernel: 5.11.3-300.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (2 frames) #0 hangul_ic_select_keyboard at /usr/src/debug/libhangul-0.1.0-23.fc34.x86_64/hangul/hangulinputcontext.c:1626 #1 settings_changed at /usr/src/debug/ibus-hangul-1.5.4-4.fc34.x86_64/src/engine.c:1941 -- You are receiving this mail because: You are on the CC list for the bug.

11 months, 1 week

1
7
0 / 0

[Fedora-i18n-bugs] [Bug 1790554] New: Keyboard layout of Kana Kanji wont show up

by bugzilla＠redhat.com

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.

11 months, 1 week

1
20
0 / 0

[Bug 2105043] New: After an update, Japanese input stopped working

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2105043 Bug ID: 2105043 Summary: After an update, Japanese input stopped working Product: Fedora Version: 35 Status: NEW Component: anthy Assignee: tagoh(a)redhat.com Reporter: zaitcev(a)redhat.com 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: The 'ja' cannot be selected as before from Gnome menu. But "Japanese (Anthy)" is present in Settings. Tried to remove and re-add, no success. Version-Release number of selected component (if applicable): anthy-unicode-1.0.0.20211224-1.fc35.x86_64 ibus-anthy-1.5.14-1.fc35.x86_64 How reproducible: 100% on the affected system, but we don't know what triggered it. Steps to Reproduce: 1. Open Settins, Keyboard 2. Add Japanese (Anthy) 3. Check if the top (black) Gnome menu now has 'ja'. Actual results: No Japanese input Expected results: Working as before. 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=2105043

11 months, 1 week

1
12
0 / 0

[Bug 1964374] New: stardict scan hotkey doesn't work

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1964374 Bug ID: 1964374 Summary: stardict scan hotkey doesn't work Product: Fedora Version: 33 Status: NEW Component: stardict Assignee: psatpute(a)redhat.com Reporter: antmak.pub(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: anish.developer(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, nav007(a)gmail.com, petersen(a)redhat.com, psatpute(a)redhat.com, pwu(a)redhat.com, robinlee.sysu(a)gmail.com, yanqiyu01(a)gmail.com Target Milestone: --- Classification: Fedora Description of problem: The "Use scan hotkey:" option from StarDict's Preferences doesn't work Version-Release number of selected component (if applicable): stardict-3.0.6-15.fc33.x86_64 Fedore 33 GNOME @ Wayland session How reproducible: Just change the option to any value, it doesn't work. Steps to Reproduce: 1. Open StarDict 2. Open Preferences, "Scan Selection" tab 3. Enable "Use scan hotkey" option. 4. Values: "<Primary><Alt>x", "<Super>j", "<Primary><Alt>j" don't work - it can't scan selected words from other windows like Firefox or Gedit Actual results: It should scan selected words in other apps and open a translate window Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

11 months, 1 week

1
12
0 / 0

[Fedora-i18n-bugs] [Bug 1847347] New: gnome-terminal and xfce4-terminal get surrounding text from previous application

by bugzilla＠redhat.com

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/hun... ) 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.

11 months, 1 week

1
13
0 / 0

[Bug 2109358] New: emacs fails to start: Cannot open load file: No such file or directory, comp

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2109358 Bug ID: 2109358 Summary: emacs fails to start: Cannot open load file: No such file or directory, comp Product: Fedora Version: 36 Status: NEW Component: emacs-common-ddskk Assignee: dueno(a)redhat.com Reporter: nicku(a)nicku.org 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: emacs fails to start if emacs-ddsdk is installed Version-Release number of selected component (if applicable): 16.2-12.fc36 How reproducible: Always Steps to Reproduce: 1.Install emacs, it runs 2.install emacs-ddsdk 3. Emacs refuses to start, with message, "Cannot open load file: No such file or directory, comp" Actual results: Emacs refuses to start, with message, "Cannot open load file: No such file or directory, comp" Expected results: emacs runs. Additional info: strace shows emacs looking iin so many places other than the right one. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2109358

11 months, 1 week

1
15
0 / 0

[Bug 2113224] New: fcitx-unikey: FTBFS in Fedora rawhide/f37

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2113224 Bug ID: 2113224 Summary: fcitx-unikey: FTBFS in Fedora rawhide/f37 Product: Fedora Version: rawhide Status: NEW Component: fcitx-unikey Assignee: liangsuilong(a)gmail.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, liangsuilong(a)gmail.com, robinlee.sysu(a)gmail.com, yanqiyu01(a)gmail.com Blocks: 2045102 (F37FTBFS,RAWHIDEFTBFS) Target Milestone: --- Classification: Fedora fcitx-unikey failed to build from source in Fedora rawhide/f37 https://koji.fedoraproject.org/koji/taskinfo?taskID=89772056 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild Please fix fcitx-unikey at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, fcitx-unikey will be orphaned. Before branching of Fedora 38, fcitx-unikey will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai... Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2045102 [Bug 2045102] Fedora 37 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2113224

11 months, 1 week

1
4
0 / 0

[Bug 2113223] New: fcitx-skk: FTBFS in Fedora rawhide/f37

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2113223 Bug ID: 2113223 Summary: fcitx-skk: FTBFS in Fedora rawhide/f37 Product: Fedora Version: rawhide Status: NEW Component: fcitx-skk Assignee: dueno(a)redhat.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Blocks: 2045102 (F37FTBFS,RAWHIDEFTBFS) Target Milestone: --- Classification: Fedora fcitx-skk failed to build from source in Fedora rawhide/f37 https://koji.fedoraproject.org/koji/taskinfo?taskID=89772009 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild Please fix fcitx-skk at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, fcitx-skk will be orphaned. Before branching of Fedora 38, fcitx-skk will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai... Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2045102 [Bug 2045102] Fedora 37 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2113223

11 months, 1 week

1
4
0 / 0

[Bug 2113221] New: fcitx-kkc: FTBFS in Fedora rawhide/f37

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2113221 Bug ID: 2113221 Summary: fcitx-kkc: FTBFS in Fedora rawhide/f37 Product: Fedora Version: rawhide Status: NEW Component: fcitx-kkc Assignee: dueno(a)redhat.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Blocks: 2045102 (F37FTBFS,RAWHIDEFTBFS) Target Milestone: --- Classification: Fedora fcitx-kkc failed to build from source in Fedora rawhide/f37 https://koji.fedoraproject.org/koji/taskinfo?taskID=89771949 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild Please fix fcitx-kkc at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, fcitx-kkc will be orphaned. Before branching of Fedora 38, fcitx-kkc will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai... Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2045102 [Bug 2045102] Fedora 37 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2113221

11 months, 1 week

1
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs September 2022