April 2026 - i18n-bugs - Fedora mailing-lists

[Bug 2435442] New: Question: Can fcitx5 branch and build to EPEL?
by bugzilla＠redhat.com 17 Jul '26

17 Jul '26

https://bugzilla.redhat.com/show_bug.cgi?id=2435442 Bug ID: 2435442 Summary: Question: Can fcitx5 branch and build to EPEL? Product: Fedora EPEL Version: epel10 Hardware: x86_64 OS: Linux Status: NEW Component: fcitx Assignee: yanqiyu01(a)gmail.com Reporter: gerenlzn(a)hotmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, i(a)cicku.me, liangsuilong(a)gmail.com, pwu(a)redhat.com, robinlee.sysu(a)gmail.com, yanqiyu01(a)gmail.com Target Milestone: --- Classification: Fedora Distro:Alma Linux 10.1 Because I am a KDE user and I have many XWayland software. iBus XWayland and non-GNOME experience is suck. So I wanna use fcitx5 on EPEL. Plz branch and build fcitx5 series package to EPEL :( Thx. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2435442 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 6

[Bug 2461123] New: translate-toolkit-3.19.6 is available
by bugzilla＠redhat.com 15 Jul '26

15 Jul '26

https://bugzilla.redhat.com/show_bug.cgi?id=2461123 Bug ID: 2461123 Summary: translate-toolkit-3.19.6 is available Product: Fedora Version: rawhide Status: NEW Component: translate-toolkit Keywords: FutureFeature, Triaged Assignee: sshil(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com, petersen(a)redhat.com, sshil(a)redhat.com, sundeep_anand(a)yahoo.com Target Milestone: --- Classification: Fedora Releases retrieved: 3.19.6 Upstream release that is considered latest: 3.19.6 Current version/release in rawhide: 3.19.5-1.fc45 URL: http://toolkit.translatehouse.org/ 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/3685/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/translate-toolkit -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2461123 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 29

[Fedora-i18n-bugs] [Bug 1919932] New: Culmus Hebrew fonts aren't usable by TeXLive after installation
by bugzilla＠redhat.com 01 Jul '26

01 Jul '26

https://bugzilla.redhat.com/show_bug.cgi?id=1919932 Bug ID: 1919932 Summary: Culmus Hebrew fonts aren't usable by TeXLive after installation Product: Fedora Version: 33 Status: NEW Component: culmus-fonts Assignee: petersen(a)redhat.com Reporter: nikita(a)leshenko.net QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, petersen(a)redhat.com, pnemade(a)redhat.com, psatpute(a)redhat.com, vishalvijayraghavan(a)gmail.com Target Milestone: --- Classification: Fedora Created attachment 1750496 --> https://bugzilla.redhat.com/attachment.cgi?id=1750496&action=edit Basic Hebrew document Description of problem: On a clean Fedora 33 after installing texlive, babel-hebrew, and tex-fonts-hebrew, I can't use pdflatex to render a Hebrew document. Detailed steps to reproduce and a possible fix are provided below. Version-Release number of selected component (if applicable): texlive 9:2020-34.fc33 texlive-babel-hebrew 9:svn30273.2.3h-34.fc33 tex-fonts-hebrew 0.1-33.fc33 How reproducible: Always Steps to Reproduce: 1. Start a new Fedora 33 container: podman run -it fedora:33 2. dnf install texlive texlive-babel-hebrew tex-fonts-hebrew 3. Try to render hello.tex document attached to this bug report (this is a basic Hebrew document). \documentclass{article} \usepackage[utf8x]{inputenc} \usepackage[english,hebrew]{babel} \begin{document} שלום! \end{document} Actual results: We get the following error message: !pdfTeX error: pdflatex (file rdavid): Font rdavid at 600 not found ==> Fatal error occurred, no output PDF file produced! Full log is at first.log. Expected results: Document is rendered :) Additional info: We need two steps to resolve the problem here. I'm not sure if these steps are the idiomatic way to fix the issue, but it worked for me... The first issue that that culmus.map is not included in the pdflatex.map, even though culmus.map is enabled in /etc/texlive/web2c/updmap.cfg. I was able to solve it with - updmap-sys --syncwithtrees - updmap-sys to recreate the map file. It would be nice the Culmus will do this by default as part of the installation. (Another temporary per-document solution is to add \pdfmapfile{culmus.map} to the Hebrew document.) Now if we re-run pdflatex we get a new error: !pdfTeX error: pdflatex (file DavidCLM-Medium.pfa): cannot open Type 1 font file for reading ==> Fatal error occurred, no output PDF file produced! The full log is in second.log. There are multiple ways around this problem: 1. Note that /usr/share/texmf/fonts/type1/public/ has a broken symlink to culmus. Even if we fix the symlink to point to /usr/share/fonts/culmus/, it doesn't work because pdflatex doesn't seem to follow directory symlinks. But if we actually create a directory and symlink fonts individually, it will work, like this: mkdir /usr/share/texmf/fonts/type1/public/culmus2 for i in /usr/share/fonts/culmus/*; do ln $i /usr/share/texmf/fonts/type1/public/culmus2/${i##*/}; done 2. A more "general" fix is to edit /etc/texlive/web2c/texmf.cnf instead and set OSFONTDIR to /usr/share/fonts/, but it seems like this change extends beyond Culmus so I'm not sure how practical is it to edit OSFONTDIR as part of installation. After building the map file and teaching latex to find Type1 Culmus fonts the Hebrew document can compile successfully. I hope that it will be possible to adjust the Culmus package so that Hebrew latex works out of the box. Thanks! I'm available for questions and clarifications. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 2249005] New: mozc-2.29.5268.102 is available
by bugzilla＠redhat.com 27 Jun '26

27 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2249005 Bug ID: 2249005 Summary: mozc-2.29.5268.102 is available Product: Fedora Version: rawhide Status: NEW Component: mozc Keywords: FutureFeature, Triaged Assignee: tagoh(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 2.29.5268.102 Upstream release that is considered latest: 2.29.5268.102 Current version/release in rawhide: 2.29.5111.102-3.fc40 URL: http://code.google.com/p/mozc 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/2016/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/mozc -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2249005 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 26

[Bug 2437062] New: Please consider building for epel10
by bugzilla＠redhat.com 24 Jun '26

24 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2437062 Bug ID: 2437062 Summary: Please consider building for epel10 Product: Fedora Version: rawhide Status: NEW Component: cldr-emoji-annotation Assignee: tfujiwar(a)redhat.com Reporter: yanqiyu01(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora I am trying to build fcitx5 on epel 10, and found this dependency is missing from the repo. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2437062 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 5

[Bug 2400564] New: xkeyboard-config-2.46 is available
by bugzilla＠redhat.com 20 Jun '26

20 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2400564 Bug ID: 2400564 Summary: xkeyboard-config-2.46 is available Product: Fedora Version: rawhide Status: NEW Component: xkeyboard-config Keywords: FutureFeature, Triaged Assignee: peter.hutterer(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org 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, rstrode(a)redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 2.46 Upstream release that is considered latest: 2.46 Current version/release in rawhide: 2.45-1.fc43 URL: https://www.freedesktop.org/wiki/Software/XKeyboardConfig/ 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/5191/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/xkeyboard-config -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2400564 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 8

[Bug 2444787] New: [abrt] ibus-panel: g_utf8_pointer_to_offset(): ibus-ui-gtk3 killed by SIGSEGV
by bugzilla＠redhat.com 19 Jun '26

19 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2444787 Bug ID: 2444787 Summary: [abrt] ibus-panel: g_utf8_pointer_to_offset(): ibus-ui-gtk3 killed by SIGSEGV Product: Fedora Version: 43 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:4c9239b94f10bfb4d9d83e6c4d0a4cb93d3cc6bf;VAR IANT_ID=kde; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: mmakowski985(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: i do not know what caused this problem but one thing i can say is that i was switching keyboard layout from russian translit to polish Version-Release number of selected component: ibus-panel-1.5.33-5.fc43 Additional info: reporter: libreport-2.17.15 type: CCpp reason: ibus-ui-gtk3 killed by SIGSEGV journald_cursor: s=6f5faf66e4c44139b8cc0749a0d86681;i=545a36;b=c6e2780fc3344068a0f3d8390d025efa;m=540bc83e;t=64c42b85f0548;x=4bb4b35b46bb8916 executable: /usr/libexec/ibus-ui-gtk3 cmdline: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args $'--xim --panel disable' cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service rootdir: / uid: 1000 kernel: 6.18.13-200.fc43.x86_64 package: ibus-panel-1.5.33-5.fc43 runlevel: /bin/sh: line 1: runlevel: command not found xsession_errors: comment: i do not know what caused this problem but one thing i can say is that i was switching keyboard layout from russian translit to polish backtrace_rating: 4 crash_function: g_utf8_pointer_to_offset Truncated backtrace: Thread no. 1 (17 frames) #0 g_utf8_pointer_to_offset at ../glib/gutf8.c:426 #1 handle_surrounding_text at ../../client/wayland/ibuswaylandim.c:726 #2 ffi_call_unix64 at ../src/x86/unix64.S:104 #3 ffi_call_int at ../src/x86/ffi64.c:676 #4 ffi_call at ../src/x86/ffi64.c:713 #5 wl_closure_invoke at ../src/connection.c:1241 #6 dispatch_event at ../src/wayland-client.c:1707 #7 dispatch_queue at ../src/wayland-client.c:1853 #8 wl_display_dispatch_queue_pending at ../src/wayland-client.c:2190 #9 wl_display_dispatch_pending at ../src/wayland-client.c:2253 #10 _gdk_wayland_display_queue_events at ../gdk/wayland/gdkeventsource.c:201 #11 gdk_display_get_event at ../gdk/gdkdisplay.c:442 #14 g_main_context_dispatch_unlocked at ../glib/gmain.c:4425 #15 g_main_context_iterate_unlocked at ../glib/gmain.c:4490 #17 gtk_main at ../gtk/gtkmain.c:1332 #18 application_run at /usr/src/debug/ibus-1.5.33-5.fc43.x86_64/ui/gtk3/application.vala:90 #19 application_main at /usr/src/debug/ibus-1.5.33-5.fc43.x86_64/ui/gtk3/application.vala:406 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2444787 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 9

[Bug 2402600] New: google-roboto-fonts-3.013 is available
by bugzilla＠redhat.com 17 Jun '26

17 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2402600 Bug ID: 2402600 Summary: google-roboto-fonts-3.013 is available Product: Fedora Version: rawhide Status: NEW Component: google-roboto-fonts Keywords: FutureFeature, Triaged Assignee: dtardon(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: davide(a)cavalca.name, dtardon(a)redhat.com, epel-packagers-sig(a)lists.fedoraproject.org, fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 3.000, 3.001, 3.002, 3.003, 3.004, 3.005, 3.006, 3.007, 3.008, 3.009, 3.010, 3.011, 3.012, 3.013 Upstream release that is considered latest: 3.013 Current version/release in rawhide: 2.138-20.fc43 URL: https://github.com/googlefonts/roboto-3-classic 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/12041/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/google-roboto-fonts -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2402600 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 12

[Bug 2131516] New: Sinhala letters shake, wobble and momentarily disappear and reappear when typing, sometimes with wrong cursor positions.
by bugzilla＠redhat.com 14 Jun '26

14 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2131516 Bug ID: 2131516 Summary: Sinhala letters shake, wobble and momentarily disappear and reappear when typing, sometimes with wrong cursor positions. Product: Fedora Version: 37 Status: NEW Component: ibus-m17n Assignee: pnemade(a)redhat.com Reporter: lohang(a)riseup.net QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com, pnemade(a)redhat.com, shawn.p.huang(a)gmail.com Target Milestone: --- Classification: Fedora Created attachment 1915511 --> https://bugzilla.redhat.com/attachment.cgi?id=1915511&action=edit Issue reproduced with gedit on GNOME + Wayland. Description of problem: When typing Sinhala text with ibus, the characters shake and wobble, making writing experience uncomfortable. Letters sometimes disappear for a moment and reappear. Two cursor positions or wrong cursor positions seem to appear during the process. The latter is somewhat similar to the issue described here https://gitlab.gnome.org/GNOME/pango/-/issues/684 Version-Release number of selected component (if applicable): How reproducible: Reproducible throughout the system. Environment : Fedora 37 beta, GNOME on Wayland. Applications : Gedit, Firefox, LibreOffice. Steps to Reproduce: 1. Enable Sinhala input with si-wijesekera 2. Type : isxy, NdIdfjka ,sjSfua oS wlqrq Tn fudn mksk whqrq ksrSlaIKh lrkak' (සිංහල භාෂාවෙන් ලිවීමේ දී අකුරු ඔබ මොබ පනින අයුරු නිරීක්ෂණය කරන්න.) 3. Typing any meaningful chunk of text can actually demonstrate the issue. Actual results: See attachments Expected results: Smooth typing without shaking, wobbling and disappearing/reappearing of characters. The issue is already there to a lesser extent on Fedora 36 too. So I am unable to show you a video of the ideal expected result at the moment. 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=2131516

1 26

[Bug 2402531] New: fedora is using obselete version of Roboto font
by bugzilla＠redhat.com 12 Jun '26

12 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2402531 Bug ID: 2402531 Summary: fedora is using obselete version of Roboto font Product: Fedora Version: 42 Status: NEW Component: google-roboto-fonts Assignee: dtardon(a)redhat.com Reporter: uneasy_latitude544(a)simplelogin.com QA Contact: extras-qa(a)fedoraproject.org CC: davide(a)cavalca.name, dtardon(a)redhat.com, epel-packagers-sig(a)lists.fedoraproject.org, fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org Target Milestone: --- Classification: Fedora Description of problem: fedora is using old version of Roboto font, see readme in https://github.com/googlefonts/roboto-2?tab=readme-ov-file, more updated version https://github.com/googlefonts/roboto-3-classic v3.012 Version-Release number of selected component (if applicable): v2.138 How reproducible: Yes. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2402531 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 4

[Bug 2395836] New: don't combine pinyin Chinese IME and bopomofo Chinese IME into one single package
by bugzilla＠redhat.com 10 Jun '26

10 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2395836 Bug ID: 2395836 Summary: don't combine pinyin Chinese IME and bopomofo Chinese IME into one single package Product: Fedora Version: 42 Hardware: x86_64 OS: Linux Status: NEW Component: ibus-libpinyin Keywords: Desktop, RFE Severity: medium Assignee: pwu(a)redhat.com Reporter: lutingrong(a)hotmail.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 Hello the authors of ibus-libpinyin , I'm using ibus-libpinyin on fedora 42 . I found ibus-libpinyin provides both pinyin Chinese IME and bopomofo Chinese IME . Could you please consider split ibus-libpinyin into ibus-libpinyin and ibus-libbopomofo ? The reason is that those who use pinyin IME doesn't know bopomofo IME at all , and vice verse those who use bopomofo IME doesn't know pinyin IME neither . So I can install only the package which I use . Why must combine pinyin IME and bopomofo IME into one single package ? Most hope there is no unnecessary codes in their computers . Hope ibus-libpinyin more modularized and more divided ! Thanks for your time and consideration! Best regards, Tingrong Reproducible: Always Steps to Reproduce: 1. sudo dnf install ibus-libpinyin 2. ibus-setup 3. will see there are both pinyin Chinese IME and bopomofo Chinese IME Actual Results: one single package -- ibus-libpinyin provides more than one IME . Expected Results: one package provides only one IME . -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2395836 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 6

[Bug 2389161] New: [abrt] ibus: XFilterEvent(): ibus-x11 killed by SIGSEGV
by bugzilla＠redhat.com 08 Jun '26

08 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2389161 Bug ID: 2389161 Summary: [abrt] ibus: XFilterEvent(): ibus-x11 killed by SIGSEGV Product: Fedora Version: 42 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:a66be73ad13c8fcab90850e60a97bac8edd45ff3;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: patrick(a)laimbock.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-1.5.32-1.fc42 Additional info: reporter: libreport-2.17.15 runlevel: N 5 crash_function: XFilterEvent type: CCpp reason: ibus-x11 killed by SIGSEGV journald_cursor: s=89812708b80a4f43b4479d23aa64b1b7;i=af096;b=1ba500cede60472eaaa1a4f5b02f7f8d;m=2067a5f289;t=63c8fb12a7934;x=fadf305ea5641571 executable: /usr/libexec/ibus-x11 uid: 1001 package: ibus-1.5.32-1.fc42 backtrace_rating: 4 cmdline: /usr/libexec/ibus-x11 cgroup: 0::/user.slice/user-1001.slice/user@1001.service/session.slice/org.gnome.SettingsDaemon.XSettings.service kernel: 6.15.9-201.fc42.x86_64 rootdir: / Truncated backtrace: Thread no. 1 (7 frames) #0 XFilterEvent at /usr/src/debug/libX11-1.8.12-1.fc42.x86_64/src/FilterEv.c:93 #1 _gdk_x11_display_queue_events at ../gdk/x11/gdkeventsource.c:337 #2 gdk_display_get_event at ../gdk/gdkdisplay.c:442 #3 gdk_event_source_dispatch.lto_priv at ../gdk/x11/gdkeventsource.c:354 #5 g_main_context_dispatch_unlocked at ../glib/gmain.c:4249 #6 g_main_context_iterate_unlocked at ../glib/gmain.c:4314 #8 ibus_main at /usr/src/debug/ibus-1.5.32-1.fc42.x86_64/src/ibusshare.c:336 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2389161 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 3

[Bug 2372839] New: cinnamon-screensaver segfault with uim-1.9.6.
by bugzilla＠redhat.com 08 Jun '26

08 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2372839 Bug ID: 2372839 Summary: cinnamon-screensaver segfault with uim-1.9.6. Product: Fedora Version: 42 OS: Linux Status: NEW Component: uim Keywords: Desktop, Upgrades Severity: medium Assignee: tagoh(a)redhat.com Reporter: ta1yanagiya+rh(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Cinnamon-screensaver does not work after updating to uim-1.9.6. The following logs are output to journal: ``` systemd[2183]: Started dbus-:1.2-org.cinnamon.ScreenSaver@3.service. cinnamon-screensaver[5935]: CsNotificationWatcher: Could not add match rule to bus - GDBus.Error:org.freedesktop.DBus.Error.MatchRuleInvalid: Invalid match rule cinnamon-screensaver[5935]: Loading AccountsService cinnamon-screensaver[5935]: Fractional scaling active: False cinnamon-screensaver[5935]: Trying to connect to logind... cinnamon-screensaver[5935]: Starting screensaver... cinnamon-screensaver[5935]: Cinnamon Screensaver support not found in current theme - adding some... audit[5935]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=3 pid=5935 comm="cinnamon-screen" exe="/usr/bin/python3.13" sig=11 res=1 kernel: cinnamon-screen[5935]: segfault at a6e ip 00007f27627571dd sp 00007ffdedc4a278 error 4 in libc.so.6[1491dd,7f276260e000+16f000] likely on CPU 5 (core 2, socket 0) kernel: Code: 00 00 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 00 <c5> fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66 kernel: audit: type=1701 audit(1749905665.970:333): auid=1001 uid=1001 gid=1001 ses=3 pid=5935 comm="cinnamon-screen" exe="/usr/bin/python3.13" sig=11 res=1 (snip) ``` Reproducible: Always Steps to Reproduce: 1. Log in to cinnamon session. (The following versions) uim-1.9.6-1.fc42.x86_64 uim-anthy-1.9.6-1.fc42.x86_64 uim-gtk3-1.9.6-1.fc42.x86_64 cinnamon-6.4.9-1.fc42.x86_64 cinnamon-screensaver-6.4.0-2.fc42.x86_64 2. Press Alt-Ctl-L. Actual Results: The screensaver does not work. Expected Results: The screensaver works. Additional Information: Cinnamon-screensaver works when downgrades to uim-1.8.9. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2372839 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 4

[Bug 2364700] New: [abrt] ibus: __strcmp_evex(): ibus-x11 killed by SIGSEGV
by bugzilla＠redhat.com 08 Jun '26

08 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2364700 Bug ID: 2364700 Summary: [abrt] ibus: __strcmp_evex(): ibus-x11 killed by SIGSEGV Product: Fedora Version: 42 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:184db64f4234731aa826b676bd01b8507c23e6da;VAR IANT_ID=compneuro; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: sanjay.ankur(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-1.5.32-1.fc42 Additional info: reporter: libreport-2.17.15 type: CCpp reason: ibus-x11 killed by SIGSEGV journald_cursor: s=facd15e04f384ea0b6e611e9078e70c2;i=92231f2d;b=34ca2973d2434e6f973add5fae86b10f;m=75f14af9;t=6347a7e580b45;x=3b76384ca1e0b033 executable: /usr/libexec/ibus-x11 cmdline: /usr/libexec/ibus-x11 --kill-daemon cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service rootdir: / uid: 1000 kernel: 6.14.5-300.fc42.x86_64 package: ibus-1.5.32-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: __strcmp_evex Truncated backtrace: Thread no. 1 (18 frames) #0 __strcmp_evex at ../sysdeps/x86_64/multiarch/strcmp-evex.S:316 #1 g_str_equal at ../glib/ghash.c:2444 #2 g_hash_table_lookup_node at ../glib/ghash.c:442 #3 g_hash_table_lookup at ../glib/ghash.c:1488 #4 g_dbus_proxy_get_cached_property at ../gio/gdbusproxy.c:712 #5 ibus_input_context_post_process_key_event at /usr/src/debug/ibus-1.5.32-1.fc42.x86_64/src/ibusinputcontext.c:1534 #6 _process_key_event_sync at /usr/src/debug/ibus-1.5.32-1.fc42.x86_64/client/x11/main.c:638 #7 xim_forward_event at /usr/src/debug/ibus-1.5.32-1.fc42.x86_64/client/x11/main.c:765 #8 ims_protocol_handler at /usr/src/debug/ibus-1.5.32-1.fc42.x86_64/client/x11/main.c:1020 #9 ForwardEventMessageProc at ../../util/IMdkit/i18nPtHdr.c:1224 #10 _Xi18nMessageHandler at ../../util/IMdkit/i18nPtHdr.c:1898 #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 #16 g_main_context_dispatch_unlocked at ../glib/gmain.c:4249 #17 g_main_context_iterate_unlocked at ../glib/gmain.c:4314 #19 ibus_main at /usr/src/debug/ibus-1.5.32-1.fc42.x86_64/src/ibusshare.c:336 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2364700 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 3

[Bug 2362429] New: [abrt] ibus: g_hash_table_remove_all_nodes(): ibus-x11 killed by SIGABRT
by bugzilla＠redhat.com 08 Jun '26

08 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2362429 Bug ID: 2362429 Summary: [abrt] ibus: g_hash_table_remove_all_nodes(): ibus-x11 killed by SIGABRT Product: Fedora Version: 42 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:6ef4db86fa264ddee0fbb467ca28f667a1602325;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: wangxuke.china(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: input chinese in Intellij IDEA Version-Release number of selected component: ibus-1.5.32-1.fc42 Additional info: reporter: libreport-2.17.15 type: CCpp reason: ibus-x11 killed by SIGABRT journald_cursor: s=3c0dd3d416e941f6a30daef456f5e069;i=314c71;b=df414e19ee6c4d1f94962765166ef677;m=fd1cc199;t=633a404f8f053;x=14c6bfd5955da7ef executable: /usr/libexec/ibus-x11 cmdline: /usr/libexec/ibus-x11 --kill-daemon cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service rootdir: / uid: 1000 kernel: 6.14.3-300.fc42.x86_64 package: ibus-1.5.32-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: g_hash_table_remove_all_nodes comment: input chinese in Intellij IDEA Truncated backtrace: Thread no. 1 (12 frames) #10 g_hash_table_remove_all_nodes at ../glib/ghash.c:656 #12 g_hash_table_unref at ../glib/ghash.c:1438 #14 g_dbus_message_finalize at ../gio/gdbusmessage.c:521 #16 message_to_write_data_free at ../gio/gdbusprivate.c:902 #17 write_message_cb at ../gio/gdbusprivate.c:1370 #18 g_task_return_now at ../gio/gtask.c:1363 #19 complete_in_idle_cb at ../gio/gtask.c:1377 #22 g_main_context_dispatch_unlocked at ../glib/gmain.c:4249 #23 g_main_context_iterate_unlocked at ../glib/gmain.c:4314 #25 gdbus_shared_thread_func at ../gio/gdbusprivate.c:284 #26 g_thread_proxy at ../glib/gthread.c:893 #28 __clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2362429 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 3

[Bug 2362341] New: [abrt] ibus: signal_data_free(): ibus-x11 killed by SIGABRT
by bugzilla＠redhat.com 08 Jun '26

08 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2362341 Bug ID: 2362341 Summary: [abrt] ibus: signal_data_free(): ibus-x11 killed by SIGABRT Product: Fedora Version: 42 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:7936830f237804278aac65806e5ac2a42481d11b;VAR IANT_ID=; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: iweiss(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-1.5.32-1.fc42 Additional info: reporter: libreport-2.17.15 type: CCpp reason: ibus-x11 killed by SIGABRT journald_cursor: s=ad8df5fbe10e4eff88921a95a3c2f30d;i=f30f6f;b=1bc60ca687884a3d997ae6706b477154;m=13d0a25551;t=6339cf9411412;x=c677f35ec1eb8625 executable: /usr/libexec/ibus-x11 cmdline: /usr/libexec/ibus-x11 --kill-daemon cgroup: 0::/user.slice/user-1001.slice/session-2.scope rootdir: / uid: 1001 kernel: 6.14.2-300.fc42.x86_64 package: ibus-1.5.32-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: signal_data_free Truncated backtrace: Thread no. 1 (18 frames) #10 signal_data_free at ../gio/gdbusconnection.c:428 #11 remove_signal_data_if_unused at ../gio/gdbusconnection.c:4068 #12 unsubscribe_id_internal.isra.0 at ../gio/gdbusconnection.c:4106 #13 g_dbus_connection_signal_unsubscribe at ../gio/gdbusconnection.c:4147 #15 g_dbus_proxy_finalize at ../glib/gmain.h:920 #17 _free_ic at /usr/src/debug/ibus-1.5.32-1.fc42.x86_64/client/x11/main.c:814 #18 g_list_foreach at ../glib/glist.c:1008 #19 g_list_free_full at ../glib/glist.c:162 #20 _free_x11_iconn_from_id at /usr/src/debug/ibus-1.5.32-1.fc42.x86_64/client/x11/main.c:837 #21 CloseMessageProc at ../../util/IMdkit/i18nPtHdr.c:302 #22 _Xi18nMessageHandler at ../../util/IMdkit/i18nPtHdr.c:1821 #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 #28 g_main_context_dispatch_unlocked at ../glib/gmain.c:4249 #29 g_main_context_iterate_unlocked at ../glib/gmain.c:4314 #31 ibus_main at /usr/src/debug/ibus-1.5.32-1.fc42.x86_64/src/ibusshare.c:336 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2362341 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 6

[Bug 2361916] New: [abrt] imsettings: g_malloc0_n(): imsettings-daemon killed by SIGTRAP
by bugzilla＠redhat.com 08 Jun '26

08 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2361916 Bug ID: 2361916 Summary: [abrt] imsettings: g_malloc0_n(): imsettings-daemon killed by SIGTRAP Product: Fedora Version: 42 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:8b8d4cb79153aa86bf5c71a5a74b459e4bd8183c;VAR IANT_ID=cosmic; Component: imsettings Assignee: tagoh(a)redhat.com Reporter: varunrajvj79(a)gmail.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: Version-Release number of selected component: imsettings-1.8.10-2.fc42 Additional info: reporter: libreport-2.17.15 type: CCpp reason: imsettings-daemon killed by SIGTRAP journald_cursor: s=c6bd9352fa734f5297f51e606d1a9e71;i=3915;b=faf40bff69234be1b4df0f4eee99aafe;m=83e92f0;t=6334cdc4f1aef;x=59f4f4a7cc2b347f executable: /usr/libexec/imsettings-daemon cmdline: /usr/libexec/imsettings-daemon cgroup: 0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-dbus\x2d:1.2\x2dcom.redhat.imsettings.slice/dbus-:1.2-com.redhat.imsettings@0.service rootdir: / uid: 1000 kernel: 6.14.2-300.fc42.x86_64 package: imsettings-1.8.10-2.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: g_malloc0_n comment: Truncated backtrace: Thread no. 1 (9 frames) #3 g_malloc0_n at ../glib/gmem.c:433 #4 _start_process at /usr/src/debug/imsettings-1.8.10-2.fc42.x86_64/imsettings-daemon/imsettings-proc.c:351 #5 _start_main_process at /usr/src/debug/imsettings-1.8.10-2.fc42.x86_64/imsettings-daemon/imsettings-proc.c:272 #6 imsettings_proc_spawn at /usr/src/debug/imsettings-1.8.10-2.fc42.x86_64/imsettings-daemon/imsettings-proc.c:716 #7 imsettings_server_cb_switch_im at /usr/src/debug/imsettings-1.8.10-2.fc42.x86_64/imsettings-daemon/imsettings-server.c:921 #8 imsettings_server_bus_method_call at /usr/src/debug/imsettings-1.8.10-2.fc42.x86_64/imsettings-daemon/imsettings-server.c:1277 #9 call_in_idle_cb at ../gio/gdbusconnection.c:5476 #12 g_main_context_dispatch_unlocked at ../glib/gmain.c:4249 #13 g_main_context_iterate_unlocked at ../glib/gmain.c:4314 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2361916 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 4

[Bug 2323789] New: The word "Favorites" appears as a candidate in emojier when pressed!
by bugzilla＠redhat.com 08 Jun '26

08 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2323789 Bug ID: 2323789 Summary: The word "Favorites" appears as a candidate in emojier when pressed! Product: Fedora Version: 41 OS: Linux Status: NEW Component: ibus Keywords: Regression Severity: medium Assignee: tfujiwar(a)redhat.com Reporter: petersen(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Manish and I discovered this bug in emojier last week while testing. Reproducible: Always Steps to Reproduce: 0. Open gnome-text-editor 1. Start emojier by pressing Super+Period Space 2. Click on Favorites category Actual Results: The word "Favorites" is listed as an emoji candidate in the grid! Expected Results: "Favorites" should not be listed as a favorite emoji. Does not seem to happen in current F40. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2323789 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 5

[Bug 2277345] New: NotoSansMono[wght].ttf file name causes scripts with failglob enabled to fail
by bugzilla＠redhat.com 08 Jun '26

08 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2277345 Bug ID: 2277345 Summary: NotoSansMono[wght].ttf file name causes scripts with failglob enabled to fail Product: Fedora Version: 40 Hardware: All OS: Linux Status: NEW Component: google-noto-fonts Severity: medium Assignee: tagoh(a)redhat.com Reporter: hartsjc(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, pwu(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora shopt failglob If set, patterns which fail to match filenames during pathname expansion result in an expansion error. Using this feature is good practice in scripts as helps prevent scripting mistakes; however, having file name with square brackets causes failures. And with Fedora 40 upgrade seems google-noto-sans-mono-vf-fonts-20240301-2.fc40.noarch has added one with: /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf Reproducible: Always Steps to Reproduce: 1. Causes globs that don't expand to cause errors $ shopt -s failglob 2. Try use files from rpm as variable, and fail $ for file in $(rpm -q --list google-noto-sans-mono-vf-fonts) ; do [[ -f "/${file}" ]] || echo "${file}" done -bash: no match: /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf 3. Note the RC $ echo $? 1 4. Or even command line $ rpm -qf /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf -bash: no match: /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf $ rpm -qf '/usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf' google-noto-sans-mono-vf-fonts-20240301-2.fc40.noarch Actual Results: -bash: no match: /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf Expected Results: no error accessing files with failglob shopt enabled started fedora 40 upgrade, as daily script of mine fails because this file is included in initramfs too. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2277345 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 8

[Bug 2368622] New: ibus-daemon uses insane amounts of CPU and causes a laggy experience
by bugzilla＠redhat.com 03 Jun '26

03 Jun '26

https://bugzilla.redhat.com/show_bug.cgi?id=2368622 Bug ID: 2368622 Summary: ibus-daemon uses insane amounts of CPU and causes a laggy experience Product: Fedora Version: 42 Hardware: x86_64 OS: Linux Status: NEW Component: ibus Keywords: Desktop Severity: high Assignee: tfujiwar(a)redhat.com Reporter: torvalds(a)linux-foundation.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Not a lot of details here, but I decided that instead of just fixing it with killall ibus-daemon which gets rid of that broken thing, I would at least open a bug report to see if there is some official fix for this. Google shows a lot of people complaining about this going back years, so it's not me. There's no crash, and no obvious system logs either. All I see in system logs is gdm-wayland-session activating, and when I kill it systemd seems to log consumtion information like org.freedesktop.IBus.session.GNOME.service: Consumed 26min 22.196s CPU time, 125.1M memory peak. (That was after the system had been up for one day, so 26 min of CPU time seems pretty excessive) Reproducible: Sometimes Steps to Reproduce: 1. Boot the system 2. Be happy 3. Some time randomly later, notice laggy behavior and ibus-daemon using 100% CPU in top Actual Results: Slow keyboard response on a fast system Expected Results: Snappy action Additional Information: Sorry for the horrible bug report, but can we please just disable ibus-daemon by default as a useless problem-causing thing? When google shows this problem going back AT LEAST to 2020 (and probably longer), with the solution invariably being "kill, restart or disable ibus-daemon to fix the problem temporarily", why is that thing enabled by default in the first place? Please at least give a good setting for this, so that the answer can be for people to not enable that thing. And if somebody has "please debug this next time it happens by doing Xyz", I'll happily do that. But you need to tell me what Xyz is, because I don't know the first thing about ibus-daemon. I know that the "i" is supposed to stand for "intelligent". But honestly, I can come up with a lot better suggestions for what that "i" might stand for. And absolutely *none* of them are polite. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2368622 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 21

[Bug 2397329] New: ibus-typing-booster: Please build in Fedora 43
by bugzilla＠redhat.com 25 May '26

25 May '26

https://bugzilla.redhat.com/show_bug.cgi?id=2397329 Bug ID: 2397329 Summary: ibus-typing-booster: Please build in Fedora 43 Product: Fedora Version: 43 Status: NEW Component: ibus-typing-booster Assignee: mfabian(a)redhat.com Reporter: ksurma(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com Blocks: 2373702 (PYC3.14rc3) Target Milestone: --- Classification: Fedora Dear package maintainer, Due to reasons described in https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… a rebuild of ibus-typing-booster was needed in Fedora 43 and 44. During the mass rebuild we built the package for Fedora 44, but the automation determined that there was an existing build for Fedora 43, which was not tagged to the main repository. We didn't want to interfere with the plans you may have with the package, so we ask you to rebuild the package for Fedora 43 once again, when it's convenient to you. Thank you. Let me know if you need help. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2373702 [Bug 2373702] Rebuild all packages with .pyc files with Python 3.14.0rc3+ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2397329 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 4

[Bug 2437635] New: [abrt] ibus-panel: pango_attr_list_change(): ibus-ui-gtk3 killed by SIGSEGV
by bugzilla＠redhat.com 21 May '26

21 May '26

https://bugzilla.redhat.com/show_bug.cgi?id=2437635 Bug ID: 2437635 Summary: [abrt] ibus-panel: pango_attr_list_change(): ibus-ui-gtk3 killed by SIGSEGV Product: Fedora Version: 43 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:23ad854bfc28f5ca1cb06e5514ab5d3a2b77bb67;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, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Version-Release number of selected component: ibus-panel-1.5.33-5.fc43 Additional info: reporter: libreport-2.17.15 comment: executable: /usr/libexec/ibus-ui-gtk3 crash_function: pango_attr_list_change package: ibus-panel-1.5.33-5.fc43 kernel: 6.18.9-200.fc43.x86_64 cgroup: 0::/user.slice/user-10030.slice/session-2.scope uid: 10030 type: CCpp reason: ibus-ui-gtk3 killed by SIGSEGV backtrace_rating: 4 runlevel: /bin/sh: line 1: runlevel: command not found journald_cursor: s=b9e570c33ff64b4aad9ccf855c4d0992;i=e6c89708;b=4b3ee2756ae447b08137e8614dfe100c;m=b85100b;t=64a5395f2f95d;x=61686746ceadbdeb rootdir: / cmdline: /usr/libexec/ibus-ui-gtk3 Truncated backtrace: Thread no. 1 (4 frames) #0 pango_attr_list_change at ../pango/pango-attributes.c:2077 #1 candidate_panel_set_auxiliary_text_real at /usr/src/debug/ibus-1.5.33-5.fc43.x86_64/ui/gtk3/candidatepanel.vala:270 #2 candidate_panel_set_auxiliary_text at /usr/src/debug/ibus-1.5.33-5.fc43.x86_64/ui/gtk3/candidatepanel.vala:247 #3 panel_real_update_auxiliary_text at /usr/src/debug/ibus-1.5.33-5.fc43.x86_64/ui/gtk3/panel.vala:2001 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2437635 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 1

[Bug 2375440] New: [abrt] ibus-panel: _bus_global_engine_changed_cb(): ibus-ui-gtk3 killed by SIGABRT
by bugzilla＠redhat.com 21 May '26

21 May '26

https://bugzilla.redhat.com/show_bug.cgi?id=2375440 Bug ID: 2375440 Summary: [abrt] ibus-panel: _bus_global_engine_changed_cb(): ibus-ui-gtk3 killed by SIGABRT Product: Fedora Version: 42 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:331776bb8c03402b51dbeedcf3d69ad7db095042;VAR IANT_ID=kde; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: xfox(a)linuxuser.site QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-panel-1.5.32-1.fc42 Additional info: reporter: libreport-2.17.15 crash_function: _bus_global_engine_changed_cb cmdline: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args $'--xim --panel disable' cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service journald_cursor: s=eba8c06984c246a68797330ee0fc5fc7;i=1ef6d;b=242bd8c7c62e4f8ba7bcc4b7cc7acb96;m=a7a3f75;t=638b97d0f4638;x=b8590b204d3135c4 type: CCpp reason: ibus-ui-gtk3 killed by SIGABRT executable: /usr/libexec/ibus-ui-gtk3 runlevel: N 5 package: ibus-panel-1.5.32-1.fc42 backtrace_rating: 4 uid: 1000 kernel: 6.15.3-200.fc42.x86_64 rootdir: / Truncated backtrace: Thread no. 1 (9 frames) #6 _bus_global_engine_changed_cb at ../../client/wayland/ibuswaylandim.c:920 #9 signal_emit_valist_unlocked at ../gobject/gsignal.c:3534 #12 _connection_ibus_signal_cb at /usr/src/debug/ibus-1.5.32-1.fc42.x86_64/src/ibusbus.c:309 #13 emit_signal_instance_in_idle_cb at ../gio/gdbusconnection.c:4207 #16 g_main_context_dispatch_unlocked at ../glib/gmain.c:4249 #17 g_main_context_iterate_unlocked at ../glib/gmain.c:4314 #19 gtk_main at ../gtk/gtkmain.c:1329 #20 application_run at /usr/src/debug/ibus-1.5.32-1.fc42.x86_64/ui/gtk3/application.vala:89 #21 application_main at /usr/src/debug/ibus-1.5.32-1.fc42.x86_64/ui/gtk3/application.vala:379 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2375440 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 4

[Bug 2262532] New: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT
by bugzilla＠redhat.com 21 May '26

21 May '26

https://bugzilla.redhat.com/show_bug.cgi?id=2262532 Bug ID: 2262532 Summary: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT Product: Fedora Version: 39 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:b24defc317ee932c47b15b9c24c231f607dad274;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: flomaker84(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.29~rc2-6.fc39 Additional info: reporter: libreport-2.17.11 journald_cursor: s=12fe9cd95439407dac30bd572f9b8b0a;i=3c751d;b=8468a63c7e3f4d71bee1954f018d928a;m=265979b;t=60f8bf17f39bc;x=f99ebdd856eb797d cmdline: ibus-daemon --panel disable -r --xim reason: ibus-daemon killed by SIGABRT uid: 42 executable: /usr/bin/ibus-daemon kernel: 6.6.11-200.fc39.x86_64 crash_function: bus_dbus_impl_connection_filter_cb package: ibus-1.5.29~rc2-6.fc39 type: CCpp rootdir: / backtrace_rating: 4 runlevel: N 5 cgroup: 0::/user.slice/user-42.slice/session-c1.scope Truncated backtrace: Thread no. 1 (10 frames) #6 bus_dbus_impl_connection_filter_cb at /usr/src/debug/ibus-1.5.29 #7 on_worker_message_about_to_be_sent at ../gio/gdbusconnection.c:2384 #9 _g_dbus_worker_emit_message_about_to_be_sent at ../gio/gdbusprivate.c:501 #10 continue_writing at ../gio/gdbusprivate.c:1514 #11 continue_writing_in_idle_cb at ../gio/gdbusprivate.c:1575 #14 g_main_context_dispatch_unlocked at ../glib/gmain.c:4284 #15 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4349 #17 gdbus_shared_thread_func at ../gio/gdbusprivate.c:284 #18 g_thread_proxy at ../glib/gthread.c:831 #20 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Potential duplicate: bug 906086 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2262532 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 8

[Bug 2440813] New: [abrt] ibus: ibus_bus_connect_async(): ibus-x11 killed by SIGSEGV
by bugzilla＠redhat.com 21 May '26

21 May '26

https://bugzilla.redhat.com/show_bug.cgi?id=2440813 Bug ID: 2440813 Summary: [abrt] ibus: ibus_bus_connect_async(): ibus-x11 killed by SIGSEGV Product: Fedora Version: 43 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:e9e25725fbf5b802310f7153823734fd779117b2;VAR IANT_ID=; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: henrytro2022(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-1.5.33-5.fc43 Additional info: reporter: libreport-2.17.15 type: CCpp reason: ibus-x11 killed by SIGSEGV journald_cursor: s=827d5a919b3d42cc9c7c245e1b677390;i=17167;b=1fd848e4a9434d10b0c075ee51324ad3;m=37966ad;t=64b1db7b905aa;x=41a918f55f6473eb executable: /usr/libexec/ibus-x11 cmdline: /usr/libexec/ibus-x11 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service rootdir: / uid: 1000 kernel: 6.18.10-200.fc43.x86_64 package: ibus-1.5.33-5.fc43 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: ibus_bus_connect_async Truncated backtrace: Thread no. 1 (8 frames) #0 ibus_bus_connect_async at /usr/src/debug/ibus-1.5.33-5.fc43.x86_64/src/ibusbus.c:506 #1 _g_cclosure_marshal_VOID__OBJECT_OBJECT_ENUMv at ../gio/gmarshal-internal.c:1382 #2 _g_closure_invoke_va at ../gobject/gclosure.c:980 #3 signal_emit_valist_unlocked at ../gobject/gsignal.c:3439 #6 g_file_monitor_source_dispatch at ../gio/glocalfilemonitor.c:582 #8 g_main_context_dispatch_unlocked at ../glib/gmain.c:4425 #9 g_main_context_iterate_unlocked at ../glib/gmain.c:4490 #11 ibus_main at /usr/src/debug/ibus-1.5.33-5.fc43.x86_64/src/ibusshare.c:336 Potential duplicate: bug 1926996 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2440813 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 2

[Bug 2459650] New: [abrt] ibus: g_type_check_instance_is_fundamentally_a(): ibus-x11 killed by SIGSEGV
by bugzilla＠redhat.com 21 May '26

21 May '26

https://bugzilla.redhat.com/show_bug.cgi?id=2459650 Bug ID: 2459650 Summary: [abrt] ibus: g_type_check_instance_is_fundamentally_a(): ibus-x11 killed by SIGSEGV Product: Fedora Version: 43 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:d5b9a38a7fc38ceaf4c7f723514a21714c6429b2;VAR IANT_ID=kde; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: prumsadofaikr(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-1.5.33-5.fc43 Additional info: reporter: libreport-2.17.15 type: CCpp reason: ibus-x11 killed by SIGSEGV journald_cursor: s=92553229c6fb44a98e44d783155a86da;i=3413b;b=6d02051cb8a2448995a67a43c7f1a26b;m=c7a560c;t=64fdf8b665dba;x=5a20067653313333 executable: /usr/libexec/ibus-x11 cmdline: /usr/libexec/ibus-x11 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service rootdir: / uid: 1000 kernel: 7.0.0 package: ibus-1.5.33-5.fc43 runlevel: /bin/sh: 줄 1: runlevel: 명령을 찾을 수 없음 backtrace_rating: 4 crash_function: g_type_check_instance_is_fundamentally_a Truncated backtrace: Thread no. 1 (7 frames) #0 g_type_check_instance_is_fundamentally_a at ../gobject/gtype.c:3917 #1 g_object_ref at ../gobject/gobject.c:4656 #2 g_task_new at ../gio/gtask.c:830 #3 g_async_initable_real_init_async at ../gio/gasyncinitable.c:281 #4 g_async_initable_new_valist_async at ../gio/gasyncinitable.c:438 #5 g_async_initable_new_async at ../gio/gasyncinitable.c:347 #6 g_dbus_connection_new_for_address at ../gio/gdbusconnection.c:3255 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2459650 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 1

[Bug 2450200] New: pango-1.57.1 is available
by bugzilla＠redhat.com 16 May '26

16 May '26

https://bugzilla.redhat.com/show_bug.cgi?id=2450200 Bug ID: 2450200 Summary: pango-1.57.1 is available Product: Fedora Version: rawhide Status: NEW Component: pango Keywords: FutureFeature, Triaged Assignee: pwu(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: fonts-bugs(a)lists.fedoraproject.org, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com, pwu(a)redhat.com, rhughes(a)redhat.com, rstrode(a)redhat.com, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 1.57.1 Upstream release that is considered latest: 1.57.1 Current version/release in rawhide: 1.57.0-4.fc45 URL: http://www.pango.org 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/11783/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/pango -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2450200 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 5

[Bug 2461799] New: CVE-2026-41680 cldr-emoji-annotation: Marked: Denial of Service via specific input sequence [fedora-all]
by bugzilla＠redhat.com 13 May '26

13 May '26

https://bugzilla.redhat.com/show_bug.cgi?id=2461799 Bug ID: 2461799 Summary: CVE-2026-41680 cldr-emoji-annotation: Marked: Denial of Service via specific input sequence [fedora-all] Product: Fedora Version: rawhide Status: NEW Whiteboard: {"flaws": ["9f765a72-8087-4527-9ce5-de5649b8c5e2"]} Component: cldr-emoji-annotation Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: tfujiwar(a)redhat.com Reporter: vinair(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Blocks: 2461603 Target Milestone: --- Classification: Fedora Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2461799 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 3

[Bug 2422135] New: [abrt] ibus-typing-booster: Py_Exit(): python3.13 killed by SIGABRT
by bugzilla＠redhat.com 11 May '26

11 May '26

https://bugzilla.redhat.com/show_bug.cgi?id=2422135 Bug ID: 2422135 Summary: [abrt] ibus-typing-booster: Py_Exit(): python3.13 killed by SIGABRT Product: Fedora Version: 42 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:1016fbf3f898a8e267bb35897e7a7417c6d30f73;VAR IANT_ID=workstation; Component: ibus-typing-booster Assignee: mfabian(a)redhat.com Reporter: htl10(a)users.sourceforge.net QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: ibus-typing-booster seems to often crash on gnome-shell logging out, and crashes gnome-shell on the way too. Version-Release number of selected component: ibus-typing-booster-2.28.6-1.fc42 Additional info: reporter: libreport-2.17.15 executable: /usr/bin/python3.13 rootdir: / kernel: 6.16.8-200.fc42.x86_64 journald_cursor: s=d85d4e6a420649199e9c9ed3c18b1efe;i=92a38d;b=d547d11eb0634f1fa7e01d689bbad122;m=50aa753cbc;t=645f2872f7a59;x=86672d859f327ae2 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service runlevel: N 5 uid: 1000 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py --ibus type: CCpp reason: python3.13 killed by SIGABRT package: ibus-typing-booster-2.28.6-1.fc42 comment: ibus-typing-booster seems to often crash on gnome-shell logging out, and crashes gnome-shell on the way too. crash_function: Py_Exit Truncated backtrace: Thread no. 1 (4 frames) #5 Py_Exit at /usr/src/debug/python3.13-3.13.9-1.fc42.x86_64/Python/pylifecycle.c:3523 #6 handle_system_exit at /usr/src/debug/python3.13-3.13.9-1.fc42.x86_64/Python/pythonrun.c:679 #7 _PyErr_PrintEx at /usr/src/debug/python3.13-3.13.9-1.fc42.x86_64/Python/pythonrun.c:688 #8 PyErr_PrintEx at /usr/src/debug/python3.13-3.13.9-1.fc42.x86_64/Python/pythonrun.c:768 Potential duplicate: bug 2185830 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2422135 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 2

[Bug 2389767] New: The brise package is deprecated upstream since 2018 and providing outdated data files for ibus-rime, fcitx5-rime etc
by bugzilla＠redhat.com 06 May '26

06 May '26

https://bugzilla.redhat.com/show_bug.cgi?id=2389767 Bug ID: 2389767 Summary: The brise package is deprecated upstream since 2018 and providing outdated data files for ibus-rime, fcitx5-rime etc Product: Fedora Version: 42 OS: Linux Status: NEW Component: brise Keywords: Desktop, RFE Severity: medium Assignee: pwu(a)redhat.com Reporter: alt.euyis(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 Per the readme file in the upstream repo (https://github.com/rime/brise/blob/master/README.md) brise is deprecated and the last release version of 0.38 dating back to 2018 is still being served as a dependency package for Rime front-ends in Fedora (ibus-rime, fcitx5-rime, etc). As the schema files in the package are essentially what actually provide the user-facing input features of Rime, the fact that they are several years outdated when newer, current version are available with updates & bug fixes are readily available is clearly not ideal. In fact, this bug report is prompted by me running into an upstream bug (https://github.com/rime/home/issues/831) that was fixed all the way back to 2021 yet still present Fedora 42, due to the schema files being stuck in 2018. Would it be possible to either update the files provided by the brise package to the latest versions available, or move them to a new dependency package for Rime front-end packages, since a update version would clearly not be specifically brise anymore so the name would be misleading in that case? 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=2389767 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 5

[Bug 2319795] New: Please branch and build translate-toolkit for EPEL 10
by bugzilla＠redhat.com 06 May '26

06 May '26

https://bugzilla.redhat.com/show_bug.cgi?id=2319795 Bug ID: 2319795 Summary: Please branch and build translate-toolkit for EPEL 10 Product: Fedora Version: rawhide Status: NEW Component: translate-toolkit Assignee: petersen(a)redhat.com Reporter: xavier(a)bachelot.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com, petersen(a)redhat.com, sshil(a)redhat.com, sundeep_anand(a)yahoo.com Blocks: 2303880 (EPEL10Tracker) Target Milestone: --- Classification: Fedora Hi, Could you please branch and build translate-toolkit for EPEL 10 ? It is needed to build another package. Regards, Xavier Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2303880 [Bug 2303880] EPEL 10 Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2319795 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 5

[Bug 2260744] New: Fedora build does not enable cloud input
by bugzilla＠redhat.com 06 May '26

06 May '26

https://bugzilla.redhat.com/show_bug.cgi?id=2260744 Bug ID: 2260744 Summary: Fedora build does not enable cloud input Product: Fedora Version: 39 OS: Linux Status: NEW Component: ibus-libpinyin Keywords: Desktop, EasyFix, RFE Severity: low Assignee: pwu(a)redhat.com Reporter: jiechushou(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 ibus-libpinyin upstream supports cloud input function, which can greatly improve user experience Cloud input support can be enabled by adding the --enable-cloud-input-mode flag to the build configuration. This cloud input option is optional and turned off by default. It does not violate Fedora Packaging Guidelines 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=2260744 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 3

[Bug 2262410] New: Fonts are looking wrong after 20240101 update
by bugzilla＠redhat.com 05 May '26

05 May '26

https://bugzilla.redhat.com/show_bug.cgi?id=2262410 Bug ID: 2262410 Summary: Fonts are looking wrong after 20240101 update Product: Fedora Version: 39 Hardware: x86_64 OS: Linux Status: NEW Component: google-noto-fonts Severity: medium Assignee: tagoh(a)redhat.com Reporter: priv.luk(a)gmail.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, tagoh(a)redhat.com Target Milestone: --- Classification: Fedora Fonts look improperly in multiple places, e.g. mpv or KDE file picker. Reproducible: Always Steps to Reproduce: 1. Open mpv and look at OSD fonts Actual Results: Fonts look wrong Expected Results: Fonts look properly See https://github.com/mpv-player/mpv/issues/13396 for screenshots. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2262410 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 46

[Bug 2456590] New: m17n-db-1.8.11 is available
by bugzilla＠redhat.com 04 May '26

04 May '26

https://bugzilla.redhat.com/show_bug.cgi?id=2456590 Bug ID: 2456590 Summary: m17n-db-1.8.11 is available Product: Fedora Version: rawhide Status: NEW Component: m17n-db Keywords: FutureFeature, Triaged Assignee: mfabian(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com, petersen(a)redhat.com, pnemade(a)redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 1.8.11 Upstream release that is considered latest: 1.8.11 Current version/release in rawhide: 1.8.10-3.fc44 URL: http://download.savannah.gnu.org/releases/m17n/ 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/1869/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/m17n-db -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2456590 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 3

[Bug 2463420] New: [abrt] ibus-anthy-python: __update_anthy_convert_chars(): engine.py:1307:__update_anthy_convert_chars:TypeError: can only concatenate str (not "NoneType") to str
by bugzilla＠redhat.com 28 Apr '26

28 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2463420 Bug ID: 2463420 Summary: [abrt] ibus-anthy-python: __update_anthy_convert_chars(): engine.py:1307:__update_anthy_convert_chars:TypeError: can only concatenate str (not "NoneType") to str Product: Fedora Version: 41 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:38d86fa2efcd3270714c641b1b13ba7b15cb5e69;VAR IANT_ID=workstation; Component: ibus-anthy Assignee: tfujiwar(a)redhat.com Reporter: ksuzumur(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2463420 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 0

[Bug 2457897] New: CVE-2026-34478 cldr-emoji-annotation: Apache Log4j Core: Log injection via CRLF sequences due to configuration attribute renames [fedora-all]
by bugzilla＠redhat.com 28 Apr '26

28 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2457897 Bug ID: 2457897 Summary: CVE-2026-34478 cldr-emoji-annotation: Apache Log4j Core: Log injection via CRLF sequences due to configuration attribute renames [fedora-all] Product: Fedora Version: rawhide Status: NEW Whiteboard: {"flaws": ["3b3e57ac-d7bc-486b-86c6-b7be7077654f"]} Component: cldr-emoji-annotation Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: tfujiwar(a)redhat.com Reporter: jmoroney(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Blocks: 2457323 Target Milestone: --- Classification: Fedora Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2457897 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 2

[Bug 1326470] glibc `locale -a` output does not exactly match between locale-archive and langpacks.
by bugzilla＠redhat.com 27 Apr '26

27 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=1326470 Pravin Satpute <psatpute(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(psatpute(a)redhat.c | |om) | --- Comment #18 from Pravin Satpute <psatpute(a)redhat.com> --- Hi, I do not remember it. Let me ping Jens Petersen, he might able to assign someone to this issue. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1326470 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 0

[Bug 2129399] Postscript standard symbol font is not looked up correctly
by bugzilla＠redhat.com 27 Apr '26

27 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2129399 Akira TAGOH <tagoh(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|42 |rawhide Keywords| |FutureFeature --- Comment #37 from Akira TAGOH <tagoh(a)redhat.com> --- Any suggestions for Symbol substitute are welcome. I mark this as FutureFeature so far. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2129399 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 0

[Bug 2444009] Keyboard layout latch accents broken after update
by bugzilla＠redhat.com 26 Apr '26

26 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2444009 --- Comment #21 from Askolds <askolds11+rh(a)gmail.com> --- Sorry for the delay. > I'd ask you to describe your issue with detail. After some experimentation, if I restart ibus with "Use system keyboard layout" disabled, mismatched layouts (lv for ibus, us for kde) work, but when restarting with "Use system keyboard layout" enabled, they do not work. After reading your second explanation, this seems to be limited by the KDE issue, so it's fine. > I assume you switch the layouts of the IBus keymaps with Super-space key, I.e. configuring multiple keymaps with ibus-setup -> "Input Method" seciton. I switch with the icon in the toolbar, but as I found out the switching part is unrelated, it was all from "Use system keyboard layout". -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2444009 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 0

[Bug 2442573] New: ibus-engine-typing-booster --xml can trigger display/gtk/dbus
by bugzilla＠redhat.com 24 Apr '26

24 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2442573 Bug ID: 2442573 Summary: ibus-engine-typing-booster --xml can trigger display/gtk/dbus Product: Fedora Version: 44 Hardware: All OS: Linux Status: NEW Whiteboard: AcceptedFreezeException Component: ibus-typing-booster Keywords: AutomationTriaged Severity: high Assignee: mfabian(a)redhat.com Reporter: petersen(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adscvr(a)gmail.com, alpha(a)bookwar.info, anaconda-maint(a)bot.bugzilla.redhat.com, awilliam(a)redhat.com, bugzilla(a)colorremedies.com, extras-qa(a)fedoraproject.org, fmuellner(a)redhat.com, gnome-sig(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, jadahl(a)redhat.com, johan.o.hedin(a)gmail.com, kkoukiou(a)redhat.com, kparal(a)redhat.com, mclasen(a)redhat.com, mfabian(a)redhat.com, mkolman(a)redhat.com, ngompa13(a)gmail.com, otaylor(a)redhat.com, petersen(a)redhat.com, philip.wyett(a)kathenas.org, robatino(a)fedoraproject.org, tfujiwar(a)redhat.com, w(a)wizard.zone Depends On: 2439813 Blocks: 2362357 (BetaBlocker,F44BetaBlocker), 2362358 (BetaFreezeException,F44BetaFreezeException) Target Milestone: --- Classification: Fedora +++ This bug was initially created as a clone of Bug #2439813 +++ On both Fedora 44 (branched) and Rawhide currently, if you try to do a network install of KDE, the install process hangs during package scriptlets; it seems to get stuck during %triggerin of the ibus package. The GUI shows "Configuring gtk3.x86_64", but /tmp/dnf5.log shows the gtk3 scriptlet completed with return code 0, then shows 'start' for the ibus %triggerin , but that's the last entry - there's no 'stop' line for ibus. So it seems like we're stuck on ibus. This has been happening on Fedora 44 since Fedora-44-20260206.n.3, but it only started happening on Rawhide with Fedora-Rawhide-20260210.n.0; the test uses default repos, so it was actually probably installing the package set from the previous compose, Fedora-Rawhide-20260209.n.0 , so that's most likely where the problem appeared in Rawhide. Though I can't see any obviously-related packages in the changelog. Just installing @core plus ibus (via a kickstart) doesn't reproduce the problem, so some other packages have to be involved somehow. I'll look into this more next week if nobody else can get to it. --- Additional comment from Adam Williamson on 2026-02-24 00:17:37 +08 --- --- Additional comment from Adam Williamson on 2026-02-24 00:34:13 +08 --- In the dupe, kparal guessed we might actually be in the `dconf update || :` call in %posttrans, which is possible I guess. (It should be fairly easy to check with ps, so I'll take a look in a minute). He also proposed it as a blocker: "Proposing for F44 blocker discussion. KDE is a release blocking environment, and Everything netinst is a release blocking deliverable." I'm not sure that holds up, but we can talk about it in the meeting. --- Additional comment from Adam Williamson on 2026-02-24 01:20:33 +08 --- Nope, that's not it. I've just reproduced this and looked at the ps list, and I see `/bin/sh /var/tmp/rpm-tmp.G1eBN2 1`. /mnt/sysimage/var/tmp/rpm-tmp.G1eBN2 says: [ -x /usr/bin/ibus ] && \ /usr/bin/ibus write-cache --system &>/dev/null || : so that's what we're stuck on. I do indeed see an `ibus write-cache --system` process, and a `/usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py --xml`, and `dbus-launch --autolaunch=(randomstrng) --binary-syntax --close-stderr`. --- Additional comment from Kamil Páral on 2026-02-24 01:31:49 +08 --- Discussed during blocker review meeting on 2025-02-23 [1]: agreed 2439813 - punt (delay decision) - there's substantial sentiment that this ought to be blocking, but the current criteria don't clearly allow for that. whether the criteria should be adjusted to make this a blocker is a somewhat complex question we don't want to try and resolve live during a meeting, so we'll punt this to allow for more calm consideration of that [1] https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-… --- Additional comment from Kamil Páral on 2026-02-24 01:45:04 +08 --- (In reply to Kamil Páral from comment #4) > Discussed during blocker review meeting on 2025-02-23 [1]: I almost got the year correct. 2026-02-23. --- Additional comment from Adam Williamson on 2026-02-24 03:09:23 +08 --- Hmm. If I chroot into /mnt/sysimage and run `/usr/bin/ibus write-cache --system`, it runs and returns quite quickly, it doesn't get stuck. Not sure why the scriptlet invocation gets stuck. --- Additional comment from Adam Williamson on 2026-02-24 03:58:50 +08 --- I'm running an install with an ibus build patched to drop the `&>/dev/null` from the ibus write-cache call, so we get the messages from it. It looks like it prints: INFO [scriptlet] (ibus write-cache:29935): IBUS-WARNING **: 19:50:24.268: Engines exec:/usr/libexec/ibus-engine-table --xml is failed: INFO [scriptlet] INFO [scriptlet] (ibus write-cache:29935): IBUS-WARNING **: 19:50:24.373: Engines exec:/usr/libexec/ibus-engine-anthy --xml is failed: literally that - the messages look like there should be some more text indicating the reason, but there isn't. If I run the command manually in chroot /mnt/sysimage , I get the same two messages first, but then I also get: Engines exec:/usr/libexec/ibus-engine-typing-booster --xml is failed: Engines exec:/usr/libexec/ibus-engine-libpinyin --xml is failed: Engines exec:/usr/libexec/ibus-engine-m17n --xml is failed: and a couple other things. That ties in with the apparently-stuck `/usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py --xml` process, obviously (the next message we're expecting from ibus write-cache is the "Engines exec:/usr/libexec/ibus-engine-typing-booster --xml is failed:" one). Still don't know why the scriptlet call gets stuck while a manual one works, though. --- Additional comment from Adam Williamson on 2026-02-24 05:36:01 +08 --- OK, took a bit of fiddling but I managed to backtrace the dbus-launch process which seems to be at the bottom of the stuck processes pile, here's the trace: #0 __internal_syscall_cancel (a1=a1@entry=140722696347344, a2=a2@entry=1, a3=a3@entry=-1, a4=a4@entry=0, a5=a5@entry=0, a6=a6@entry=0, nr=7) at cancellation.c:44 result = -516 pd = <optimized out> ch = <optimized out> #1 0x00007f6340e5e234 in __syscall_cancel (a1=a1@entry=140722696347344, a2=a2@entry=1, a3=a3@entry=-1, a4=a4@entry=0, a5=a5@entry=0, a6=a6@entry=0, nr=7) at cancellation.c:75 r = <optimized out> #2 0x00007f6340ed843e in __GI___poll (fds=fds@entry=0x7ffc8e53ded0, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 No locals. #3 0x00007f6340c8dbb0 in poll (__fds=0x7ffc8e53ded0, __nfds=1, __timeout=-1) at /usr/include/bits/poll2.h:44 No locals. #4 read_block (fd=3, buf=0x558600568ab0, len=8) at /usr/src/debug/libxcb-1.17.0-7.fc44.x86_64/src/xcb_in.c:394 pfd = {fd = 3, events = 1, revents = 0} ret = <optimized out> done = 0 #5 _xcb_in_read_block (c=c@entry=0x5586005637d0, buf=0x558600568ab0, len=len@entry=8) at /usr/src/debug/libxcb-1.17.0-7.fc44.x86_64/src/xcb_in.c:1087 ret = <optimized out> done = 0 #6 0x00007f6340c9173e in read_setup (c=0x5586005637d0) at /usr/src/debug/libxcb-1.17.0-7.fc44.x86_64/src/xcb_conn.c:180 newline = 10 '\n' #7 xcb_connect_to_fd (fd=fd@entry=3, auth_info=<optimized out>) at /usr/src/debug/libxcb-1.17.0-7.fc44.x86_64/src/xcb_conn.c:386 c = 0x5586005637d0 #8 0x00007f6340c919cf in xcb_connect_to_display_with_auth_info (displayname=displayname@entry=0x0, auth=auth@entry=0x0, screenp=screenp@entry=0x0) at /usr/src/debug/libxcb-1.17.0-7.fc44.x86_64/src/xcb_util.c:568 fd = <optimized out> display = 1 host = 0x5586005620f0 "" protocol = 0x0 ourauth = {namelen = 0, name = 0x7f63411b6f31 <_dl_map_object_deps+1057> "H\203\275x\373\377\377", datalen = 1, data = 0x7f6340c8a530 ""} c = <optimized out> parsed = <optimized out> #9 0x00007f6340c9225e in xcb_connect (displayname=displayname@entry=0x0, screenp=screenp@entry=0x0) at /usr/src/debug/libxcb-1.17.0-7.fc44.x86_64/src/xcb_util.c:522 No locals. #10 0x00007f6341016f6a in _XConnectXCB (dpy=0x558600562410, display=0x0, screenp=0x7ffc8e53e26c) at /usr/src/debug/libX11-1.8.12-3.fc44.x86_64/src/xcb_disp.c:78 host = 0x5586005620f0 "" n = 1 c = <optimized out> #11 0x00007f634100ea9d in XOpenDisplay (display=display@entry=0x0) at /usr/src/debug/libX11-1.8.12-3.fc44.x86_64/src/OpenDis.c:129 dpy = 0x558600562410 i = <optimized out> j = <optimized out> k = <optimized out> display_name = 0x5586005620d0 ":1" setup = 0x0 iscreen = 0 prefix = <optimized out> vendorlen = <optimized out> u = <optimized out> setuplength = <optimized out> usedbytes = 0 mask = <optimized out> conn_buf_size = <optimized out> xlib_buffer_size = <optimized out> #12 0x00005585c27ce1a3 in open_x11 () at ../tools/dbus-launch-x11.c:229 No locals. #13 x11_init () at ../tools/dbus-launch-x11.c:472 ok = <optimized out> #14 0x00005585c27cbf12 in main (argc=4, argv=0x7ffc8e53ea18) at ../tools/dbus-launch.c:1060 prev_arg = 0x7ffc8e540aed "--close-stderr" shname = <optimized out> runprog = <optimized out> remaining_args = <optimized out> exit_with_session = <optimized out> exit_with_x11 = 1 binary_syntax = <optimized out> c_shell_syntax = 0 bourne_shell_syntax = 0 auto_shell_syntax = <optimized out> autolaunch = 1 requires_arg = <optimized out> close_stderr = <optimized out> i = <optimized out> ret = <optimized out> bus_pid_to_launcher_pipe = {1089986000, 32611} bus_pid_to_babysitter_pipe = {-1907104524, 32764} bus_address_to_launcher_pipe = {-1907104520, 32764} config_file = 0x0 existing_bus_supported = 0 existing_bus = {dummy1 = 0x0, dummy2 = 0, dummy3 = 0, dummy_bit1 = 0, dummy_bit2 = 0, dummy_bit3 = 0, dummy_bits = 0} error_str = 0x0 error = {name = 0x0, message = 0x0, dummy1 = 1, dummy2 = 0, dummy3 = 0, dummy4 = 0, dummy5 = 0, padding1 = 0x0} so we're in X init stuff, here...theory: because the installer is running in a graphical environment we get into this codepath and get stuck, but when I do chroot /mnt/sysimage and run the command from a tty on vt3, we're *not* a graphical environment so we don't hit this codepath and everything's fine? --- Additional comment from Adam Williamson on 2026-02-24 06:52:25 +08 --- Another interesting finding: despite the fact that this happens during the install process in a scriptlet run in the installed system root, the bug depends on the *installer environment*. If I use the 20260209.n.0 netinst image, the bug doesn't happen, no matter whether I use the 20260209.n.0, 20260210.n.0 or today's compose as the repository. If I use the 20260210.n.0 netinst, or today's netinst, the bug always happens, even if I use the 20260209.n.0 compose as the install repo. So, something changed in the installer environment between 0209.n.0 and 0210.n.0 that triggers this, somehow. The changelog is at https://lists.fedoraproject.org/archives/list/test-reports@lists.fedoraproj… . --- Additional comment from Adam Williamson on 2026-02-24 08:28:41 +08 --- I was all set to guess that glib2 would be the culprit and get into bisecting it, only...it seems not to be. I tried both an updates.img with the previous glib2 build in it and a custom netinst ISO build with a '2.87.3' which is actually just a rebuild of 2.87.0, and both of those still hit the bug. So it must be something else, but nothing else looks as obvious of a suspect unfortunately. Possibly glibc? There's no changes to dbus or ibus-related bits that I can see, or libxcb, or anaconda. I guess gnome-kiosk is another vaguely plausible suspect? I'll keep trying options. --- Additional comment from Adam Williamson on 2026-02-24 09:21:04 +08 --- OK, I think this is somewhere in the gnome-shell / gnome-kiosk / mutter triad. https://adamwill.fedorapeople.org/updates-gs49.img is an updates.img containing the files from gnome-kiosk-49.0-4.fc44.x86_64.rpm , gnome-shell-49.2-4.fc44.x86_64.rpm and mutter-49.2-8.fc44.x86_64.rpm - I built it with: [adamw@toolbx fedora-toolbox-43 anaconda (main %)]$ ./scripts/makeupdates -a ~/Downloads/gnome-kiosk-49.0-4.fc44.x86_64.rpm ~/Downloads/gnome-shell-49.2-4.fc44.x86_64.rpm ~/Downloads/mutter-49.2-8.fc44.x86_64.rpm if I run a KDE install from the 20260210.n.0 Rawhide netinst using that updates.img , it completes successfully. If I run the same install from the same netinst without the updates.img, it hits the bug. Another thing I forgot to post earlier, trimmed backtrace of the /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py --xml process showing it is indeed the thing that spawned the dbus-launch process, via gtk and glib (I cut it off at the point where we get back into python gobject-introspection): #0 __syscall_cancel_arch () at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56 No locals. #1 0x00007efdd44751ec in __internal_syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=a4@entry=0, a5=a5@entry=0, a6=a6@entry=0, nr=7) at cancellation.c:49 result = <optimized out> pd = <optimized out> ch = <optimized out> #2 0x00007efdd4475234 in __syscall_cancel (a1=<optimized out>, a2=<optimized out>, a3=<optimized out>, a4=a4@entry=0, a5=a5@entry=0, a6=a6@entry=0, nr=7) at cancellation.c:75 r = <optimized out> #3 0x00007efdd44ef43e in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:29 No locals. #4 0x00007efdc5d0c26c in g_spawn_sync_impl (working_directory=0x0, argv=<optimized out>, envp=0x0, flags=G_SPAWN_SEARCH_PATH, child_setup=0x0, user_data=0x0, standard_output=<optimized out>, standard_error=<optimized out>, wait_status=0x7ffe3c39afc4, error=0x7ffe3c39b048) at ../glib/gspawn-posix.c:284 fds = {{fd = 5, events = 25, revents = 0}, {fd = 7, events = 25, revents = 0}} outpipe = 5 errpipe = 7 pid = 29723 ret = <optimized out> outstr = 0x563d19ee31a0 errstr = <optimized out> failed = 0 status = 22077 __func__ = <optimized out> _g_boolean_var_10 = <optimized out> _g_boolean_var_11 = <optimized out> _g_boolean_var_12 = <optimized out> _g_boolean_var_13 = <optimized out> _g_boolean_var_14 = <optimized out> #5 g_spawn_sync (working_directory=working_directory@entry=0x0, argv=<optimized out>, envp=envp@entry=0x0, flags=flags@entry=G_SPAWN_SEARCH_PATH, child_setup=child_setup@entry=0x0, user_data=user_data@entry=0x0, standard_output=0x7ffe3c39afd0, standard_error=0x7ffe3c39afc8, wait_status=0x7ffe3c39afc4, error=0x7ffe3c39b048) at ../glib/gspawn.c:153 __func__ = "g_spawn_sync" #6 0x00007efdc5d0c67f in g_spawn_command_line_sync (command_line=command_line@entry=0x563d19ee2ff0 "dbus-launch --autolaunch=51ec2262ee88469f9a84975e48057f59 --binary-syntax --close-stderr", standard_output=standard_output@entry=0x7ffe3c39afd0, standard_error=standard_error@entry=0x7ffe3c39afc8, wait_status=wait_status@entry=0x7ffe3c39afc4, error=error@entry=0x7ffe3c39b048) at ../glib/gspawn.c:590 retval = <optimized out> argv = 0x563d19ee3250 __func__ = "g_spawn_command_line_sync" #7 0x00007efdc475b267 in get_session_address_dbus_launch (error=error@entry=0x7ffe3c39b048) at ../gio/gdbusaddress.c:1143 ret = 0x0 machine_id = 0x563d19ee2fc0 "51ec2262ee88469f9a84975e48057f59" command_line = 0x563d19ee2ff0 "dbus-launch --autolaunch=51ec2262ee88469f9a84975e48057f59 --binary-syntax --close-stderr" launch_stdout = 0x0 launch_stderr = 0x0 wait_status = 32766 old_dbus_verbose = 0x0 restore_dbus_verbose = 0 #8 0x00007efdc475cda4 in get_session_address_platform_specific (error=0x7ffe3c39b048) at ../gio/gdbusaddress.c:1258 ret = <optimized out> #9 g_dbus_address_get_for_bus_sync (bus_type=G_BUS_TYPE_SESSION, cancellable=0x0, error=0x0) at ../gio/gdbusaddress.c:1354 has_elevated_privileges = 0 ret = <optimized out> s = <optimized out> starter_bus = <optimized out> local_error = 0x0 __func__ = "g_dbus_address_get_for_bus_sync" #10 0x00007efdc476f566 in get_uninitialized_connection (bus_type=bus_type@entry=G_BUS_TYPE_SESSION, cancellable=cancellable@entry=0x0, error=error@entry=0x0) at ../gio/gdbusconnection.c:7979 address = <optimized out> singleton = 0x7efdc486a008 <the_session_bus> ret = 0x0 __func__ = "get_uninitialized_connection" #11 0x00007efdc476f62e in g_bus_get_sync (bus_type=bus_type@entry=G_BUS_TYPE_SESSION, cancellable=cancellable@entry=0x0, error=error@entry=0x0) at ../gio/gdbusconnection.c:8079 connection = <optimized out> __func__ = "g_bus_get_sync" #12 0x00007efdc328c6b5 in environment_has_portals () at ../gdk/gdk.c:464 bus = 0x0 result = 0x0 activatable_names = 0x0 name = 0x0 error = 0x0 cached = <optimized out> has_portals = <optimized out> __func__ = <optimized out> #13 gdk_display_should_use_portal (display=<optimized out>, portal_interface=0x0, min_version=0) at ../gdk/gdk.c:642 sandboxed = <optimized out> #14 gdk_display_should_use_portal (display=<optimized out>, portal_interface=0x0, min_version=0) at ../gdk/gdk.c:619 sandboxed = <optimized out> #15 0x00007efdc32b07f7 in file_transfer_portal_register () at ../gdk/filetransferportal.c:606 called = <optimized out> #16 0x00007efdc2f2de61 in file_transfer_portal_register () at ../gdk/gdk.c:239 called = <optimized out> _pp = <optimized out> _ptr = <optimized out> #17 gdk_content_init_serializers () at ../gdk/gdkcontentserializer.c:1054 formats = <optimized out> f = <optimized out> charset = 0x0 initialized = <optimized out> #18 gdk_content_init_serializers () at ../gdk/gdkcontentserializer.c:966 formats = <optimized out> f = <optimized out> charset = <optimized out> initialized = <optimized out> fmt = <optimized out> mimes = <optimized out> m = <optimized out> name = <optimized out> mime = <optimized out> #19 gdk_pre_parse () at ../gdk/gdk.c:357 disabled_features = <optimized out> #20 do_pre_parse_initialization () at ../gtk/gtkmain.c:524 env_string = <optimized out> slowdown = <optimized out> __func__ = <optimized out> #21 gtk_init_check () at ../gtk/gtkmain.c:658 ret = <optimized out> __func__ = <optimized out> #22 gtk_init_check () at ../gtk/gtkmain.c:643 ret = <optimized out> __func__ = "gtk_init_check" #23 0x00007efdc5c0c056 in ffi_call_unix64 () at ../src/x86/unix64.S:104 No locals. #24 0x00007efdc5c0805c in ffi_call_int (cif=cif@entry=0x563d19eda5c0, fn=fn@entry=0x7efdc2f2cc10 <gtk_init_check>, rvalue=<optimized out>, rvalue@entry=0x7ffe3c39b520, avalue=avalue@entry=0x0, closure=closure@entry=0x0) at ../src/x86/ffi64.c:676 classes = {435004864, 22077, 1010414832, 32766} stack = <optimized out> argp = 0x7ffe3c39b370 "\003" arg_types = <optimized out> gprcount = 0 ssecount = <optimized out> ngpr = 32509 nsse = -976775186 i = <optimized out> avn = <optimized out> flags = <optimized out> reg_args = <optimized out> #25 0x00007efdc5c0ad8e in ffi_call (cif=cif@entry=0x563d19eda5c0, fn=0x7efdc2f2cc10 <gtk_init_check>, rvalue=rvalue@entry=0x7ffe3c39b520, avalue=0x0) at ../src/x86/ffi64.c:713 arg_types = <optimized out> i = <optimized out> nargs = <optimized out> max_reg_struct_size = <optimized out> #26 0x00007efdc5e3a080 in pygi_invoke_c_callable (function_cache=0x563d19eda530, state=<optimized out>, py_args=<optimized out>, py_nargsf=<optimized out>, py_kwnames=<optimized out>) at ../gi/pygi-invoke.c:722 _save = 0x7efdd4c3c560 <_PyRuntime+315648> cache = 0x563d19eda530 ffi_return_value = {v_boolean = 0, v_int8 = 0 '\000', v_uint8 = 0 '\000', v_int16 = 0, v_uint16 = 0, v_int32 = 0, v_uint32 = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_short = 0, v_ushort = 0, v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_ssize = 0, v_size = 0, v_string = 0x0, v_pointer = 0x0} ret = 0x0 --- Additional comment from Fedora Admin user for bugzilla script actions on 2026-02-24 09:21:14 +08 --- Bug reports for this component on Red Hat Bugzilla are not actively monitored. Please consider reporting your issue directly to GNOME at https://gitlab.gnome.org/GNOME/ to improve the chances that your issue will be resolved. This issue should only be kept open if it: 1. Relates to Fedora packaging or integration with other Fedora components 2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions If this issue isn't needed for either of these two reasons, please: * create an issue with GNOME * add a link to the GNOME issue here * close this issue as CLOSED/UPSTREAM Thank you! --- Additional comment from fujiwara on 2026-02-24 12:53:53 +08 --- ibus-daemon should not require to open any displays so I'd always say ibus-typing-booster should not open a display with "--xml" option. But ibus-anthy does not require any displays with "--xml" option. (In reply to Adam Williamson from comment #7) > INFO [scriptlet] (ibus write-cache:29935): IBUS-WARNING **: 19:50:24.373: > Engines exec:/usr/libexec/ibus-engine-anthy --xml is failed: > Engines exec:/usr/libexec/ibus-engine-typing-booster --xml is failed: > Engines exec:/usr/libexec/ibus-engine-libpinyin --xml is failed: > Engines exec:/usr/libexec/ibus-engine-m17n --xml is failed: I'm not sure why the script was failed. You could run `/usr/libexec/ibus-engine-anthy --xml` command locally by manual and notice it just combines the XML strings. --- Additional comment from Adam Williamson on 2026-02-24 14:40:18 +08 --- The failures per se aren't necessarily a problem unless we really need these commands to actually *work* at install time (I'm assuming not since all it's doing is building/updating a cache). It's not uncommon for scriptlets running in the installer chroot environment to fail as it's a somewhat odd environment. It's the hang that's the problem, as it prevents the transaction completing. --- Additional comment from Matthias Clasen on 2026-02-25 00:07:49 +08 --- I would consider this an ibus (more specifically ibus-typing-booster) bug if it runs something in a trigger that tries to open a display or a dbus connection, or somesuch. That being said, dbus calls should still time out after 25 seconds, allowing things to eventually fail. What is the deadlock here ? --- Additional comment from Adam Williamson on 2026-02-25 01:35:44 +08 --- I don't know. All I know is up above: the fact that the hang started happening with the GNOME 50 update, and the backtraces of the stuck processes. I'm looking at ibus-typing-booster now and it looks like it does specifically try to *not* do anything that would open a display when running in the --xml mode, e.g. there's a long comment about it here: https://github.com/mike-fabian/ibus-typing-booster/blob/c0bac5f73142c7f2cd8… In the XML mode, large chunks of main.py are skipped. Essentially all that actually gets run is the environment discovery stuff and arg parsing at the start, the imports from xml.etree.ElementTree , and the write_xml() function. The IMApp class never gets instantiated. I'm trying now to think/see how it could still wind up in us getting into display code. I guess we also don't know how exactly the behaviour changed with GNOME 50. Did this display code path not get hit at all with GNOME 49? Or did we still hit it, but it didn't hang? I guess the latter is more likely, but I don't know for sure. --- Additional comment from Adam Williamson on 2026-02-25 01:39:33 +08 --- aha, so, main.py (unconditionally) imports itb_util.py , and itb_util.py imports Gdk and Gtk from itb_gtk . That's one obvious thing. There's also code in write_xml which is explicitly poking at desktop-y stuff: symbol = '🚀' if (itb_util.is_desktop('gnome') and itb_util.get_gnome_shell_version() >= (48, 3)): # If running on Gnome and gnome-shell is new enough to contain # https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/3753 # make the symbol black and white: symbol = '🚀\uFE0E' so, all of that likely has something to do with this. I'll go do some git blame'ing on all this stuff and see if there's a pattern where the idea of avoiding display code in the XML output path got lost over time... --- Additional comment from Adam Williamson on 2026-02-25 01:46:47 +08 --- Yeah, looks like that's the case. The big long comment comes from 2021: https://github.com/mike-fabian/ibus-typing-booster/commit/93ce0203c The import of itb_util comes from 2024: https://github.com/mike-fabian/ibus-typing-booster/commit/e87d24c51 The code snippet in the previous comment comes from June 2025: https://github.com/mike-fabian/ibus-typing-booster/commit/295ae18e so it does look like when adding various enhancements in 2024 and 2025, Mike might've forgotten about trying to avoid setting up a display on the --xml path. --- Additional comment from Fedora Update System on 2026-02-25 05:26:58 +08 --- FEDORA-2026-d8b30d5a3b (ibus-1.5.34~beta1-3.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-d8b30d5a3b --- Additional comment from Adam Williamson on 2026-02-25 06:50:50 +08 --- The update uses a suggestion from mclasen: it runs the trigger scriptlets via `env -i` so all environment variables are unset. This either avoids us going down the gdk->dbus-session path at all, or makes it not hang, we don't know which (probably the former), but it works. We suspect the install transaction uses the *installer environment's* environment variables (despite the fact it's installing into a chroot), which might or might not be considered a bug in itself, but we probably shouldn't poke it during a beta freeze; just changing these scriptlets is safer. So there are a few different things here: 1) ibus-typing-booster should go back to avoiding the gtk/gdk path when just doing --xml. We can probably achieve that by separating the m17n bits it really needs in itb_util out from the rest of it. 2) arguably, all the desktop environment detection stuff in ibus-typing-booster is fragile at least for use in RPM scriptlets, because those don't always run within the same environment in which ibus-typing-booster will actually be used (e.g. when doing offline updates, as well as in this installer path). 3) there probably is a bug of some kind in gnome-shell/gnome-kiosk/mutter here, since we survived ibus-typing-booster going down the gtk/gdk path with GNOME 49, but we don't with GNOME 50. 4) we might want to consider dropping some or all of the installer environment's env vars from the set used for running the install package transaction. Since there are criteria issues around accepting this as a blocker, but we have a fix/workaround now, I'm proposing it as an FE so we can get the fix in without worrying about the criteria. --- Additional comment from Fedora Update System on 2026-02-25 07:10:20 +08 --- FEDORA-2026-d8b30d5a3b has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-d8b30d5a3b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-d8b30d5a3b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. --- Additional comment from Adam Williamson on 2026-02-25 07:22:30 +08 --- +3 FE in https://pagure.io/fedora-qa/blocker-review/issue/2048 , marking accepted. --- Additional comment from fujiwara on 2026-02-25 09:53:09 +08 --- @Adam Williamson: Thank you for the evaluation. If we will enhance ibus-typing-booster, it would be better to fork this bug to the new one since a change was applied to ibus this time. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2362357 [Bug 2362357] Fedora 44 Beta blocker bug tracker https://bugzilla.redhat.com/show_bug.cgi?id=2362358 [Bug 2362358] Fedora 44 Beta freeze exception bug tracker https://bugzilla.redhat.com/show_bug.cgi?id=2439813 [Bug 2439813] KDE network installs hang during scriptlets (%triggerin on ibus) -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2442573 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 5

[Bug 1088983] RFE: support sougo pinyin in Fedora
by bugzilla＠redhat.com 24 Apr '26

24 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=1088983 Fedora Admin user for bugzilla script actions <fedora-admin-xmlrpc(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|pwu(a)redhat.com |alexepico(a)gmail.com --- Comment #3 from Fedora Admin user for bugzilla script actions <fedora-admin-xmlrpc(a)fedoraproject.org> --- This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1088983 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 0

[Bug 2460541] New: [abrt] imsettings: g_malloc0_n(): imsettings-daemon killed by SIGABRT
by bugzilla＠redhat.com 22 Apr '26

22 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2460541 Bug ID: 2460541 Summary: [abrt] imsettings: g_malloc0_n(): imsettings-daemon killed by SIGABRT Product: Fedora Version: 44 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:8b8d4cb79153aa86bf5c71a5a74b459e4bd8183c;VAR IANT_ID=workstation; Component: imsettings Assignee: tagoh(a)redhat.com Reporter: mfabian(a)redhat.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: Version-Release number of selected component: imsettings-1.8.11-2.fc44 Additional info: reporter: libreport-2.17.15 type: CCpp reason: imsettings-daemon killed by SIGABRT journald_cursor: s=0a42150c4c5e4daaa68849b7d3dfe01e;i=100ef;b=fa8669f8e32147168fe5695ed2047724;m=14d6fe891f;t=65008f24d3ae9;x=9ae49b695a645e79 executable: /usr/libexec/imsettings-daemon cmdline: /usr/libexec/imsettings-daemon --replace cgroup: 0::/user.slice/user-1000.slice/user@1000.service/app.slice/run-p17043-i17044.service rootdir: / uid: 1000 kernel: 6.19.13-300.fc44.x86_64 package: imsettings-1.8.11-2.fc44 runlevel: /bin/sh: 行 1: runlevel: command not found xsession_errors: backtrace_rating: 4 crash_function: g_malloc0_n comment: Truncated backtrace: Thread no. 1 (9 frames) #7 g_malloc0_n at ../glib/gmem.c:435 #8 _start_process at /usr/src/debug/imsettings-1.8.11-2.fc44.x86_64/imsettings-daemon/imsettings-proc.c:351 #9 _start_main_process at /usr/src/debug/imsettings-1.8.11-2.fc44.x86_64/imsettings-daemon/imsettings-proc.c:272 #10 imsettings_proc_spawn at /usr/src/debug/imsettings-1.8.11-2.fc44.x86_64/imsettings-daemon/imsettings-proc.c:716 #11 imsettings_server_cb_switch_im at /usr/src/debug/imsettings-1.8.11-2.fc44.x86_64/imsettings-daemon/imsettings-server.c:921 #12 imsettings_server_bus_method_call at /usr/src/debug/imsettings-1.8.11-2.fc44.x86_64/imsettings-daemon/imsettings-server.c:1277 #13 call_in_idle_cb at ../gio/gdbusconnection.c:5476 #16 g_main_context_dispatch_unlocked at ../glib/gmain.c:4451 #17 g_main_context_iterate_unlocked at ../glib/gmain.c:4516 Potential duplicate: bug 2361916 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2460541 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 0

[Bug 1326470] glibc `locale -a` output does not exactly match between locale-archive and langpacks.
by bugzilla＠redhat.com 21 Apr '26

21 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=1326470 Florian Weimer <fweimer(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|fberat(a)redhat.com |glibc-bugzilla(a)redhat.com Status|ASSIGNED |NEW --- Comment #17 from Florian Weimer <fweimer(a)redhat.com> --- Next step: We should reach out to the systemd maintainers and raise the bug that they filter out UTF-8-only locales (unless glibc-all-langpacks is installed). -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1326470 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 0

[Bug 2380583] New: fcitx-anthy: FTBFS with change proposal CMake 4.0
by bugzilla＠redhat.com 20 Apr '26

20 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2380583 Bug ID: 2380583 Summary: fcitx-anthy: FTBFS with change proposal CMake 4.0 Product: Fedora Version: rawhide Status: NEW Component: fcitx-anthy Assignee: robinlee.sysu(a)gmail.com Reporter: fedora(a)lecris.me QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, robinlee.sysu(a)gmail.com, yanqiyu01(a)gmail.com Blocks: 2376114 Target Milestone: --- Classification: Fedora \ Dear package maintainer, This is an automated bug created due to a FTBFS when rebuilding this package for the change proposal CMake 4.0. The rebuild is being tracked in https://copr.fedorainfracloud.org/coprs/cmake-4.0. See https://fedoraproject.org/wiki/Changes/CMake4.0 for more information on how to make the package compatible. More specifically, depending on the state of the project: - If it is actively maintained, please update the `cmake_minimum_required`, and instruct upstream to do so as well. To minimize future maintenance, please add a higher bound as well, preferrably with the highest CMake version being tested. You may use 4.0 as the higher bound as this is being tested in the tracked copr project. - If the project is not maintained, you may add `CMAKE_POLICY_VERSION_MINIMUM=3.5` as a CMake variable or environment variable. You can check the build locally following the instructions in the change proposal, or submit your build to the tracking copr project. Let me know if you encounter any issues, or need any other help. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2376114 [Bug 2376114] CMake 4.0 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2380583 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 2

[Bug 2459606] New: harfbuzz-14.2.0 is available
by bugzilla＠redhat.com 20 Apr '26

20 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2459606 Bug ID: 2459606 Summary: harfbuzz-14.2.0 is available Product: Fedora Version: rawhide Status: NEW Component: harfbuzz Keywords: FutureFeature, Triaged Assignee: pnemade(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, kalevlember(a)gmail.com, moceap(a)hotmail.com, pnemade(a)redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 14.2.0 Upstream release that is considered latest: 14.2.0 Current version/release in rawhide: 14.1.0-2.fc45 URL: https://harfbuzz.github.io 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/1299/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/harfbuzz -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2459606 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 4

[Bug 2456894] New: translate-toolkit-3.19.4 is available
by bugzilla＠redhat.com 15 Apr '26

15 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2456894 Bug ID: 2456894 Summary: translate-toolkit-3.19.4 is available Product: Fedora Version: rawhide Status: NEW Component: translate-toolkit Keywords: FutureFeature, Triaged Assignee: sshil(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com, petersen(a)redhat.com, sshil(a)redhat.com, sundeep_anand(a)yahoo.com Target Milestone: --- Classification: Fedora Releases retrieved: 3.19.4 Upstream release that is considered latest: 3.19.4 Current version/release in rawhide: 3.19.3-1.fc45 URL: http://toolkit.translatehouse.org/ 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/3685/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/translate-toolkit -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2456894 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 8

[Bug 2457887] New: CVE-2026-34480 cldr-emoji-annotation: Apache Log4j Core: Invalid XML output causes denial of service in logging [fedora-all]
by bugzilla＠redhat.com 14 Apr '26

14 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2457887 Bug ID: 2457887 Summary: CVE-2026-34480 cldr-emoji-annotation: Apache Log4j Core: Invalid XML output causes denial of service in logging [fedora-all] Product: Fedora Version: rawhide Status: NEW Whiteboard: {"flaws": ["43e81c52-9a5c-4fd5-8679-d40721c51d82"]} Component: cldr-emoji-annotation Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: tfujiwar(a)redhat.com Reporter: jmoroney(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Blocks: 2457328 Target Milestone: --- Classification: Fedora Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2457887 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 1

[Bug 2457905] New: CVE-2026-34477 cldr-emoji-annotation: Apache Log4j Core: Man-in-the-middle attack due to incomplete hostname verification [fedora-all]
by bugzilla＠redhat.com 14 Apr '26

14 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2457905 Bug ID: 2457905 Summary: CVE-2026-34477 cldr-emoji-annotation: Apache Log4j Core: Man-in-the-middle attack due to incomplete hostname verification [fedora-all] Product: Fedora Version: rawhide Status: NEW Whiteboard: {"flaws": ["7c2c7a23-223c-4fc8-a8cb-4a45291c236a"]} Component: cldr-emoji-annotation Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: tfujiwar(a)redhat.com Reporter: jmoroney(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Blocks: 2457319 Target Milestone: --- Classification: Fedora Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2457905 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 1

[Bug 2326455] New: [abrt] ibus-panel: wl_proxy_get_version(): ibus-ui-gtk3 killed by SIGSEGV
by bugzilla＠redhat.com 08 Apr '26

08 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2326455 Bug ID: 2326455 Summary: [abrt] ibus-panel: wl_proxy_get_version(): ibus-ui-gtk3 killed by SIGSEGV Product: Fedora Version: 41 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:c75ecfa14c60b64aa5a0248ea5b67ce73f59fb4e;VAR IANT_ID=kde; Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: josiah.kelsall(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora Version-Release number of selected component: ibus-panel-1.5.31-1.fc41 Additional info: reporter: libreport-2.17.15 type: CCpp reason: ibus-ui-gtk3 killed by SIGSEGV journald_cursor: s=bddcfc14326c495fb4104e9a987039d9;i=5494c7d;b=02ef6094b287413cb6d4e63a1ff0a693;m=2ae2fdda6;t=626e97fe3eeec;x=3ac86f5e15988c executable: /usr/libexec/ibus-ui-gtk3 cmdline: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon --daemon-args $'--xim --panel disable' cgroup: 0::/user.slice/user-5120.slice/user@5120.service/session.slice/plasma-kwin_wayland.service rootdir: / uid: 5120 kernel: 6.11.7-300.fc41.x86_64 package: ibus-panel-1.5.31-1.fc41 runlevel: N 5 backtrace_rating: 4 crash_function: wl_proxy_get_version Truncated backtrace: Thread no. 1 (15 frames) #0 wl_proxy_get_version at ../src/wayland-client.c:2313 #1 zwp_input_method_context_v1_preedit_string at ../../client/wayland/input-method-unstable-v1-client-protocol.h:389 #2 _context_hide_preedit_text_cb at ../../client/wayland/ibuswaylandim.c:500 #5 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3887 #6 signal_emit_valist_unlocked at ../gobject/gsignal.c:3519 #9 ibus_input_context_g_signal at /usr/src/debug/ibus-1.5.31-1.fc41.x86_64/src/ibusinputcontext.c:605 #11 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3927 #12 signal_emit_valist_unlocked at ../gobject/gsignal.c:3519 #15 on_signal_received at ../gio/gdbusproxy.c:874 #16 emit_signal_instance_in_idle_cb at ../gio/gdbusconnection.c:4189 #19 g_main_context_dispatch_unlocked at ../glib/gmain.c:4208 #20 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4273 #22 gtk_main at ../gtk/gtkmain.c:1329 #23 application_run at /usr/src/debug/ibus-1.5.31-1.fc41.x86_64/ui/gtk3/application.vala:87 #24 application_main at /usr/src/debug/ibus-1.5.31-1.fc41.x86_64/ui/gtk3/application.vala:354 Potential duplicate: bug 2252227 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2326455 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 13

[Bug 1326470] glibc `locale -a` output does not exactly match between locale-archive and langpacks.
by bugzilla＠redhat.com 08 Apr '26

08 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=1326470 Florian Weimer <fweimer(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(psatpute(a)redhat.c | |om) --- Comment #16 from Florian Weimer <fweimer(a)redhat.com> --- (In reply to Carlos O'Donell from comment #14) > Note that "SYSTEMD_LIST_NON_UTF8_LOCALES=1 localectl list-locales" should > also be compared for matching correctness since systemd does some filtering. This does not run “locale -a” under the covers. If we change the locale command output, it will not alter the “localectl list-locales” output. Creating the symbolic links does not work, either, because systemd skips over entries that do not have DT_DIR (not sure if the code handles DT_UNKNOWN correctly). The systemd code lists subdirectories /usr/lib/locale and parses the binary locale archive file (which we do not treat as part of ABI on the glibc side, oh well). By default, locales whose canonical name does not end with ".utf8" will be skipped by the systemd code even if the locale name is UTF-8 because it's purely name-based. This is probably the reason for this bug report: “localectl list-locales” does not list mr_IN by default even though it's an UTF-8 locale, and systemd wants to include those in the output. Next step is to file an upstream issue with systemd, to get an idea what they want to do. For example, can they just run “locale -a” and parse its output? Then we can concentrate on fixing the locale command in such a way that it includes the expected output for systemd. Pravin, do you still remember whether this was about “locale -a” output specifically, or localectl integration 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=1326470 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 0

[Bug 2455367] New: libchewing-0.12.0 is available
by bugzilla＠redhat.com 07 Apr '26

07 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2455367 Bug ID: 2455367 Summary: libchewing-0.12.0 is available Product: Fedora Version: rawhide Status: NEW Component: libchewing Keywords: FutureFeature, Triaged Assignee: kanru(a)kanru.info Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, kanru(a)kanru.info, robinlee.sysu(a)gmail.com Target Milestone: --- Classification: Fedora Releases retrieved: 0.12.0 Upstream release that is considered latest: 0.12.0 Current version/release in rawhide: 0.11.0-2.fc44 URL: https://chewing.im/ 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/1577/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/libchewing -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2455367 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 4

[Bug 2444009] Keyboard layout latch accents broken after update
by bugzilla＠redhat.com 07 Apr '26

07 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2444009 --- Comment #20 from fujiwara <tfujiwar(a)redhat.com> --- > but not when KDE is set to something else (e.g. en(us) - though I'm not sure if this counts as a bug. Also, after changing layouts many times and ibus restarts, this mismatched layout issue seemed to disappear. As I noted, now IBus supports such a situation. I'd ask you to describe your issue with detail. IBus now works with the latch keys in case that you set "lv(tilde)" for IBus keymap and "us" for the session keymap. Do you mean your issue happens only when you switch layouts many times? I assume you switch the layouts of the IBus keymaps with Super-space key, I.e. configuring multiple keymaps with ibus-setup -> "Input Method" seciton. > When I enable "Use system keyboard layout" in ibus preferences, It means to use the session keymap forcibly and IBus won't set any keymaps so your issue cann be reproduced until your issue will be fixed in KDE side. So the new feature does not enhance your issue. I'm not sure whether KDE(kwin_wayland) or each application should fix your issue in fact. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2444009 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 0

[Bug 2445691] New: IBus misrecognize LXQt desktop as Plasma desktop
by bugzilla＠redhat.com 07 Apr '26

07 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2445691 Bug ID: 2445691 Summary: IBus misrecognize LXQt desktop as Plasma desktop Product: Fedora Version: 44 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, tfujiwar(a)redhat.com Target Milestone: --- Classification: Fedora I installed Fedora-LXQt-Live-44-20260308.n.0.x86_64.iso and ibus is brought up by imsettings though, ibus warns it should be setup by systemsettings on KDE. Even though it isn't KDE and there are no systemsettings nor similar equipment. Reproducible: Always Steps to Reproduce: 1.Install LXQt from Live with Japanese 2.Log into LXQt desktop 3. Actual Results: The notification from ibus open Expected Results: No notifications about KDE -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2445691 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 9

[Bug 2451645] New: CVE-2026-34085 fontconfig: Fontconfig: Security flaw allows arbitrary code execution or system crash [fedora-all]
by bugzilla＠redhat.com 07 Apr '26

07 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2451645 Bug ID: 2451645 Summary: CVE-2026-34085 fontconfig: Fontconfig: Security flaw allows arbitrary code execution or system crash [fedora-all] Product: Fedora Version: rawhide Status: NEW Whiteboard: {"flaws": ["65df9a0b-8d8a-40c1-a4e1-f6ae7b5cc3e9"]} Component: fontconfig Keywords: Security, SecurityTracking Severity: medium Priority: medium Assignee: tagoh(a)redhat.com Reporter: trathi(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: ajax(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org, i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com, rstrode(a)redhat.com, tagoh(a)redhat.com Blocks: 2451414 (CVE-2026-34085) Target Milestone: --- Classification: Fedora Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2451414 [Bug 2451414] CVE-2026-34085 fontconfig: Fontconfig: Security flaw allows arbitrary code execution or system crash -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2451645 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 1

[Bug 2444009] Keyboard layout latch accents broken after update
by bugzilla＠redhat.com 06 Apr '26

06 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2444009 --- Comment #19 from Askolds <askolds11+rh(a)gmail.com> --- The Caps lock issue seemed to be fixed when I booted up the machine, so maybe just a case of needing another reboot (I did one after updates). Accents work correctly now when I set both layouts (KDE and ibus) to latvian (tilde), but not when KDE is set to something else (e.g. en(us) - though I'm not sure if this counts as a bug. Also, after changing layouts many times and ibus restarts, this mismatched layout issue seemed to disappear. When I enable "Use system keyboard layout" in ibus preferences, both with "ibus restart" and without it, accents only work with quick succession of the symbol key after the accent key (tilde). I'm not sure if this is the correct command, but the KDE keyboard icon might just not set the XKB layout correctly (command run with latvian layout in KDE icon): setxkbmap -query | grep layout WARNING: Running setxkbmap against an Xwayland server layout: us The ibus icon shows latvian layout though, or rather the layout I had set it to. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2444009 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 0

[Bug 2444009] Keyboard layout latch accents broken after update
by bugzilla＠redhat.com 05 Apr '26

05 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2444009 --- Comment #18 from fujiwara <tfujiwar(a)redhat.com> --- I updated the COPR repo with the latest patch: https://copr.fedorainfracloud.org/coprs/fujiwara/test/ - Fix latch key with shift in cause it used by compose - Support use-system-keyboard-layout to use the session layout with ibus-setup @Askolds: > Caps lock seems to get stuck (after toggling it once, it can no longer be disabled I couldn't reproduce your issue with both case of (system keymap lv, ibus keymap lv) and (system keymap us, ibus keymap lv). When I type CapsLock, a, b, c, CapsLock, d, "ABCd" is output correctly with ibus-1.5.34~rc1-4.1 in COPR. But it would be good for you to try ibus-1.5.34~rc2-1.1 in COPR. I reported clicking KDE icon issue for multiple layouts to KDE: https://bugs.kde.org/show_bug.cgi?id=518371 So switching XKB layouts with the XKB option keys works but you need to restart ibus if you switch XKB layouts with clicking KDE keyboard icon. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2444009 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 0

[Bug 2455139] New: harfbuzz-14.1.0 is available
by bugzilla＠redhat.com 04 Apr '26

04 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2455139 Bug ID: 2455139 Summary: harfbuzz-14.1.0 is available Product: Fedora Version: rawhide Status: NEW Component: harfbuzz Keywords: FutureFeature, Triaged Assignee: pnemade(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, kalevlember(a)gmail.com, moceap(a)hotmail.com, pnemade(a)redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 14.1.0 Upstream release that is considered latest: 14.1.0 Current version/release in rawhide: 14.0.0-2.fc45 URL: https://harfbuzz.github.io 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/1299/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/harfbuzz -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2455139 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…

1 4

[Bug 2453867] New: harfbuzz-14.0.0 is available
by bugzilla＠redhat.com 01 Apr '26

01 Apr '26

https://bugzilla.redhat.com/show_bug.cgi?id=2453867 Bug ID: 2453867 Summary: harfbuzz-14.0.0 is available Product: Fedora Version: rawhide Status: NEW Component: harfbuzz Keywords: FutureFeature, Triaged Assignee: pnemade(a)redhat.com Reporter: upstream-release-monitoring(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, kalevlember(a)gmail.com, moceap(a)hotmail.com, pnemade(a)redhat.com Target Milestone: --- Classification: Fedora Releases retrieved: 14.0.0 Upstream release that is considered latest: 14.0.0 Current version/release in rawhide: 13.2.1-1.fc45 URL: https://harfbuzz.github.io 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/1299/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/harfbuzz -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2453867 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 April 2026