Description of problem: It appears to happen while I'm using the "zed" IDE. 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=3038da996bb64301a3a8d025b1477d50;i=d56d9e;b=9e313c0541794596abe52b83ffd3d022;m=2c3ef03a09;t=634a3b6ca1a07;x=49f987088ab6daa5 executable: /usr/libexec/ibus-x11 cmdline: /usr/libexec/ibus-x11 --kill-daemon cgroup: 0::/user.slice/user-1001.slice/user/session.slice/org.freedesktop.IBus.session.GNOME.service rootdir: / uid: 1001 kernel: 6.14.5-300.fc42.x86_64 package: ibus-1.5.32-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: _Xi18nSetPropertyOffset comment: It appears to happen while I'm using the "zed" IDE. Truncated backtrace: Thread no. 1 (9 frames) #8 _Xi18nSetPropertyOffset at ../../util/IMdkit/i18nOffsetCache.c:86 #9 ReadXIMMessage at ../../util/IMdkit/i18nX.c:194 #10 WaitXIMProtocol at ../../util/IMdkit/i18nX.c:516 #11 _gdk_x11_display_queue_events at ../gdk/x11/gdkeventsource.c:337 #12 gdk_display_get_event at ../gdk/gdkdisplay.c:442 #13 gdk_event_source_dispatch.lto_priv at ../gdk/x11/gdkeventsource.c:354 #15 g_main_context_dispatch_unlocked at ../glib/gmain.c:4249 #16 g_main_context_iterate_unlocked at ../glib/gmain.c:4314 #18 ibus_main at /usr/src/debug/ibus-1.5.32-1.fc42.x86_64/src/ibusshare.c:336 Potential duplicate: bug 2347229
Created attachment 2089105 [details] File: proc_pid_status
Created attachment 2089106 [details] File: maps
Created attachment 2089107 [details] File: limits
Created attachment 2089108 [details] File: environ
Created attachment 2089109 [details] File: open_fds
Created attachment 2089110 [details] File: mountinfo
Created attachment 2089111 [details] File: os_info
Created attachment 2089112 [details] File: cpuinfo
Created attachment 2089113 [details] File: core_backtrace
Created attachment 2089114 [details] File: dso_list
Created attachment 2089115 [details] File: backtrace
The scenario where this happens is: The "zed" editor will fetch an updated version and relaunch itself with the update. This bug happens consistently in just a few keystrokes after that update and relaunch.
This problem happens to me multiple times a day, and the editor stops taking any input. I have to close and restart my editing session, and I lose some edits. What else can I do to help resolve this?
I had a plan to fix the relative issue with other leak ones but let's evaluate this issue with the higher priority.
FEDORA-2025-9c952aaaa6 (ibus-1.5.32-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-9c952aaaa6
FEDORA-2025-96a83138d1 (ibus-1.5.33~beta1-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-96a83138d1
FEDORA-2025-9c952aaaa6 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-9c952aaaa6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-9c952aaaa6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-96a83138d1 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-96a83138d1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-96a83138d1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-9c952aaaa6 (ibus-1.5.32-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-96a83138d1 (ibus-1.5.33~rc2-2.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
*** Bug 2364698 has been marked as a duplicate of this bug. ***
*** Bug 2368152 has been marked as a duplicate of this bug. ***