i18n-bugs August 2020

i18n-bugs@lists.fedoraproject.org

2 participants
110 discussions

[Fedora-i18n-bugs] [Bug 1786596] New: Vertical alignment is off with PANGO_GRAVITY_EAST and PANGO_GRAVITY_HINT_LINE
by bugzilla＠redhat.com 26 Aug '21

26 Aug '21

https://bugzilla.redhat.com/show_bug.cgi?id=1786596 Bug ID: 1786596 Summary: Vertical alignment is off with PANGO_GRAVITY_EAST and PANGO_GRAVITY_HINT_LINE Product: Fedora Version: 31 OS: Linux Status: NEW Component: pango Assignee: pwu(a)redhat.com Reporter: abetakehiko(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: Japanese chars and Latin chars in the same line do not vertically align when the pango context's gravity is set to PANGO_GRAVITY_EAST and its hint set to PANGO_GRAVITY_HINT_LINE. Version-Release number of selected component (if applicable): pango-1.44.7-1.fc31.x86_64 How reproducible: Always Steps to Reproduce: pango-view --text="あーいうえお abcde" --gravity east --gravity-hint line --font="NotoSerifJP 24" Actual results: Japanese chars and Latin chars in the same line do not vertically align. Expected results: Japanese chars and Latin chars in the same line vertically align as before. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[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 1832098] New: Due to socket path changes ibus not working in F32 Wayland for qt4 apps
by bugzilla＠redhat.com 26 May '21

26 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1832098 Bug ID: 1832098 Summary: Due to socket path changes ibus not working in F32 Wayland for qt4 apps Product: Fedora Version: 32 Status: NEW Component: ibus-qt Severity: high Assignee: tfujiwar(a)redhat.com Reporter: petersen(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: Due to changes in socket path for Wayland, ibus input does not work for qt4 apps under Wayland in Fedora 32. https://github.com/ibus/ibus-qt/pull/5 Version-Release number of selected component (if applicable): ibus-qt-1.3.3-22.fc31 How reproducible: 100% -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Fedora-i18n-bugs] [Bug 1836327] New: Hangul text commit and key forward don't preserve order sometimes
by bugzilla＠redhat.com 25 May '21

25 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1836327 Bug ID: 1836327 Summary: Hangul text commit and key forward don't preserve order sometimes Product: Fedora Version: 32 Hardware: x86_64 OS: Linux Status: NEW Component: ibus Severity: medium Assignee: tfujiwar(a)redhat.com Reporter: edward.park0203(a)gmail.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: Hangul text commit and key forward don't preserve order sometimes Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Fedora-i18n-bugs] [Bug 1753295] New: Pango no longer supports bitmap fonts
by bugzilla＠redhat.com 25 May '21

25 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1753295 Bug ID: 1753295 Summary: Pango no longer supports bitmap fonts Product: Fedora Version: 31 Status: NEW Component: pango Assignee: tagoh(a)redhat.com Reporter: jsbillin(a)umich.edu 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 bitmap fonts, so font packages like terminus-fonts and ucs-miscfixed-fonts no longer appear in GNOME applications that use pango, such as Terminal. If you did a dnf system-upgrade from Fedora 30 and were using a bitmap font like Terminus, all your terminals will show the rectangular placeholders the first time you start a terminal. Bitmap fonts like terminus and ucs-miscfixed are much easier to read in a terminal since they are pixel perfect. If Fedora 31 is going to disable support for bitmap fonts, it needs to be announced and the package maintainers of those bitmap font packages are going to need to find a way to convert their fonts. Version-Release number of selected component (if applicable): pango-1.44.6-1.fc31.x86_64 How reproducible: always Steps to Reproduce: 1. install 'terminus-fonts' 2. Start GNOME terminal 3. Open Terminal Preferences 4. Attempt to change the font to Terminus font Actual results: If you upgraded from Fedora 30 and had Terminus fonts as the default font, the first time you launch Terminal, all the text will be the rectangular placeholders. If you search for the Terminus font in the preferences, you won't be able to find it. Expected results: Use the Terminus font as usual Additional info: It appears that pango switched from using FreeType to HarfBuzz, which only supports truetype. I rebuilt the Fedora 30 pango package (1.43) for Fedora 31, downgraded it, and now my terminals are fine showing my bitmap fonts. -- You are receiving this mail because: You are on the CC list for the bug.

1 127

[Fedora-i18n-bugs] [Bug 1830709] New: Invalid metainfo files
by bugzilla＠redhat.com 16 May '21

16 May '21

https://bugzilla.redhat.com/show_bug.cgi?id=1830709 Bug ID: 1830709 Summary: Invalid metainfo files Product: Fedora Version: 32 Status: NEW Component: google-noto-fonts Assignee: petersen(a)redhat.com Reporter: mohd.akram(a)outlook.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, pwu(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Metainfo files provided by the package are deemed invalid by appstream. Version-Release number of selected component (if applicable): 20181223-7.fc32 How reproducible: Always. Steps to Reproduce: 1. appstreamcli validate /usr/share/metainfo/google-noto-sans-sinhala-vf.metainfo.xml Actual results: E: google-noto-sans-sinhala-vf:~: font-no-font-data E: google-noto-sans-sinhala-vf:4: cid-is-not-rdns google-noto-sans-sinhala-vf I: google-noto-sans-sinhala-vf:~: font-description-missing E: google-noto-sans-sinhala-vf:~: component-summary-missing E: google-noto-sans-sinhala-vf:~: component-name-missing E: google-noto-sans-sinhala-vf:~: extends-not-allowed I: google-noto-sans-sinhala-vf:4: cid-contains-hyphen google-noto-sans-sinhala-vf Validation failed: errors: 5, infos: 2 Expected results: Validation was successful. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[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 1749943] New: pango contain header with wrong hb.h include
by bugzilla＠redhat.com 08 Mar '21

08 Mar '21

https://bugzilla.redhat.com/show_bug.cgi?id=1749943 Bug ID: 1749943 Summary: pango contain header with wrong hb.h include Product: Fedora Version: rawhide Status: NEW Component: pango Assignee: tagoh(a)redhat.com Reporter: vascom2(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: I am try to build eiskaltdcpp and it fsilrd with error: BUILDSTDERR: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory BUILDSTDERR: 28 | #include <hb.h> BUILDSTDERR: | ^~~~~~ Full build log https://kojipkgs.fedoraproject.org/work/tasks/5226/37235226/build.log Version-Release number of selected component (if applicable): pango-1.44.6-1.fc32 How reproducible: Always. As I see this line was added in pango 1.44. But harfbuzz's hb.h in Fedora placed at /usr/include/harfbuzz/ Need to solve it for build other packages. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Fedora-i18n-bugs] [Bug 1807534] New: pyzy requires Python 2 to build
by bugzilla＠redhat.com 18 Jan '21

18 Jan '21

https://bugzilla.redhat.com/show_bug.cgi?id=1807534 Bug ID: 1807534 Summary: pyzy requires Python 2 to build Product: Fedora Version: rawhide Status: NEW Component: pyzy Assignee: pwu(a)redhat.com Reporter: pviktori(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, pwu(a)redhat.com Blocks: 1803205 (BRPY27) Target Milestone: --- Classification: Fedora Python 2 reached upstream end-of-life in January 2020. In Fedora Rawhide, it's now provided from the compat package `python27`. Packages that only use Python 2 at build time, like pyzy, had a general exception to keep using it in Fedora 31. Now, the dependency should be removed. Let us know if you need any help investigating or removing the dependency. (There are dozens of packages like this, so we didn't investigate this one thoroughly. We assume you know the package best.) If it's possible that the dependency won't be removed in Fedora 33. Please request a FESCo exception. You can refer to the exception for mercurial as an example: https://pagure.io/fesco/issue/2243 It's good to mention: - What is the reason for the Python 2 build dependency? - What are the upstream/community plans/timelines regarding Python 2? - What is the guidance for porting the build 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?) If you need anything from us, or something is unclear, please mention it here. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1803205 [Bug 1803205] Tracking: Packages BuildRequiring python27 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs August 2020