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
Created attachment 2014797 [details] File: cpuinfo
Created attachment 2014798 [details] File: environ
Created attachment 2014799 [details] File: var_log_messages
Created attachment 2014800 [details] File: mountinfo
Created attachment 2014801 [details] File: dso_list
Created attachment 2014802 [details] File: limits
Created attachment 2014803 [details] File: os_info
Created attachment 2014804 [details] File: maps
Created attachment 2014805 [details] File: backtrace
Created attachment 2014806 [details] File: core_backtrace
Created attachment 2014807 [details] File: proc_pid_status
Created attachment 2014808 [details] File: open_fds
I'd keep the current state at the moment if other users encounter this issue.
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. 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 '39'. 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 39 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.
*** Bug 2324140 has been marked as a duplicate of this bug. ***
*** Bug 2368458 has been marked as a duplicate of this bug. ***
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.
The similar issue is not reported in Fedora 43 yet but I'd postpone the judgement since it's not clarified why BusConnection is NULL.