Bug 2260403

Summary: [abrt] ibus: read_packet(): ibus-x11 killed by SIGABRT
Product: [Fedora] Fedora Reporter: Rick <rick>
Component: ibusAssignee: fujiwara <tfujiwar>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 39CC: i18n-bugs, rick, shawn.p.huang, tfujiwar
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/667f5380c34208ac76537d472a4f9cf8172feb1
Whiteboard: abrt_hash:0df4e5b24651784de0d285e919048a7212b6499f;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-27 22:46:49 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: environ
none
File: limits
none
File: dso_list
none
File: cpuinfo
none
File: backtrace
none
File: proc_pid_status
none
File: maps
none
File: open_fds
none
File: core_backtrace
none
File: mountinfo
none
File: os_info
none
File: var_log_messages none

Description Rick 2024-01-25 22:09:29 UTC
Description of problem:
this happens when I use chrome and it seems to happen after I leave it alone for a bit and do not navigate.

Version-Release number of selected component:
ibus-1.5.29~rc2-6.fc39

Additional info:
reporter:       libreport-2.17.11
cmdline:        /usr/libexec/ibus-x11
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.SettingsDaemon.XSettings.service
rootdir:        /
reason:         ibus-x11 killed by SIGABRT
type:           CCpp
kernel:         6.6.13-200.fc39.x86_64
executable:     /usr/libexec/ibus-x11
package:        ibus-1.5.29~rc2-6.fc39
crash_function: read_packet
comment:        this happens when I use chrome and it seems to happen after I leave it alone for a bit and do not navigate.
uid:            1000
runlevel:       N 5
journald_cursor: s=5e69a1d92d3c40628e6adb0e1c21b2a3;i=61b14;b=3d27ee38d195474ab1c984af3ece5a50;m=2d1d005cd;t=60fcc68a5a691;x=5ebf4aa9c83134c9

Truncated backtrace:
Thread no. 1 (20 frames)
 #8 read_packet at /usr/src/debug/libxcb-1.13.1-12.fc39.x86_64/src/xcb_in.c:325
 #9 _xcb_in_read at /usr/src/debug/libxcb-1.13.1-12.fc39.x86_64/src/xcb_in.c:1030
 #10 _xcb_conn_wait at /usr/src/debug/libxcb-1.13.1-12.fc39.x86_64/src/xcb_conn.c:515
 #12 wait_for_reply at /usr/src/debug/libxcb-1.13.1-12.fc39.x86_64/src/xcb_in.c:516
 #13 xcb_wait_for_reply64 at /usr/src/debug/libxcb-1.13.1-12.fc39.x86_64/src/xcb_in.c:560
 #15 doGetScreenResources at /usr/src/debug/libXrandr-1.5.4-1.fc39.x86_64/src/XrrScreen.c:88
 #16 XRRGetScreenResourcesCurrent at /usr/src/debug/libXrandr-1.5.4-1.fc39.x86_64/src/XrrScreen.c:223
 #17 init_randr15.constprop.0 at ../gdk/x11/gdkscreen-x11.c:520
 #18 init_multihead at ../gdk/x11/gdkscreen-x11.c:1057
 #19 process_monitors_change at ../gdk/x11/gdkscreen-x11.c:1211
 #20 _gdk_x11_screen_size_changed at ../gdk/x11/gdkscreen-x11.c:1250
 #21 gdk_x11_display_translate_event at ../gdk/x11/gdkdisplay-x11.c:1201
 #22 _gdk_x11_event_translator_translate at ../gdk/x11/gdkeventtranslator.c:51
 #23 gdk_event_source_translate_event at ../gdk/x11/gdkeventsource.c:243
 #24 _gdk_x11_display_queue_events at ../gdk/x11/gdkeventsource.c:341
 #25 gdk_display_get_event at ../gdk/gdkdisplay.c:442
 #26 gdk_event_source_dispatch.lto_priv at ../gdk/x11/gdkeventsource.c:354
 #28 g_main_context_dispatch_unlocked at ../glib/gmain.c:4284
 #29 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4349
 #31 ibus_main at /usr/src/debug/ibus-1.5.29

Comment 1 Rick 2024-01-25 22:09:33 UTC
Created attachment 2010576 [details]
File: environ

Comment 2 Rick 2024-01-25 22:09:34 UTC
Created attachment 2010577 [details]
File: limits

Comment 3 Rick 2024-01-25 22:09:36 UTC
Created attachment 2010578 [details]
File: dso_list

Comment 4 Rick 2024-01-25 22:09:37 UTC
Created attachment 2010579 [details]
File: cpuinfo

Comment 5 Rick 2024-01-25 22:09:39 UTC
Created attachment 2010580 [details]
File: backtrace

Comment 6 Rick 2024-01-25 22:09:40 UTC
Created attachment 2010581 [details]
File: proc_pid_status

Comment 7 Rick 2024-01-25 22:09:41 UTC
Created attachment 2010582 [details]
File: maps

Comment 8 Rick 2024-01-25 22:09:43 UTC
Created attachment 2010583 [details]
File: open_fds

Comment 9 Rick 2024-01-25 22:09:44 UTC
Created attachment 2010584 [details]
File: core_backtrace

Comment 10 Rick 2024-01-25 22:09:46 UTC
Created attachment 2010585 [details]
File: mountinfo

Comment 11 Rick 2024-01-25 22:09:47 UTC
Created attachment 2010586 [details]
File: os_info

Comment 12 Rick 2024-01-25 22:09:48 UTC
Created attachment 2010587 [details]
File: var_log_messages

Comment 13 fujiwara 2024-05-22 14:25:19 UTC
Are you still able to reproduce your backtrace?

(In reply to Rick from comment #0)
>  #8 read_packet at
> /usr/src/debug/libxcb-1.13.1-12.fc39.x86_64/src/xcb_in.c:325
>  #9 _xcb_in_read at
> /usr/src/debug/libxcb-1.13.1-12.fc39.x86_64/src/xcb_in.c:1030
>  #10 _xcb_conn_wait at
> /usr/src/debug/libxcb-1.13.1-12.fc39.x86_64/src/xcb_conn.c:515
>  #12 wait_for_reply at
> /usr/src/debug/libxcb-1.13.1-12.fc39.x86_64/src/xcb_in.c:516
>  #13 xcb_wait_for_reply64 at
> /usr/src/debug/libxcb-1.13.1-12.fc39.x86_64/src/xcb_in.c:560
>  #15 doGetScreenResources at
> /usr/src/debug/libXrandr-1.5.4-1.fc39.x86_64/src/XrrScreen.c:88
>  #16 XRRGetScreenResourcesCurrent at
> /usr/src/debug/libXrandr-1.5.4-1.fc39.x86_64/src/XrrScreen.c:223
>  #17 init_randr15.constprop.0 at ../gdk/x11/gdkscreen-x11.c:520
>  #18 init_multihead at ../gdk/x11/gdkscreen-x11.c:1057
>  #19 process_monitors_change at ../gdk/x11/gdkscreen-x11.c:1211
>  #20 _gdk_x11_screen_size_changed at ../gdk/x11/gdkscreen-x11.c:1250
>  #21 gdk_x11_display_translate_event at ../gdk/x11/gdkdisplay-x11.c:1201
>  #22 _gdk_x11_event_translator_translate at
> ../gdk/x11/gdkeventtranslator.c:51
>  #23 gdk_event_source_translate_event at ../gdk/x11/gdkeventsource.c:243
>  #24 _gdk_x11_display_queue_events at ../gdk/x11/gdkeventsource.c:341
>  #25 gdk_display_get_event at ../gdk/gdkdisplay.c:442
>  #26 gdk_event_source_dispatch.lto_priv at ../gdk/x11/gdkeventsource.c:354
>  #28 g_main_context_dispatch_unlocked at ../glib/gmain.c:4284
>  #29 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4349
>  #31 ibus_main at /usr/src/debug/ibus-1.5.29

Comment 14 Aoife Moloney 2024-11-13 11:54:33 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 Aoife Moloney 2024-11-27 22:46:49 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 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.