i18n-bugs April 2021

i18n-bugs@lists.fedoraproject.org

1 participants
91 discussions

[Fedora-i18n-bugs] [Bug 1936817] New: [abrt] kasumi-unicode: emission_find(): kasumi-unicode killed by SIGSEGV
by bugzilla＠redhat.com 14 Sep '24

14 Sep '24

https://bugzilla.redhat.com/show_bug.cgi?id=1936817 Bug ID: 1936817 Summary: [abrt] kasumi-unicode: emission_find(): kasumi-unicode killed by SIGSEGV Product: Fedora Version: 34 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:44f05d41fea2e8a472e511e723c030f064b80150;VAR IANT_ID=workstation; Component: kasumi Assignee: tagoh(a)redhat.com Reporter: mfabian(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: kasumi-unicode-2.5-33.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: kasumi-unicode crash_function: emission_find executable: /usr/bin/kasumi-unicode journald_cursor: s=4812fe31419f4a0d9519537873c0b262;i=1d75b;b=e33e48f83165443e996e9352116d67f6;m=a1416f520;t=5bd16d16bd6c8;x=215dd7f338688f54 kernel: 5.11.3-300.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 emission_find at ../gobject/gsignal.c:893 #4 gtk_widget_dispose at /usr/src/debug/gtk3-3.24.26-1.fc34.x86_64/gtk/gtkwidget.c:12162 #7 _gtk_header_bar_update_window_buttons at /usr/src/debug/gtk3-3.24.26-1.fc34.x86_64/gtk/gtkheaderbar.c:474 #8 g_cclosure_marshal_VOID__OBJECTv at ../gobject/gmarshal.c:1910 #9 _g_closure_invoke_va at ../gobject/gclosure.c:873 #12 gtk_widget_propagate_hierarchy_changed_recurse at /usr/src/debug/gtk3-3.24.26-1.fc34.x86_64/gtk/gtkwidget.c:9995 #13 _gtk_widget_propagate_hierarchy_changed at /usr/src/debug/gtk3-3.24.26-1.fc34.x86_64/gtk/gtkwidget.c:10037 #14 gtk_widget_set_parent at /usr/src/debug/gtk3-3.24.26-1.fc34.x86_64/gtk/gtkwidget.c:9653 #15 gtk_window_set_titlebar at /usr/src/debug/gtk3-3.24.26-1.fc34.x86_64/gtk/gtkwindow.c:4234 #16 _gtk_builder_add at /usr/src/debug/gtk3-3.24.26-1.fc34.x86_64/gtk/gtkbuilder.c:906 -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[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

[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 1919963] New: /usr/share/doc/libunistring-devel/libunistring.html missing in devel
by bugzilla＠redhat.com 27 Nov '23

27 Nov '23

https://bugzilla.redhat.com/show_bug.cgi?id=1919963 Bug ID: 1919963 Summary: /usr/share/doc/libunistring-devel/libunistring.html missing in devel Product: Fedora Version: 32 Hardware: All OS: All Status: NEW Component: libunistring Severity: medium Assignee: p(a)draigbrady.com Reporter: reini.urban(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, jim(a)meyering.net, p(a)draigbrady.com, redhat-bugzilla(a)linuxnetz.de Target Milestone: --- Classification: Fedora Description of problem: after installing libunistring and libunistring-devel the main doc entrypoint for html is missing. /usr/share/doc/libunistring-devel/libunistring.html Version-Release number of selected component (if applicable): libunistring-devel-0.9.10-7.fc32.x86_64 How reproducible: Open a html doc, and click on Contents. e.g firefox /usr/share/doc/libunistring-devel/libunistring_1.html Haven't checked if that is an upstream problem, or just a bad rpm spec. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Fedora-i18n-bugs] [Bug 1910836] New: stardict-3.0.6.2 is available
by bugzilla＠redhat.com 06 Jun '23

06 Jun '23

https://bugzilla.redhat.com/show_bug.cgi?id=1910836 Bug ID: 1910836 Summary: stardict-3.0.6.2 is available Product: Fedora Version: rawhide Status: NEW Component: stardict Keywords: FutureFeature, Triaged Assignee: psatpute(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org 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 Target Milestone: --- Classification: Fedora Latest upstream release: 3.0.6.2 Current version/release in rawhide: 3.0.6-15.fc33 URL: http://sourceforge.net/projects/stardict-4 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/4887/ -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[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 1938251] New: update_preedit_text_with_mode(..., .., ..., IBus.PreeditFocusMode.COMMIT) doesn’t work in Gnome Wayland (works fine in Gnome Xorg)
by bugzilla＠redhat.com 25 May '23

25 May '23

https://bugzilla.redhat.com/show_bug.cgi?id=1938251 Bug ID: 1938251 Summary: update_preedit_text_with_mode(..., .., ..., IBus.PreeditFocusMode.COMMIT) doesn’t work in Gnome Wayland (works fine in Gnome Xorg) 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 I installed Fedora-Workstation-Live-x86_64-34-20210308.n.0.iso into qemu. Add the ibus-typing-booster input method in the Gnome control center and also add the “Vietnamese (telex (m17n))” input method from ibus-m17n. Both input methods use update_preedit_text_with_mode(..., .., ..., IBus.PreeditFocusMode.COMMIT) and this problem can be reproduced with either of them. Open a gedit and a gnome-terminal. Select ibus-typing-booster in the Gnome panel and type “test”. The word “test” is underlined, indicating that it is in preedit and not yet committed to gedit. Now click on gnome-terminal to change the focus to gnome-terminal. The string “test” vanishes from gedit. It should *not* vanish, it should be committed i.e. the underline under “test” should vanish and the string “test” should be in gedit. Same problem with the Vietnamese (telex (m17n)) input method. Select it in the Gnome panel. Type “a” into gedit. The “a” is underlined because it is in preedit. Click on gnome-terminal to change the focus to gnome-terminal. The “a” vanishes. Here as well the “a” should be commited to gedit, i.e. the underline should disappear and the “a” should remain in gedit. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1937235] New: [abrt] ibus-hangul: hangul_ic_select_keyboard(): ibus-engine-hangul killed by SIGSEGV
by bugzilla＠redhat.com 16 May '23

16 May '23

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.

1 7

[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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs April 2021