Bug 2262532

Summary: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT
Product: [Fedora] Fedora Reporter: flomaker84
Component: ibusAssignee: fujiwara <tfujiwar>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 45CC: aoellerer, dmitryburstein, flomaker84, i18n-bugs, shawn.p.huang, tfujiwar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4c7954b40e0ce16f48605229469a2eefd1be571
Whiteboard: abrt_hash:b24defc317ee932c47b15b9c24c231f607dad274;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: cpuinfo
none
File: environ
none
File: var_log_messages
none
File: mountinfo
none
File: dso_list
none
File: limits
none
File: os_info
none
File: maps
none
File: backtrace
none
File: core_backtrace
none
File: proc_pid_status
none
File: open_fds none

Description flomaker84 2024-02-03 17:38:06 UTC 
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
Comment 1 flomaker84 2024-02-03 17:38:10 UTC 
Created attachment 2014797 [details]
File: cpuinfo
Comment 2 flomaker84 2024-02-03 17:38:12 UTC 
Created attachment 2014798 [details]
File: environ
Comment 3 flomaker84 2024-02-03 17:38:14 UTC 
Created attachment 2014799 [details]
File: var_log_messages
Comment 4 flomaker84 2024-02-03 17:38:15 UTC 
Created attachment 2014800 [details]
File: mountinfo
Comment 5 flomaker84 2024-02-03 17:38:17 UTC 
Created attachment 2014801 [details]
File: dso_list
Comment 6 flomaker84 2024-02-03 17:38:18 UTC 
Created attachment 2014802 [details]
File: limits
Comment 7 flomaker84 2024-02-03 17:38:19 UTC 
Created attachment 2014803 [details]
File: os_info
Comment 8 flomaker84 2024-02-03 17:38:21 UTC 
Created attachment 2014804 [details]
File: maps
Comment 9 flomaker84 2024-02-03 17:38:22 UTC 
Created attachment 2014805 [details]
File: backtrace
Comment 10 flomaker84 2024-02-03 17:38:24 UTC 
Created attachment 2014806 [details]
File: core_backtrace
Comment 11 flomaker84 2024-02-03 17:38:25 UTC 
Created attachment 2014807 [details]
File: proc_pid_status
Comment 12 flomaker84 2024-02-03 17:38:27 UTC 
Created attachment 2014808 [details]
File: open_fds
Comment 13 fujiwara 2024-05-22 14:48:25 UTC 
I'd keep the current state at the moment if other users encounter this issue.
Comment 14 Aoife Moloney 2024-11-13 11:58:02 UTC 
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.
Comment 15 fujiwara 2024-11-14 03:21:21 UTC 
*** Bug 2324140 has been marked as a duplicate of this bug. ***
Comment 16 fujiwara 2025-10-23 00:53:59 UTC 
*** Bug 2368458 has been marked as a duplicate of this bug. ***
Comment 17 Fedora Release Engineering 2026-05-06 11:34:26 UTC 
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.
Comment 18 fujiwara 2026-05-21 14:04:31 UTC 
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.