i18n-bugs September 2019

i18n-bugs@lists.fedoraproject.org

1 participants
151 discussions

[Fedora-i18n-bugs] [Bug 1747731] New: [abrt] ibus-libpinyin: pinyin::MemoryChunk::ensure_has_more_space(unsigned long)(): ibus-engine-libpinyin killed by SIGABRT
by bugzilla＠redhat.com 29 Sep '20

29 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1747731 Bug ID: 1747731 Summary: [abrt] ibus-libpinyin: pinyin::MemoryChunk::ensure_has_more_space(unsigned long)(): ibus-engine-libpinyin killed by SIGABRT Product: Fedora Version: 30 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:ebfdf9e0e88e902f1a9d6c72641712e29b0aca46; Component: ibus-libpinyin Assignee: pwu(a)redhat.com Reporter: dcdrake42(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 Description of problem: Seemed to occur while typing immediately after changing from English to Chinese input while using the browser version of Facebook Messenger (Chromium). Version-Release number of selected component: ibus-libpinyin-1.11.1-1.fc30 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: pinyin::MemoryChunk::ensure_has_more_space(unsigned long) executable: /usr/libexec/ibus-engine-libpinyin journald_cursor: s=9c254645106a4209b447b2a1893383ad;i=189698;b=c5ac01a80c3a439eb3832a0a5ed88e02;m=202900d17;t=59173a5b8af7b;x=99dc5a43153fc974 kernel: 5.2.9-200.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #7 pinyin::MemoryChunk::ensure_has_more_space(unsigned long) at ../../src/include/memory_chunk.h:122 #8 pinyin::MemoryChunk::ensure_has_space(unsigned long) at ../../src/include/memory_chunk.h:92 #9 pinyin::MemoryChunk::set_content(unsigned long, void const*, unsigned long) at ../../src/include/memory_chunk.h:286 #10 pinyin::MemoryChunk::append_content(void const*, unsigned long) at ../../src/include/memory_chunk.h:302 #11 pinyin::merge_single_gram(pinyin::SingleGram*, pinyin::SingleGram const*, pinyin::SingleGram const*) at ngram.cpp:322 #12 pinyin::PhoneticLookup<2, 3>::search_bigram2(_GPtrArray*, int, int, _GArray**) at ../src/include/memory_chunk.h:86 #13 pinyin::PhoneticLookup<2, 3>::get_nbest_match(_GArray*, pinyin::PhoneticKeyMatrix const*, pinyin::ForwardPhoneticConstraints const*, pinyin::NBestMatchResults*) at ../src/storage/phrase_index.h:731 #14 PY::FullPinyinEditor::insert(int) at PYPFullPinyinEditor.cc:56 #15 PY::PinyinEngine::processKeyEvent(unsigned int, unsigned int, unsigned int) at /usr/include/c++/9/bits/shared_ptr_base.h:1020 -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Fedora-i18n-bugs] [Bug 1752858] New: Combinations Reph (र्श्व) not rendering correctly with Harfbuzz in gedit
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1752858 Bug ID: 1752858 Summary: Combinations Reph (र्श्व) not rendering correctly with Harfbuzz in gedit Product: Fedora Version: 31 Status: NEW Component: lohit-devanagari-fonts Assignee: petersen(a)redhat.com Reporter: psatpute(a)redhat.com 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, sshedmak(a)redhat.com, vishalvijayraghavan(a)gmail.com Target Milestone: --- Classification: Fedora Created attachment 1615839 --> https://bugzilla.redhat.com/attachment.cgi?id=1615839&action=edit Image showing rendering issue Description of problem: Combination र्श्व is not rendering correctly in gedit/harfbuzz. But it works properly in Firefox Version-Release number of selected component (if applicable): lohit-devanagari-fonts 2.95.4-9 harfbuzz-2.6.0-1 How reproducible: Evertime Steps to Reproduce: 1. Open Terminal 2. Type commng: hb-view /usr/share/fonts/lohit-devanagari/Lohit-Devanagari.ttf र्श्व 3. Observe result Actual results: Reph not getting form. Expected results: Expected Reph should get formed. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1730242] New: unable to see ibus-sayura in Region panel
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1730242 Bug ID: 1730242 Summary: unable to see ibus-sayura in Region panel Product: Fedora Version: rawhide Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: pnemade(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: On Fedora 30 updated Silverblue system, I layered ibus-sayura package. Then tried to add it via Region panel. I cannot see it listed there. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Layer ibus-sayura package 2. reboot or you can ibus restart 3. try to add Sayura input using Region panel Actual results: There is no entry for Sayura in Region panel Expected results: It should allow to select Sayura Additional info: As I did not see Sayura, I executed "ibus write-cache" Then, I executed [parag@f30sb ~]$ ibus read-cache|grep -i sayura <description>Sayura Component</description> <exec>/usr/libexec/ibus-engine-sayura --ibus</exec> <textdomain>ibus-sayura</textdomain> <path mtime="0" >/usr/share/ibus/component/sayura.xml</path> <name>sayura</name> <longname>Sayura</longname> <description>Sayura Input Method</description> <icon>/usr/share/ibus-sayura/icons/ibus-sayura.png</icon> Then, [parag@f30sb ~]$ ibus list-engine|grep -i sayura no output for above command -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1689745] New: [abrt] ibus-libpinyin: pinyin_save(): ibus-engine-libpinyin killed by SIGSEGV
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1689745 Bug ID: 1689745 Summary: [abrt] ibus-libpinyin: pinyin_save(): ibus-engine-libpinyin killed by SIGSEGV Product: Fedora Version: 30 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:cb822be7ac46c50ce113ca1671deec6e2f6c4599; Component: ibus-libpinyin Assignee: pwu(a)redhat.com Reporter: robinlee.sysu(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 Description of problem: Crash when updating system Version-Release number of selected component: ibus-libpinyin-1.11.0-2.fc30 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-libpinyin --ibus crash_function: pinyin_save executable: /usr/libexec/ibus-engine-libpinyin journald_cursor: s=cc3b4d7aa103497a99d675649b9ae013;i=94c7;b=13573ad620e541ff8cacc1ad1ceca0c3;m=eea6a32;t=584549ca4b236;x=245f7212fc098115 kernel: 5.0.0-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 pinyin_save at pinyin.cpp:736 #1 PY::LibPinyinBackEnd::clearPinyinUserData at PYLibPinyin.cc:307 #2 PY::PinyinConfig::valueChanged at /usr/include/c++/9/bits/basic_string.h:2297 #3 PY::LibPinyinConfig::valueChangedCallback at /usr/include/c++/9/bits/char_traits.h:300 #8 g_settings_real_change_event at ../gio/gsettings.c:391 #9 ffi_call_unix64 at ../src/x86/unix64.S:76 #10 ffi_call at ../src/x86/ffi64.c:525 #11 g_cclosure_marshal_generic_va at ../gobject/gclosure.c:1614 #12 _g_closure_invoke_va at ../gobject/gclosure.c:873 #15 settings_backend_path_changed at ../gio/gsettings.c:466 Potential duplicate: bug 1649100 -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Fedora-i18n-bugs] [Bug 1738159] New: tomoe depends on Python 2
by bugzilla＠redhat.com 22 Sep '20

22 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1738159 Bug ID: 1738159 Summary: tomoe depends on Python 2 Product: Fedora Version: rawhide Status: NEW Component: tomoe Assignee: pwu(a)redhat.com Reporter: lbalhar(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dingyichen(a)gmail.com, i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, pwu(a)redhat.com, tagoh(a)redhat.com Blocks: 1698500 (F31_PY2REMOVAL) Target Milestone: --- Classification: Fedora Python 2.7 will reach end-of-life in January 2020, over 9 years after it was released. This falls within the Fedora 31 lifetime. Packages that depend on Python 2 are being switched to Python 3 or removed from Fedora: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#In… Python 2 will be retired in Fedora 32: https://fedoraproject.org/wiki/Changes/RetirePython2 To help planning, we'd like to know the plans for tomoe's future. Specifically: - What is the reason for the Python2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?) - What are the upstream/community plans/timelines regarding Python 3? - What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?) This bug is filed semi-automatically, and might not have all the context specific to tomoe. If you need anything from us, or something is unclear, please mention it here. Thank you. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1698500 [Bug 1698500] F31 Mass Python 2 Package Removal -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Fedora-i18n-bugs] [Bug 1672442] New: Bug that will not accept input from keyboard
by bugzilla＠redhat.com 02 Sep '20

02 Sep '20

https://bugzilla.redhat.com/show_bug.cgi?id=1672442 Bug ID: 1672442 Summary: Bug that will not accept input from keyboard Product: Fedora Version: 29 OS: Linux Status: NEW Component: ibus Severity: medium Assignee: tfujiwar(a)redhat.com Reporter: qqke6wd9k(a)apricot.ocn.ne.jp 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 input characters, sometimes this bug occurs, the PC will not accept input from the keyboard morever. Since it accepts mouse operation, logout and shutdown are possible. When I log out and re-login, PC is able to accept only direct input (English). Also, the IME icon on the task bar is lost. It will also be impossible to switch input modes. I am a Japanese user, but when after login, I cannot enter Japanese characters. After this bug occurrence, only English characters can be entered. Version-Release number of selected component (if applicable): How reproducible: everyday Steps to Reproduce: 1.Open an application that can enter letters (eg gedit or Firefox) 2.keep typing characters until this bug occurs. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Fedora-i18n-bugs] [Bug 1750891] New: font cache not getting update on Silverblue 31?
by bugzilla＠redhat.com 01 Aug '20

01 Aug '20

https://bugzilla.redhat.com/show_bug.cgi?id=1750891 Bug ID: 1750891 Summary: font cache not getting update on Silverblue 31? Product: Fedora Version: 31 Status: NEW Component: fontconfig Assignee: tagoh(a)redhat.com Reporter: pnemade(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, 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, pnemade(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: I have this system state [parag@localhost ~]$ rpm-ostree status State: idle AutomaticUpdates: disabled Deployments: ● ostree://fedora:fedora/31/x86_64/silverblue Version: 31.20190909.n.0 (2019-09-09T08:24:14Z) BaseCommit: 093a07e18c0514e47e978c9c33ef73a2615117db343e0eef7218c298b1e3502c GPGSignature: Valid signature by 7D22D5867F2A4236474BF7B850CB390B3C3359C4 LayeredPackages: gedit gnome-tweaks hunspell-hi langpacks-hi libreoffice-core ostree://fedora:fedora/31/x86_64/silverblue Version: 31.20190909.n.0 (2019-09-09T08:24:14Z) BaseCommit: 093a07e18c0514e47e978c9c33ef73a2615117db343e0eef7218c298b1e3502c GPGSignature: Valid signature by 7D22D5867F2A4236474BF7B850CB390B3C3359C4 LayeredPackages: gedit gnome-tweaks hunspell-hi libreoffice-core [parag@localhost ~]$ rpm-ostree db diff ostree diff commit from: rollback deployment (0ad271d38c5aa4e1ce194ea625f83862d2c317774d96ba9b94d53c5324133265) ostree diff commit to: booted deployment (61f7aea98b458e53e42e85131e62ad7c84f80592676f28949cc5aa411e34ff55) Added: glibc-langpack-hi-2.30-1.fc31.x86_64 google-noto-sans-devanagari-ui-vf-fonts-20181223-6.fc31.noarch google-noto-sans-devanagari-vf-fonts-20181223-6.fc31.noarch hyphen-hi-1:0.7.0-14.fc31.noarch langpacks-core-hi-2.0-6.fc31.noarch langpacks-hi-2.0-6.fc31.noarch libreoffice-help-hi-1:6.3.1.2-1.fc31.x86_64 libreoffice-langpack-hi-1:6.3.1.2-1.fc31.x86_64 samyak-devanagari-fonts-1.2.2-22.fc31.noarch samyak-fonts-common-1.2.2-22.fc31.noarch [parag@localhost ~]$ fc-list :lang=hi /usr/share/fonts/lohit-devanagari/Lohit-Devanagari.ttf: Lohit Devanagari:style=Regular /usr/share/fonts/google-droid/DroidSansDevanagari-Regular.ttf: Droid Sans:style=Regular [parag@localhost ~]$ Version-Release number of selected component (if applicable): fontconfig-2.13.92-2.fc31.x86_64 How reproducible: always Steps to Reproduce: 1. on F31, install any langpacks which will install additional fonts packages like langpacks-hi 2. execute fc-list :lang=hi 3. Actual results: "fc-list :lang=hi" output remained same Expected results: "fc-list :lang=hi" should included rencently installed font packages as well Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Fedora-i18n-bugs] [Bug 1737785] New: CVE-2019-1010238 pango: heap based buffer overflow can be used to get code execution
by bugzilla＠redhat.com 30 Apr '20

30 Apr '20

https://bugzilla.redhat.com/show_bug.cgi?id=1737785 Bug ID: 1737785 Summary: CVE-2019-1010238 pango: heap based buffer overflow can be used to get code execution Product: Security Response Hardware: All OS: Linux Status: NEW Component: vulnerability Keywords: Security Severity: high Priority: high Assignee: security-response-team(a)redhat.com Reporter: mrehak(a)redhat.com CC: caillon+fedoraproject(a)gmail.com, eng-i18n-bugs(a)redhat.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: Other Gnome Pango 1.42 and later is affected by: Buffer Overflow. The impact is: The heap based buffer overflow can be used to get code execution. The component is: function name: pango_log2vis_get_embedding_levels, assignment of nchars and the loop condition. The attack vector is: Bug can be used when application pass invalid utf-8 strings to functions like pango_itemize. External References: https://packetstormsecurity.com/files/153838/USN-4081-1.txt -- You are receiving this mail because: You are on the CC list for the bug.

1 32

[Fedora-i18n-bugs] [Bug 1735152] New: eclipse-nls: FTBFS in Fedora rawhide/f31
by bugzilla＠redhat.com 10 Apr '20

10 Apr '20

https://bugzilla.redhat.com/show_bug.cgi?id=1735152 Bug ID: 1735152 Summary: eclipse-nls: FTBFS in Fedora rawhide/f31 Product: Fedora Version: rawhide Status: NEW Component: eclipse-nls Assignee: sean+rh(a)flanigan.org Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, sean+rh(a)flanigan.org Blocks: 1732841 Target Milestone: --- Classification: Fedora eclipse-nls failed to build from source in Fedora rawhide/f31 https://koji.fedoraproject.org/koji/taskinfo?taskID=36633177 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild Please fix eclipse-nls 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, eclipse-nls will be orphaned. Before branching of Fedora 32, eclipse-nls will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://fedoraproject.org/wiki/Fails_to_build_from_source Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1732841 [Bug 1732841] (F31FTBFS) - Fedora 31 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Fedora-i18n-bugs] [Bug 1739051] New: tomoe-gtk depends on Python 2
by bugzilla＠redhat.com 10 Apr '20

10 Apr '20

https://bugzilla.redhat.com/show_bug.cgi?id=1739051 Bug ID: 1739051 Summary: tomoe-gtk depends on Python 2 Product: Fedora Version: rawhide Status: NEW Component: tomoe-gtk Assignee: extras-orphan(a)fedoraproject.org Reporter: lbalhar(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dingyichen(a)gmail.com, extras-orphan(a)fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Blocks: 1698500 (F31_PY2REMOVAL) Target Milestone: --- Classification: Fedora Python 2.7 will reach end-of-life in January 2020, over 9 years after it was released. This falls within the Fedora 31 lifetime. Packages that depend on Python 2 are being switched to Python 3 or removed from Fedora: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#In… Python 2 will be retired in Fedora 32: https://fedoraproject.org/wiki/Changes/RetirePython2 To help planning, we'd like to know the plans for tomoe-gtk's future. Specifically: - What is the reason for the Python2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?) - What are the upstream/community plans/timelines regarding Python 3? - What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?) This bug is filed semi-automatically, and might not have all the context specific to tomoe-gtk. If you need anything from us, or something is unclear, please mention it here. Thank you. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1698500 [Bug 1698500] F31 Mass Python 2 Package Removal -- You are receiving this mail because: You are on the CC list for the bug.

1 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs September 2019