Bug 2413633

Summary: [abrt] ibus-panel: binding_common_get_xdisplay(): ibus-ui-gtk3 killed by SIGTRAP
Product: [Fedora] Fedora Reporter: 13mwtw1j
Component: ibusAssignee: fujiwara <tfujiwar>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 43CC: 13mwtw1j, i18n-bugs, tfujiwar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b6803f3baf73069e95bc7003a2ffc6d90d4314b
Whiteboard: abrt_hash:e9e901c38d0f3b15163223fa5eace9ece4b879c9;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-11-11 02:06:12 UTC 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: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: dso_list
none
File: backtrace none

Description 13mwtw1j 2025-11-09 10:28:33 UTC 
Version-Release number of selected component:
ibus-panel-1.5.33~rc2-2.fc43

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         ibus-ui-gtk3 killed by SIGTRAP
journald_cursor: s=cd297645783945f1b2eab74426b67a29;i=31d70;b=0f1f97ef90e5460296eae22a81f4292b;m=162cf5fd6;t=642f185e82feb;x=edca0f87d8e00e2
executable:     /usr/libexec/ibus-ui-gtk3
cmdline:        /usr/libexec/ibus-ui-gtk3
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/ptyxis-spawn-f69769a1-9ad1-4a5b-9fb9-2fff81f57d8c.scope
rootdir:        /
uid:            1000
kernel:         6.17.6-300.fc43.x86_64
package:        ibus-panel-1.5.33~rc2-2.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: binding_common_get_xdisplay

Truncated backtrace:
Thread no. 1 (12 frames)
 #4 binding_common_get_xdisplay at /usr/src/debug/ibus-1.5.33
 #6 binding_common_default_is_xdisplay at /usr/src/debug/ibus-1.5.33
 #7 panel_construct at /usr/src/debug/ibus-1.5.33
 #8 panel_new at /usr/src/debug/ibus-1.5.33
 #9 application_bus_name_acquired_cb at /usr/src/debug/ibus-1.5.33
 #10 _application_bus_name_acquired_cb_gd_bus_signal_callback at /usr/src/debug/ibus-1.5.33
 #11 emit_signal_instance_in_idle_cb at ../gio/gdbusconnection.c:4207
 #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
 #19 application_main at /usr/src/debug/ibus-1.5.33
Comment 1 13mwtw1j 2025-11-09 10:28:36 UTC 
Created attachment 2113481 [details]
File: proc_pid_status
Comment 2 13mwtw1j 2025-11-09 10:28:38 UTC 
Created attachment 2113482 [details]
File: maps
Comment 3 13mwtw1j 2025-11-09 10:28:39 UTC 
Created attachment 2113483 [details]
File: limits
Comment 4 13mwtw1j 2025-11-09 10:28:40 UTC 
Created attachment 2113484 [details]
File: environ
Comment 5 13mwtw1j 2025-11-09 10:28:41 UTC 
Created attachment 2113485 [details]
File: open_fds
Comment 6 13mwtw1j 2025-11-09 10:28:42 UTC 
Created attachment 2113486 [details]
File: mountinfo
Comment 7 13mwtw1j 2025-11-09 10:28:44 UTC 
Created attachment 2113487 [details]
File: os_info
Comment 8 13mwtw1j 2025-11-09 10:28:45 UTC 
Created attachment 2113488 [details]
File: cpuinfo
Comment 9 13mwtw1j 2025-11-09 10:28:46 UTC 
Created attachment 2113489 [details]
File: core_backtrace
Comment 10 13mwtw1j 2025-11-09 10:28:47 UTC 
Created attachment 2113490 [details]
File: dso_list
Comment 11 13mwtw1j 2025-11-09 10:28:49 UTC 
Created attachment 2113491 [details]
File: backtrace
Comment 12 fujiwara 2025-11-11 02:06:12 UTC 
You should not execute ibus-daemon directly in Wayland desktop sessions but `ibus start` command is available instead.
If you run it with ibus-setup, it would be a bug in ibus-setup and will be triaged with bug 2392358

*** This bug has been marked as a duplicate of bug 2392358 ***