January 2023 - i18n-bugs - Fedora Mailing-Lists

[Bug 2062407] New: msgfmt cannot invoke javac

by bugzilla＠redhat.com

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

3 days, 23 hours

1
12
0 / 0

[Bug 2157582] New: Environment variables are no longer set in Wayland session after systemd subpackage was removed

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2157582 Bug ID: 2157582 Summary: Environment variables are no longer set in Wayland session after systemd subpackage was removed Product: Fedora Version: 37 Status: NEW Component: imsettings Assignee: tagoh(a)redhat.com Reporter: accounts+fedora(a)chiller3.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: After the removal of the imsettings-systemd subpackage, the IM-related environment variables (eg. QT_IM_MODULE) are no longer set in Wayland sessions (as least for KDE). I believe this is because none of the xinput scripts are read during Wayland session initialization and things previously relied on systemd's ~/.config/environment.d/. Version-Release number of selected component (if applicable): imsettings-1.8.3-6.fc37.x86_64 How reproducible: Always Steps to Reproduce: 1. Install Fedora 37 KDE spin 2. Log into Wayland session 3. Install an input method, like fcitx5 4. Select fcitx5 with im-chooser 5. Log out and log back in (still Wayland session) 6. $ echo $QT_IM_MODULE Actual results: Environment variables like QT_IM_MODULE are not set. Expected results: The IM-related environment variables should be set. (Manually setting them allows input methods to work properly in KDE Wayland.) Additional info: n/a -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2157582

5 days, 1 hour

1
23
0 / 0

[Bug 2135079] New: Please branch and build ibus-rime in epel8

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2135079 Bug ID: 2135079 Summary: Please branch and build ibus-rime in epel8 Product: Fedora Version: rawhide Status: NEW Component: ibus-rime Assignee: pwu(a)redhat.com Reporter: acyanbird(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 Please branch and build ibus-rime in epel8. I'm new here so I don't know if this is the right step. The repo can be found here https://github.com/rime/ibus-rime -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2135079

1 week, 4 days

1
11
0 / 0

[Bug 2156108] New: [abrt] ibus: XFree(): ibus-x11 killed by SIGABRT

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2156108 Bug ID: 2156108 Summary: [abrt] ibus: XFree(): ibus-x11 killed by SIGABRT Product: Fedora Version: rawhide Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:0385d31cccb3ffe2c784112a5c2060eeaac62698;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: mikhail.v.gavrilov(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 Version-Release number of selected component: ibus-1.5.27-8.fc38 Additional info: reporter: libreport-2.17.6 type: CCpp reason: ibus-x11 killed by SIGABRT journald_cursor: s=32500b5f39e6467e9ccddd56700852eb;i=43e8f3;b=f22e26d260164e228db6c4bc7b4ef7db;m=869ce7646;t=5f017821d96fc;x=29a8c76b08f7f956 executable: /usr/libexec/ibus-x11 cmdline: /usr/libexec/ibus-x11 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.SettingsDaemon.XSettings.service rootdir: / uid: 1000 kernel: 6.1.0-65.fc38.x86_64+debug package: ibus-1.5.27-8.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: XFree Truncated backtrace: Thread no. 1 (19 frames) #8 XFree at /usr/src/debug/libX11-1.8.1-2.fc38.x86_64/src/XlibInt.c:1633 #9 ProcessQueue at ../../util/IMdkit/i18nPtHdr.c:1762 #10 _Xi18nMessageHandler at ../../util/IMdkit/i18nPtHdr.c:1923 #11 WaitXIMProtocol at ../../util/IMdkit/i18nX.c:524 #12 _gdk_x11_display_queue_events at ../gdk/x11/gdkeventsource.c:337 #13 gdk_display_get_event at ../gdk/gdkdisplay.c:442 #14 gdk_event_source_dispatch.lto_priv at ../gdk/x11/gdkeventsource.c:354 #17 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4238 #18 g_main_context_iteration at ../glib/gmain.c:4303 #19 xim_forward_event.constprop.0 at /usr/src/debug/ibus-1.5.27-8.fc38.x86_64/client/x11/main.c:631 #20 ForwardEventMessageProc at ../../util/IMdkit/i18nPtHdr.c:1224 #21 ProcessQueue at ../../util/IMdkit/i18nPtHdr.c:1758 #22 _Xi18nMessageHandler at ../../util/IMdkit/i18nPtHdr.c:1923 #23 WaitXIMProtocol at ../../util/IMdkit/i18nX.c:524 #24 _gdk_x11_display_queue_events at ../gdk/x11/gdkeventsource.c:337 #25 gdk_display_get_event at ../gdk/gdkdisplay.c:442 #26 gdk_event_source_dispatch.lto_priv at ../gdk/x11/gdkeventsource.c:354 #29 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4238 #31 ibus_main at /usr/src/debug/ibus-1.5.27-8.fc38.x86_64/src/ibusshare.c:325 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2156108

1 week, 6 days

1
28
0 / 0

[Bug 2159567] New: cldr-emoji-annotation-43-m0 is available

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2159567 Bug ID: 2159567 Summary: cldr-emoji-annotation-43-m0 is available Product: Fedora Version: rawhide Status: NEW Component: cldr-emoji-annotation Keywords: FutureFeature, Triaged Assignee: tfujiwar(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 43-m0 Upstream release that is considered latest: 43-m0 Current version/release in rawhide: 42-1.fc38 URL: https://github.com/unicode-org/cldr 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... 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/103642/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/cldr-emoji-annotation -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2159567

3 weeks, 1 day

1
5
0 / 0

[Bug 2109358] New: emacs fails to start: Cannot open load file: No such file or directory, comp

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2109358 Bug ID: 2109358 Summary: emacs fails to start: Cannot open load file: No such file or directory, comp Product: Fedora Version: 36 Status: NEW Component: emacs-common-ddskk Assignee: dueno(a)redhat.com Reporter: nicku(a)nicku.org QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Description of problem: emacs fails to start if emacs-ddsdk is installed Version-Release number of selected component (if applicable): 16.2-12.fc36 How reproducible: Always Steps to Reproduce: 1.Install emacs, it runs 2.install emacs-ddsdk 3. Emacs refuses to start, with message, "Cannot open load file: No such file or directory, comp" Actual results: Emacs refuses to start, with message, "Cannot open load file: No such file or directory, comp" Expected results: emacs runs. Additional info: strace shows emacs looking iin so many places other than the right one. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2109358

4 weeks, 1 day

1
13
0 / 0

[Bug 2123720] New: Noto Sans Thai to default for Thai

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2123720 Bug ID: 2123720 Summary: Noto Sans Thai to default for Thai Product: Fedora Version: rawhide Status: NEW Component: google-noto-fonts Keywords: FutureFeature Assignee: tagoh(a)redhat.com Reporter: tagoh(a)redhat.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: As we have changed most languages default to Noto, it may be good to consider updating Thai to Noto as well. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2123720

1 month

1
4
0 / 0

[Bug 2123722] New: Noto Khmer to default for Khmer

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2123722 Bug ID: 2123722 Summary: Noto Khmer to default for Khmer Product: Fedora Version: rawhide Status: NEW Component: google-noto-fonts Keywords: FutureFeature Assignee: tagoh(a)redhat.com Reporter: tagoh(a)redhat.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: As we have changed most languages default to Noto, it may be good to consider updating Khmer to Noto as well. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2123722

1 month

1
3
0 / 0

[Bug 2113538] New: nafees-tehreer-naskh-fonts: FTBFS in Fedora rawhide/f37

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2113538 Bug ID: 2113538 Summary: nafees-tehreer-naskh-fonts: FTBFS in Fedora rawhide/f37 Product: Fedora Version: rawhide Status: NEW Component: nafees-tehreer-naskh-fonts Assignee: psatpute(a)redhat.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, psatpute(a)redhat.com Blocks: 2045102 (F37FTBFS,RAWHIDEFTBFS) Target Milestone: --- Classification: Fedora nafees-tehreer-naskh-fonts failed to build from source in Fedora rawhide/f37 https://koji.fedoraproject.org/koji/taskinfo?taskID=89834809 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild Please fix nafees-tehreer-naskh-fonts at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, nafees-tehreer-naskh-fonts will be orphaned. Before branching of Fedora 38, nafees-tehreer-naskh-fonts will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai... Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2045102 [Bug 2045102] Fedora 37 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2113538

1 month

1
6
0 / 0

[Bug 2113537] New: nafees-riqa-fonts: FTBFS in Fedora rawhide/f37

by bugzilla＠redhat.com

https://bugzilla.redhat.com/show_bug.cgi?id=2113537 Bug ID: 2113537 Summary: nafees-riqa-fonts: FTBFS in Fedora rawhide/f37 Product: Fedora Version: rawhide Status: NEW Component: nafees-riqa-fonts Assignee: psatpute(a)redhat.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, psatpute(a)redhat.com Blocks: 2045102 (F37FTBFS,RAWHIDEFTBFS) Target Milestone: --- Classification: Fedora nafees-riqa-fonts failed to build from source in Fedora rawhide/f37 https://koji.fedoraproject.org/koji/taskinfo?taskID=89834806 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild Please fix nafees-riqa-fonts at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, nafees-riqa-fonts will be orphaned. Before branching of Fedora 38, nafees-riqa-fonts will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai... Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2045102 [Bug 2045102] Fedora 37 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2113537

1 month

1
5
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs January 2023