June 2020 - i18n-bugs - Fedora Mailing-Lists

[Fedora-i18n-bugs] [Bug 1832098] New: Due to socket path changes ibus not working in F32 Wayland for qt4 apps

by bugzilla＠redhat.com

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.

2 years, 11 months

1
11
0 / 0

[Fedora-i18n-bugs] [Bug 1836327] New: Hangul text commit and key forward don't preserve order sometimes

by bugzilla＠redhat.com

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.

2 years, 11 months

1
8
0 / 0

[Fedora-i18n-bugs] [Bug 1753295] New: Pango no longer supports bitmap fonts

by bugzilla＠redhat.com

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.

2 years, 11 months

1
127
0 / 0

[Fedora-i18n-bugs] [Bug 1830709] New: Invalid metainfo files

by bugzilla＠redhat.com

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.

2 years, 11 months

1
12
0 / 0

[Fedora-i18n-bugs] [Bug 1711646] New: Scriptlet error when updating through SSH

by bugzilla＠redhat.com

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.

2 years, 11 months

1
22
0 / 0

[Fedora-i18n-bugs] [Bug 1749943] New: pango contain header with wrong hb.h include

by bugzilla＠redhat.com

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.

3 years, 1 month

1
3
0 / 0

[Fedora-i18n-bugs] [Bug 1807534] New: pyzy requires Python 2 to build

by bugzilla＠redhat.com

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.

3 years, 3 months

1
5
0 / 0

[Fedora-i18n-bugs] [Bug 1707001] New: Ibus-pinyin ERROR

by bugzilla＠redhat.com

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.

3 years, 3 months

1
8
0 / 0

[Fedora-i18n-bugs] [Bug 1843643] New: Space bar wrongly mapping to "switch IME" on first login (plasma + ibus)

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=1843643 Bug ID: 1843643 Summary: Space bar wrongly mapping to "switch IME" on first login (plasma + ibus) Product: Fedora Version: 31 Hardware: x86_64 OS: Linux Status: NEW Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: billcrawford1970(a)googlemail.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: When I first login and open a konsole window, spaces don't get input to the shell, but seem to cause an input method switch. Version-Release number of selected component (if applicable): 1.5.21-9.fc31 How reproducible: Log in. Try to type. Steps to Reproduce: 1. Choose ibus using im-chooser, configure Meta + Space as IME switcher 2. Reboot machine 3. Log in Actual results: Typing a space doesn't enter a space in the terminal, but switches IME. Expected results: Entering a space enters a space. Additional info: · Configured "switch engine" shortcut it Meta + Space. · Meta is Right Win Key, configured in KDE system settings. · I suspect there is a startup ordering issue between keyboard layout configuration and ibus starting. · Restarting ibus (via right-click on "ibus panel" notification icon) fixes it. It also causes the icon to reappear to the left of the "keyboard layout" icon, which bolsters my suspicion this is an ordering issue. -- You are receiving this mail because: You are on the CC list for the bug.

3 years, 5 months

1
4
0 / 0

[Fedora-i18n-bugs] [Bug 1787190] New: Windows+ Space shortcut opened KRunner instead of switch keyboard (ibus) in KDE plasma

by bugzilla＠redhat.com

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.

3 years, 5 months

1
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs June 2020