i18n-bugs May 2020

i18n-bugs@lists.fedoraproject.org

1 participants
151 discussions

[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 17 May '21

17 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

[Fedora-i18n-bugs] [Bug 1787190] New: Windows+ Space shortcut opened KRunner instead of switch keyboard (ibus) in KDE plasma
by bugzilla＠redhat.com 04 Nov '20

04 Nov '20

https://bugzilla.redhat.com/show_bug.cgi?id=1787190 Bug ID: 1787190 Summary: Windows+ Space shortcut opened KRunner instead of switch keyboard (ibus) in KDE plasma Product: Fedora Version: 31 Status: NEW Component: kf5-plasma Keywords: i18n Assignee: me(a)dvratil.cz Reporter: aalam(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, jgrulich(a)redhat.com, kde-sig(a)lists.fedoraproject.org, me(a)dvratil.cz, rdieter(a)gmail.com, than(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: after updating KDE with Fedora 31, Windows+Space is opening 'Krunner', but not switching keyboard (which is default shortcut for ibus keybaord switch). Krunner is not running with Alt+F2 Krunner is running with Windows +F2 Version-Release number of selected component (if applicable): plasma-desktop-5.17.4-1.fc31.x86_64 plasma-nm-openswan-5.17.4-1.fc31.x86_64 plasma-desktop-doc-5.17.4-1.fc31.noarch plasma-browser-integration-5.17.4-1.fc31.x86_64 plasma-workspace-5.17.4-1.fc31.x86_64 plasma-nm-vpnc-5.17.4-1.fc31.x86_64 plasma-workspace-common-5.17.4-1.fc31.x86_64 plasma-nm-5.17.4-1.fc31.x86_64 plasma-workspace-geolocation-5.17.4-1.fc31.x86_64 plasma-milou-5.17.4-1.fc31.x86_64 plasma-integration-5.17.4-1.fc31.x86_64 plasma-discover-5.17.4-1.fc31.x86_64 plasma-nm-openvpn-5.17.4-1.fc31.x86_64 plasma-breeze-5.17.4-1.fc31.x86_64 plasma-drkonqi-5.17.4-1.fc31.x86_64 kdeplasma-addons-5.17.4-1.fc31.x86_64 plasma-user-manager-5.17.4-1.fc31.x86_64 plasma-pk-updates-0.3.2-4.fc31.x86_64 plasma-nm-l2tp-5.17.4-1.fc31.x86_64 plasma-nm-openconnect-5.17.4-1.fc31.x86_64 kf5-plasma-5.64.0-1.fc31.x86_64 plasma-workspace-geolocation-libs-5.17.4-1.fc31.x86_64 plasma-lookandfeel-fedora-5.17.4-1.fc31.noarch plasma-nm-pptp-5.17.4-1.fc31.x86_64 plasma-workspace-libs-5.17.4-1.fc31.x86_64 plasma-systemsettings-5.17.4-1.fc31.x86_64 kde-settings-plasma-31.0-1.fc31.noarch glibc-2.30-8.fc31.x86_64 glibc-langpack-pa-2.30-8.fc31.x86_64 glibc-langpack-en-2.30-8.fc31.x86_64 glibc-all-langpacks-2.30-8.fc31.x86_64 glibc-common-2.30-8.fc31.x86_6 ibus-setup-1.5.21-5.fc31.noarch ibus-gtk3-1.5.21-5.fc31.x86_64 ibus-m17n-1.4.1-3.fc31.x86_64 ibus-gtk2-1.5.21-5.fc31.x86_64 ibus-qt-1.3.3-22.fc31.x86_64 ibus-libs-1.5.21-5.fc31.x86_64 ibus-1.5.21-5.fc31.x86_64 How reproducible: Everytime after updating Fedora 31 KDE desktop with latest package Steps to Reproduce: 1. Fresh install KDE Plasma with language (Punjabi, Hindi, any language using iBus) 2. try to input by switching keyboard (ibus) pressing Windows+Space 3. sudo dnf update 4. Reboot 5. try to input by switching keyboard (ibus) pressing Windows+Space Actual results: Opened 'KRunner' Expected results: input keyboard layout should switch with 'Windows+space'. Krunner should run with 'Alt+F2', which is not working Additional info: before updating, opened system setting -> Shortcut -> Global Shortcut - There is NO krunner' After update, system setting -> Shortcut -> Global Shortcut -> Krunner (this is something new) -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[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 1797926] New: Korean Baekmuk fonts does not map missing glyphs to id 0
by bugzilla＠redhat.com 21 Oct '20

21 Oct '20

https://bugzilla.redhat.com/show_bug.cgi?id=1797926 Bug ID: 1797926 Summary: Korean Baekmuk fonts does not map missing glyphs to id 0 Product: Fedora Version: 31 Hardware: All OS: All Status: NEW Component: baekmuk-ttf-fonts Severity: medium Assignee: pwu(a)redhat.com Reporter: matt(a)nightrealms.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, pwu(a)redhat.com Target Milestone: --- Classification: Fedora From https://bugs.chromium.org/p/chromium/issues/detail?id=1042994 "So the font, does not map missing characters to a glyph id 0, missing glyph id, but instead maps it to a glyph named '.null', glyph id 12505." The result is that when Chrome tries to display the Korean characters listed at http://www.alanwood.net/unicode/hangul-jamo-extended-b.html the characters come out as blank. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs May 2020