i18n-bugs August 2019

i18n-bugs@lists.fedoraproject.org

2 participants
87 discussions

[Fedora-i18n-bugs] [Bug 1733869] New: gettext: Getting errors in double free with msgfmt command.
by bugzilla＠redhat.com 13 Dec '22

13 Dec '22

https://bugzilla.redhat.com/show_bug.cgi?id=1733869 Bug ID: 1733869 Summary: gettext: Getting errors in double free with msgfmt command. Product: Fedora Version: 30 Status: NEW Component: gettext Assignee: panovotn(a)redhat.com Reporter: poyadav(a)redhat.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, panovotn(a)redhat.com, petersen(a)redhat.com, praiskup(a)redhat.com, suanand(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Error in poc, please refer the result section for details. Version-Release number of selected component (if applicable): gettext-0.19.8.1-18.fc30.x86_64 How reproducible: Always Steps to Reproduce: 1. Clone https://github.com/CCCCCrash/POCs.git. 2. Run valgrind msgfmt poc command. 3. Observe the output. Actual results: [poyadav@localhost doublefree]$ valgrind msgfmt poc ==8072== Memcheck, a memory error detector ==8072== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==8072== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==8072== Command: msgfmt poc ==8072== ==8072== Conditional jump or move depends on uninitialised value(s) ==8072== at 0x48D9940: freea (in /usr/lib64/libgettextlib-0.19.8.1.so) ==8072== by 0x487E8EA: po_lex_charset_set (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x487E098: po_gram_parse (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x487EB9A: ??? (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x487A773: catalog_reader_parse (in /usr/lib64/libgettextsrc-0.19.8.1.so) ==8072== by 0x10E7C7: ??? (in /usr/bin/msgfmt) ==8072== by 0x10D8EB: ??? (in /usr/bin/msgfmt) ==8072== by 0x4AABF32: (below main) (in /usr/lib64/libc-2.29.so) ==8072== poc:17: duplicate message definition... poc:16: ...this is the location of the first definition poc:18:3: syntax error poc:18: keyword "n" unknown poc:19: end-of-line within string poc:28: duplicate message definition... poc:24: ...this is the location of the first definition poc:35: keyword "msgud_plural" unknown poc:34: missing 'msgstr' section poc:35:13: syntax error poc:40: end-of-line within string poc:46: end-of-line within string poc: warning: Charset missing in header. Message conversion to user's charset will not work. poc:42: duplicate message definition... poc:6: ...this is the location of the first definition poc:46:2: syntax error poc:46: keyword "Ep" unknown poc:47: keyword "C" unknown poc:48: keyword "s" unknown poc:49: keyword "bo" unknown poc:50: keyword "S" unknown poc:50:236: invalid control sequence poc:50:397: invalid control sequence poc:51: end-of-line within string msgfmt: too many errors, aborting ==8072== ==8072== HEAP SUMMARY: ==8072== in use at exit: 59,783 bytes in 123 blocks ==8072== total heap usage: 547 allocs, 424 frees, 99,479 bytes allocated ==8072== ==8072== LEAK SUMMARY: ==8072== definitely lost: 650 bytes in 82 blocks ==8072== indirectly lost: 0 bytes in 0 blocks ==8072== possibly lost: 0 bytes in 0 blocks ==8072== still reachable: 59,133 bytes in 41 blocks ==8072== suppressed: 0 bytes in 0 blocks ==8072== Rerun with --leak-check=full to see details of leaked memory ==8072== ==8072== Use --track-origins=yes to see where uninitialised values come from ==8072== For lists of detected and suppressed errors, rerun with: -s ==8072== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Expected results: No errors. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Fedora-i18n-bugs] [Bug 1659748] New: Characters get deleted as you type
by bugzilla＠redhat.com 13 Oct '21

13 Oct '21

https://bugzilla.redhat.com/show_bug.cgi?id=1659748 Bug ID: 1659748 Summary: Characters get deleted as you type Product: Fedora Version: 29 Status: NEW Component: ibus-m17n Severity: high Assignee: pnemade(a)redhat.com Reporter: lohang(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com, shawn.p.huang(a)gmail.com Target Milestone: --- Classification: Fedora Description of problem: When you type Sinhala using Wijesekera keyboard layout through ibus the first character gets deleted as soon as you start typing the second character. This is similar to the bug previously reported for Fedora 28 https://bugzilla.redhat.com/show_bug.cgi?id=1617978 How reproducible: (1) Steps to Reproduce: 1. Open Libre Office Writer (6.1.2.1) 2. Switch to Sinhala; Sinhalese (wijesekera (m17n)) 3. Type keys vksIal kjSka 4. Hit space to separate the second word from the first word. And hit space at the end of the first word. Actual results: ක වීන් Expected results: ඩනිෂ්ක නවීන් Additional info: (2) When you try this with emacs the results are a little different. I am including it here assuming this is related to the same issue: This is how to reproduce with emacs: 1. Open emacs 26.1 (build 1, x86_64-redhat-linux-gnu, GTK+ Version 3.23.2) of 2018-08-13 2. Switch to Sinhala; Sinhalese (wijesekera (m17n)) 3. Type keys vksIal kjSka 4. Hit space to separate the second word from the first word. And hit space at the end of the first word. Actual results: ඩනිෂ් කනවී න් Expected results: ඩනිෂ්ක නවීන් This adds a space before the last character of the first word, not where you want the space to be. -- You are receiving this mail because: You are on the CC list for the bug.

1 49

[Fedora-i18n-bugs] [Bug 1677534] New: texttopaps OOMs with 4GB text file!
by bugzilla＠redhat.com 28 Jun '21

28 Jun '21

https://bugzilla.redhat.com/show_bug.cgi?id=1677534 Bug ID: 1677534 Summary: texttopaps OOMs with 4GB text file! Product: Fedora Version: rawhide Hardware: x86_64 OS: Linux Status: NEW Component: paps Severity: high Assignee: tagoh(a)redhat.com Reporter: petersen(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: desktop-qa-list(a)redhat.com, eng-i18n-bugs(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, rhel(a)vlasiu.net, tagoh(a)redhat.com Depends On: 1635160 Target Milestone: --- Classification: Fedora (Cloned from a RHEL7 report) +++ This bug was initially created as a clone of Bug #1635160 +++ Description of problem: Trying to print with cups a 4Gb text file fail. texttopaps consume all the memory and is killed bye the system: [1023082.003989] Out of memory: Kill process xxxx (texttopaps) score 955 or sacrifice child [1023082.005120] Killed process xxxx (texttopaps) total-vm:19958848kB, anon-rss:7531872kB, file-rss:84kB, shmem-rss:0kB /usr/lib/cups/filter/texttopaps 1 user1 "example" 1 "" sample-4Gb.txt --- Additional comment from Akira TAGOH on 2018-10-03 11:54:48 SGT --- Hmm, that log says it all. I don't think OOM is a software bug. --- Additional comment from GV on 2018-10-03 13:00:48 SGT --- Of course OOM is not a software bug. Where exactly did I said that? The problem is texttopaps that allocate memory out of control. texttopaps should allocate memory, use-it, release-it. Like any sane program. The issue was not present on RHEL 6. I had printed the same file multiple times with cups on RHEL6 and it worked just fine (not sure it was texttopaps cups filter involved). Printing the file does not work on RHEL 7 and it should. The 4Gb file is a testcase for our application we develop. --- Additional comment from Jens Petersen on 2018-10-18 17:49:35 SGT --- I don't think the paps in RHEL7 is significantly different from RHEL6. As you say it could be due to changes in Cups? The cups versions in RHEL 6, 7 and Fedora are certainly quite different. Unless texttopaps really worked in RHEL6 it might make to reassign this to cups? --- Additional comment from GV on 2018-10-25 18:29:46 SGT --- Since the real computer running RHEL 6 was already scrapped, I tried to make a virtual machine using RHEL 6. Unfortunately, now I also get a crash on RHEL 6 when printing the 4GB file. I can't recall how much memory was in that computer. The virtual machine had 8Gb of memory allocated. Still, it does not matter that much. I think texttopaps have an issue and it should be fixed or at least an workaround should be available (other than 'don't print a file that large'). I'm afraid this is not a cups issue since I can reproduce the issue running the texttopaps standalone. Sincerely, Gabriel --- Additional comment from Akira TAGOH on 2018-11-16 17:59:04 SGT --- paps isn't supposed to work with large files. to support it, most of code needs to rewritten. this isn't realistic to provide an update for existing products. for a workaround, you can remove paps package (or simply remove /usr/share/cups/mime/paps.convs file) to fall back the text filter to texttops which CUPS originally provides. this should works for this issue and as long as you don't need the internationalization support for printing. Hope that helps. --- Additional comment from GV on 2018-12-07 14:03:33 SGT --- It helps. Thank you! Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1635160 [Bug 1635160] texttopaps OOMs with 4GB text file! -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Fedora-i18n-bugs] [Bug 1711646] New: Scriptlet error when updating through SSH
by bugzilla＠redhat.com 09 May '21

09 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1711646 Bug ID: 1711646 Summary: Scriptlet error when updating through SSH Product: Fedora Version: 30 Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: dreua(a)posteo.de 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 update or reinstall ibus-1.5.20-4.fc30 over SSH, dnf outputs the error "X11 connection rejected because of wrong authentication.". This is caused by https://src.fedoraproject.org/rpms/ibus/blob/master/f/ibus.spec#_338 running `sudo ibus write-cache --system` results in the same error when called over SSH. Version-Release number of selected component (if applicable): ibus-1.5.20-4.fc30 How reproducible: Always over SSH, never when using the terminal directly on the machine. Steps to Reproduce: 1. Reinstall or update to ibus-1.5.20-4.fc30 Actual results: Running scriptlet: ibus-1.5.20-4.fc30.x86_64 X11 connection rejected because of wrong authentication. X11 connection rejected because of wrong authentication. Verifying : ibus-1.5.20-4.fc30.x86_64 Expected results: Running scriptlet: ibus-1.5.20-4.fc30.x86_64 Verifying : ibus-1.5.20-4.fc30.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Fedora-i18n-bugs] [Bug 1707001] New: Ibus-pinyin ERROR
by bugzilla＠redhat.com 12 Jan '21

12 Jan '21

https://bugzilla.redhat.com/show_bug.cgi?id=1707001 Bug ID: 1707001 Summary: Ibus-pinyin ERROR Product: Fedora Version: 30 Hardware: All OS: Linux Status: NEW Component: ibus-pinyin Severity: urgent Assignee: pwu(a)redhat.com Reporter: 1990konger(a)gmail.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 Description of problem: The input method is incorrect and cannot be recognized correctly. The text to be entered is required. For example, 'nihao' should be right, '你好'. Now enter 'nihao' to show 'niha o'.Unrecognized what you need 'ni' is a word. 'hao' is a word. 'ha' is a word but the display is wrong at this time and cannot be selected. Unable to recognize 'hao'. Affect all input suggestions to withdraw to the old version Version-Release number of selected component (if applicable): Name : ibus-pinyin Version : 1.5.0 Release : 16.fc30 How reproducible: 'nihao' is meaning is 'Hello' 'niha o', it is an error Steps to Reproduce: 1.All Chinese input is wrong Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Fedora-i18n-bugs] [Bug 1703849] New: [pango] pango-view fails for backend ft2 because of missing dependency on ImageMagick
by bugzilla＠redhat.com 21 Oct '20

21 Oct '20

https://bugzilla.redhat.com/show_bug.cgi?id=1703849 Bug ID: 1703849 Summary: [pango] pango-view fails for backend ft2 because of missing dependency on ImageMagick Product: Fedora Version: 29 Hardware: x86_64 OS: Linux Status: NEW Component: pango Assignee: tagoh(a)redhat.com Reporter: jfrieben(a)hotmail.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: Using pango-view with backend ft2 in a current Fedora 29 Workstation installation fails because pango-view tries to launch the display utility from ImageMagick which has not been pulled in as a dependency. Version-Release number of selected component (if applicable): pango-1.42.4-2.fc29 How reproducible: Always Steps to Reproduce: 1. Launch GNOME session of a current Fedora 29 Workstation installation. 2. Run 'pango-view --backend=ft2 -t PANGO'. Actual results: Utility pango-view aborts with the error message: "pango-view: When running ImageMagick 'display' command: Failed to execute child process “display” (No such file or directory)" Expected results: Utility pango-view displays the sample text. Additional info: - Installing package ImageMagick prior to running pango-view ensures correct execution. Therefore, adding ImageMagick as a requirement of package pango solves this issue. - It is probably preferable to patch pango-view such that it calls "gm display" from package GraphicsMagick and to pull in the latter instead of ImageMagick. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs August 2019