Fedora Account System
Red Hat Associate
Red Hat Customer
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/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
Created attachment 2104013 [details] File: backtrace
Created attachment 2104014 [details] File: os_info
Created attachment 2104015 [details] File: proc_pid_status
Created attachment 2104016 [details] File: core_backtrace
Created attachment 2104017 [details] File: mountinfo
Created attachment 2104018 [details] File: maps
Created attachment 2104019 [details] File: dso_list
Created attachment 2104020 [details] File: cpuinfo
Created attachment 2104021 [details] File: exploitable
Created attachment 2104022 [details] File: limits
Created attachment 2104023 [details] File: open_fds
Created attachment 2104024 [details] File: environ
I cannot reproduce your backtrace but I guess this issue will be fixed in libX11 1.8.13. (In reply to Patrick Laimbock from comment #1) > Created attachment 2104013 [details] > File: backtrace #0 XFilterEvent (ev=0x7ffcac1ffbc0, window=0) at /usr/src/debug/libX11-1.8.12-1.fc42.x86_64/src/FilterEv.c:93 93 if (win == p->window) { [Current thread is 1 (Thread 0x7f72e912b200 (LWP 385170))] Thread 1 (Thread 0x7f72e912b200 (LWP 385170)): #0 XFilterEvent (ev=0x7ffcac1ffbc0, window=0) at /usr/src/debug/libX11-1.8.12-1.fc42.x86_64/src/FilterEv.c:93 p = 0x2a0 win = 8388648 mask = 0 ret = <optimized out> #1 0x00007f72ea52619f in _gdk_x11_display_queue_events (display=0x558f2221eba0) at ../gdk/x11/gdkeventsource.c:337 #2 0x00007f72ea4c718b in gdk_display_get_event (display=0x558f2221eba0) at ../gdk/gdkdisplay.c:442
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '42'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 42 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 42 entered end-of-life (EOL) status on 2026-05-27. Fedora Linux 42 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.