i18n-bugs October 2023

i18n-bugs@lists.fedoraproject.org

1 participants
104 discussions

[Bug 2237664] New: Emoji categories dialog has different state on cursor with keyboard and mouse
by bugzilla＠redhat.com 20 Dec '25

20 Dec '25

https://bugzilla.redhat.com/show_bug.cgi?id=2237664 Bug ID: 2237664 Summary: Emoji categories dialog has different state on cursor with keyboard and mouse Product: Fedora Version: 39 OS: Linux Status: NEW Component: ibus Severity: medium Assignee: tfujiwar(a)redhat.com Reporter: tagoh(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 The cursor on the emoji categories dialog is changed through moving mouse cursor on it though, moving the cursor with keyboard doesn't follow it. Reproducible: Always Steps to Reproduce: 1.Press Super+period and space to show the categories dialog 2.move the cursor through mouse to somewhere else 3.press down-arrow key Actual Results: The cursor moves down where it initially pointed at. i.e. 2nd item at the list in this case. Expected Results: The cursor should moves down where the mouse cursor pointed at the list. e.g. if it points to 4th item after step 2, the cursor should move down to 5th item. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2237664 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 13

[Fedora-i18n-bugs] [Bug 1683395] New: emacs-common-ddskk-20150927 is available
by bugzilla＠redhat.com 08 Oct '25

08 Oct '25

https://bugzilla.redhat.com/show_bug.cgi?id=1683395 Bug ID: 1683395 Summary: emacs-common-ddskk-20150927 is available Product: Fedora Version: rawhide Status: NEW Component: emacs-common-ddskk Keywords: FutureFeature, Triaged Assignee: dueno(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 20150927 Current version/release in rawhide: 16.2-5.fc30 URL: http://openlab.ring.gr.jp/skk/maintrunk/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/679/ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 2135166] New: libunistring-1.1 is available
by bugzilla＠redhat.com 05 Oct '25

05 Oct '25

https://bugzilla.redhat.com/show_bug.cgi?id=2135166 Bug ID: 2135166 Summary: libunistring-1.1 is available Product: Fedora Version: rawhide Status: NEW Component: libunistring Keywords: FutureFeature, Triaged Assignee: p(a)draigbrady.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, jim(a)meyering.net, p(a)draigbrady.com, redhat-bugzilla(a)linuxnetz.de Target Milestone: --- Classification: Fedora Releases retrieved: 1.1 Upstream release that is considered latest: 1.1 Current version/release in rawhide: 1.0-2.fc37 URL: http://www.gnu.org/software/libunistring/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_M… Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/1747/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/libunistring -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2135166

1 15

[Bug 2062407] New: msgfmt cannot invoke javac
by bugzilla＠redhat.com 28 May '25

28 May '25

https://bugzilla.redhat.com/show_bug.cgi?id=2062407 Bug ID: 2062407 Summary: msgfmt cannot invoke javac Product: Fedora Version: rawhide Hardware: All OS: Linux Status: NEW Component: gettext Severity: low Assignee: suanand(a)redhat.com Reporter: loganjerry(a)gmail.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, petersen(a)redhat.com, praiskup(a)redhat.com, suanand(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: I noticed while building jmol that every invocation of msgfmt failed, e.g.: update-application-catalog-lang: [echo] msgfmt Updating messages_ar.class file for Jmol ... [exec] msgfmt: Java compiler not found, try installing gcj or set $JAVAC [exec] msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC [exec] 65 translated messages, 3 fuzzy translations, 380 untranslated messages. [exec] Result: 1 Setting JAVAC does *not* help. I used strace to see how javac is invoked and found the problem: msgfmt passes -target 1.6, and sometimes -source 1.6, to javac. Now that OpenJDK 17 is the default in Fedora, those arguments are no longer valid. I don't remember if the minimum allowed is 1.7 or 1.8, but it is one of the two. Since Fedora doesn't ship a JDK lower than 1.8, then 1.8 might as well be used. Version-Release number of selected component (if applicable): gettext-0.21-11.fc37.0.20220228 How reproducible: Always Steps to Reproduce: 1. fedpkg clone jmol 2. cd jmol 3. fedpkg srpm 4. mock -r fedora-rawhide-x86_64 --rebuild jmol-14.32.22-1.fc37.src.rpm Actual results: The msgfmt invocations all fail. Expected results: The msgfmt invocations should succeed. Additional info: -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2062407

1 13

[Bug 2090204] New: [abrt] ibus: __strndup(): ibus-extension-gtk3 killed by SIGSEGV
by bugzilla＠redhat.com 16 May '25

16 May '25

https://bugzilla.redhat.com/show_bug.cgi?id=2090204 Bug ID: 2090204 Summary: [abrt] ibus: __strndup(): ibus-extension-gtk3 killed by SIGSEGV Product: Fedora Version: 36 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:8c2b2d109d6c6600cfdf1e41632f3398d6d21e15;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: mfabian(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: Version-Release number of selected component: ibus-1.5.26-6.fc36 Additional info: reporter: libreport-2.17.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service cmdline: /usr/libexec/ibus-extension-gtk3 crash_function: __strndup dso_list: /usr/libexec/ibus-extension-gtk3 ibus-1.5.26-6.fc36.x86_64 (Fedora Project) 1653401127 executable: /usr/libexec/ibus-extension-gtk3 journald_cursor: s=3da4198b50ed40bb8e39aac19c44f062;i=15b44;b=4f87f45459b64f7299ca0a57d8a15df6;m=51ec68d6;t=5dfc2daddfca9;x=e27b7bc9d78e7740 kernel: 5.17.9-300.fc36.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2090204

1 8

[Bug 2209413] New: Prepare for DNF 5, don't depend on `dnf`
by bugzilla＠redhat.com 29 Apr '25

29 Apr '25

https://bugzilla.redhat.com/show_bug.cgi?id=2209413 Bug ID: 2209413 Summary: Prepare for DNF 5, don't depend on `dnf` Product: Fedora Version: rawhide Hardware: All OS: Linux Status: NEW Component: system-config-language Severity: high Assignee: pnemade(a)redhat.com Reporter: egoode(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com Target Milestone: --- Classification: Fedora (I'm filing issues with all the packages that currently depend on `dnf`.) DNF 5 is a new package manager that will replace DNF 4 in Fedora 39+: Starting in Fedora 39, the `dnf` command will be provided by the `dnf5` package rather than the `dnf` package, and `dnf5` will obsolete `dnf`. Since system-config-language currently depends on DNF 4, it should choose one of the following strategies to avoid breaking the Fedora upgrade: - Add support for DNF 5, and depend on the `dnf5` package in Fedora 39+ instead of `dnf`. Builds of DNF 5 are available in this COPR repository: https://copr.fedorainfracloud.org/coprs/rpmsoftwaremanagement/dnf-nightly/, and documentation is available here: https://dnf5.readthedocs.io/en/latest/. - Alternatively, or in the meantime, change the system-config-language package to depend on `python3-dnf` instead of `dnf`, and call the `dnf-3` binary instead of `dnf`. The old DNF 4 command will still be available in the distribution, but only as `dnf-3` (the binary is called `dnf-3` rather than `dnf4` for historical reasons; it is the "Python 3 version" of DNF). The first option is preferred to this one; it is not recommended to modify installed software using both DNF 4 and DNF 5 on the same system. - Or, if this package is no longer being maintained, consider removing it from Fedora. At some point, this project should adopt DNF 5, but the immediate issue is removing the dependency on `dnf`. We are planning to replace DNF with DNF5 in Fedora Rawhide very soon, by 2023-06-01, and the system-config-language package will break as long as it still depends on the `dnf` package. For more information about the switch to DNF 5, see https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2209413

1 14

[Bug 2241601] New: Fedora input broke the fr(oss) French layout (default Fedora French layout)
by bugzilla＠redhat.com 14 Apr '25

14 Apr '25

https://bugzilla.redhat.com/show_bug.cgi?id=2241601 Bug ID: 2241601 Summary: Fedora input broke the fr(oss) French layout (default Fedora French layout) Product: Fedora Version: rawhide OS: Linux Status: NEW Component: xkeyboard-config Severity: medium Assignee: peter.hutterer(a)redhat.com Reporter: nicolas.mailhot(a)laposte.net QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, negativo17(a)gmail.com, peter.hutterer(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com Target Milestone: --- Classification: Fedora fr(oss) is supposed to emit French upper case accented letters in caps locks mode ÉÈÇÀ Something changed in the past months and it emits lower case instead. So you get very annoying mixed-case éLéGANT runs of text in caps locks. Explicit level 4 capital selection still works but this change breaks existing user habits and is very inconvenient for new users. To be honest I’ve noticed the breakage for some time but was hoping it was a stupid mistake that would go away with time. Reproducible: Always Steps to Reproduce: 1. switch to fr(oss) 2. set cap locks 3. tap the first (number) row → letters with diacritics should be emitted in upper case, for example É, not lower case é It is not a bug that cap locks produces symbols and accented letters. In azerty, unlike qwerty, access to the diacritics necessary to type proper French is prioritized over access to numbers -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2241601 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 3

[Bug 2002446] New: zinnia-0.07 is available
by bugzilla＠redhat.com 12 Apr '25

12 Apr '25

https://bugzilla.redhat.com/show_bug.cgi?id=2002446 Bug ID: 2002446 Summary: zinnia-0.07 is available Product: Fedora Version: rawhide Status: NEW Component: zinnia Keywords: FutureFeature, Triaged Assignee: liangsuilong(a)gmail.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, liangsuilong(a)gmail.com, petersen(a)redhat.com, pwu(a)redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 0.07 Current version/release in rawhide: 0.06-55.fc35 URL: https://github.com/silverhikari/zinnia/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/5302/ -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1974076] New: Chinese input methods use previously enabled layout
by bugzilla＠redhat.com 27 Mar '25

27 Mar '25

https://bugzilla.redhat.com/show_bug.cgi?id=1974076 Bug ID: 1974076 Summary: Chinese input methods use previously enabled layout Product: Fedora Version: 34 Hardware: All OS: Linux Status: NEW Component: ibus-libpinyin Severity: medium Assignee: pwu(a)redhat.com Reporter: nickolay.ilyushin(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: ibus-libpinyin (and most probably several other input methods) uses `default` keyboard layout instead of `us` or whatever fits best. This effectively means that the last keyboard layout (non-IME) will be used for the pinyin input. For users which use non-Latin keyboard layouts, such as Russian or Ukrainian, this makes pinyin input unusable. Version-Release number of selected component (if applicable): 1.12.0 How reproducible: easily. Steps to Reproduce: 1. Enable pinyin input method in your settings. 2. Switch to e.g. Russian layout. 3. Switch to pinyin IME. 4. You will type Russian letters and pinyin IME will not trigger. Actual results: `4. You will type Russian letters and pinyin IME will not trigger.` Expected results: `4. You will type *Latin* letters and pinyin IME *will* trigger.` Additional info: There are two workarounds: 1. Manually patch `/usr/share/ibus/component/libpinyin.xml` and change `layout` to `us` from `default`. I don't know how this will work with non-QWERTY keyboards though. 2. Switch to a Latin layout before switching to pinyin. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 2237669] New: Key repeat doesn't work on Plasma Wayland
by bugzilla＠redhat.com 15 Jan '25

15 Jan '25

https://bugzilla.redhat.com/show_bug.cgi?id=2237669 Bug ID: 2237669 Summary: Key repeat doesn't work on Plasma Wayland Product: Fedora Version: 39 OS: Linux Status: NEW Component: ibus Severity: medium Assignee: tfujiwar(a)redhat.com Reporter: tagoh(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 After configuring IBus through Input Devices on systemsettings5, key repeat stopped working. Reproducible: Always Steps to Reproduce: 1.Change Virtual Keyboard from None to IBus Wayland 2.Open a app and press a key 3. Actual Results: Character corresponding to the key pressing appears only once on apps Expected Results: Character should be repeatedly added on apps -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2237669 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 4

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs October 2023