Version-Release number of selected component: ibus-1.5.27-8.fc38 Additional info: reporter: libreport-2.17.6 type: CCpp reason: ibus-x11 killed by SIGABRT journald_cursor: s=32500b5f39e6467e9ccddd56700852eb;i=43e8f3;b=f22e26d260164e228db6c4bc7b4ef7db;m=869ce7646;t=5f017821d96fc;x=29a8c76b08f7f956 executable: /usr/libexec/ibus-x11 cmdline: /usr/libexec/ibus-x11 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.SettingsDaemon.XSettings.service rootdir: / uid: 1000 kernel: 6.1.0-65.fc38.x86_64+debug package: ibus-1.5.27-8.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: XFree Truncated backtrace: Thread no. 1 (19 frames) #8 XFree at /usr/src/debug/libX11-1.8.1-2.fc38.x86_64/src/XlibInt.c:1633 #9 ProcessQueue at ../../util/IMdkit/i18nPtHdr.c:1762 #10 _Xi18nMessageHandler at ../../util/IMdkit/i18nPtHdr.c:1923 #11 WaitXIMProtocol at ../../util/IMdkit/i18nX.c:524 #12 _gdk_x11_display_queue_events at ../gdk/x11/gdkeventsource.c:337 #13 gdk_display_get_event at ../gdk/gdkdisplay.c:442 #14 gdk_event_source_dispatch.lto_priv at ../gdk/x11/gdkeventsource.c:354 #17 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4238 #18 g_main_context_iteration at ../glib/gmain.c:4303 #19 xim_forward_event.constprop.0 at /usr/src/debug/ibus-1.5.27-8.fc38.x86_64/client/x11/main.c:631 #20 ForwardEventMessageProc at ../../util/IMdkit/i18nPtHdr.c:1224 #21 ProcessQueue at ../../util/IMdkit/i18nPtHdr.c:1758 #22 _Xi18nMessageHandler at ../../util/IMdkit/i18nPtHdr.c:1923 #23 WaitXIMProtocol at ../../util/IMdkit/i18nX.c:524 #24 _gdk_x11_display_queue_events at ../gdk/x11/gdkeventsource.c:337 #25 gdk_display_get_event at ../gdk/gdkdisplay.c:442 #26 gdk_event_source_dispatch.lto_priv at ../gdk/x11/gdkeventsource.c:354 #29 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4238 #31 ibus_main at /usr/src/debug/ibus-1.5.27-8.fc38.x86_64/src/ibusshare.c:325
Created attachment 1934325 [details] File: proc_pid_status
Created attachment 1934326 [details] File: maps
Created attachment 1934327 [details] File: limits
Created attachment 1934328 [details] File: environ
Created attachment 1934329 [details] File: open_fds
Created attachment 1934330 [details] File: mountinfo
Created attachment 1934331 [details] File: os_info
Created attachment 1934332 [details] File: cpuinfo
Created attachment 1934333 [details] File: core_backtrace
Created attachment 1934334 [details] File: dso_list
Created attachment 1934335 [details] File: var_log_messages
Created attachment 1934336 [details] File: backtrace
I cannot reproduce your issue. Are you still able to reproduce the same backtrace? (In reply to Mikhail from comment #12) > Created attachment 1934336 [details] > File: backtrace #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x00007fea7b921363 in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78 #2 0x00007fea7b8cf056 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x00007fea7b8b887c in __GI_abort () at abort.c:79 #4 0x00007fea7b8b95b3 in __libc_message (fmt=fmt@entry=0x7fea7ba2e636 "%s\n") at ../sysdeps/posix/libc_fatal.c:150 #5 0x00007fea7b92b017 in malloc_printerr (str=str@entry=0x7fea7ba31200 "double free or corruption (fasttop)") at malloc.c:5651 #6 0x00007fea7b92cdf2 in _int_free (av=0x7fea7ba67c80 <main_arena>, p=0x5608d2c05d90, have_lock=have_lock@entry=0) at malloc.c:4525 #7 0x00007fea7b92f803 in __GI___libc_free (mem=mem@entry=0x5608d2c05da0) at malloc.c:3367 #8 0x00007fea7baba74d in XFree (data=data@entry=0x5608d2c05da0) at /usr/src/debug/libX11-1.8.1-2.fc38.x86_64/src/XlibInt.c:1633 #9 0x00005608d21dfed8 in ProcessQueue (connect_id=124, ims=0x5608d2c16690) at ../../util/IMdkit/i18nPtHdr.c:1762 #10 _Xi18nMessageHandler (ims=0x5608d2c16690, connect_id=124, p=<optimized out>, delete=<optimized out>) at ../../util/IMdkit/i18nPtHdr.c:1923 #11 0x00005608d21e1cfa in WaitXIMProtocol (dpy=<optimized out>, win=<optimized out>, ev=<optimized out>, client_data=0x5608d2c16690 " \311\036\322\bV") at ../../util/IMdkit/i18nX.c:524 #12 0x00007fea7bd8c38b in _gdk_x11_display_queue_events (display=0x5608d2ba90e0) at ../gdk/x11/gdkeventsource.c:337
Eiyuden Chronicle: Rising in Steam crashed it. reporter: libreport-2.17.6 type: CCpp reason: ibus-x11 killed by SIGABRT journald_cursor: s=e09d7eba979d4985b1fa1a703afb103a;i=139a0;b=755932aa55024a4c8b72142f44109cf7;m=b22f5efa;t=5f3d2c17e5d66;x=88fd2f3338558ee4 executable: /usr/libexec/ibus-x11 cmdline: /usr/libexec/ibus-x11 cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.SettingsDaemon.XSettings.service rootdir: / uid: 1000 kernel: 6.2.0-0.rc6.20230202git9f266ccaa2f5.46.fc38.x86_64 package: ibus-1.5.27-14.fc38 runlevel: N 5 comment: Eiyuden Chronicle: Rising in Steam crashed it. backtrace_rating: 4 crash_function: XFree
Created attachment 1942146 [details] File: backtrace
Any update a few days ago broke it. It was working before?
https://retrace.fedoraproject.org/faf/reports/bthash/f9ff80f00ceb640bbebb03e1067b9d84c605d6e/ The reports was not found or is still being processed Reports are processed every few minutes, try refreshing this site in a while. Wtf.
I was using Proton Experimental as of today.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
Latest update to rawhide fixed the crash. The only problem is that keys are getting stuck in my game.
This can be closed.
Still getting it after some (longer) time now.
(In reply to romulasry from comment #18) > I was using Proton Experimental as of today. What is Proton Experimental? Can you show a URL of the site? Can you reproduce your issue in case you don't use Proton Experimental?
(In reply to fujiwara from comment #23) > (In reply to romulasry from comment #18) > > I was using Proton Experimental as of today. > > What is Proton Experimental? Can you show a URL of the site? > > Can you reproduce your issue in case you don't use Proton Experimental? https://github.com/ValveSoftware/Proton https://github.com/ValveSoftware/Proton/issues/5294 I haven't tried Wine.
Finally I can reproduce this issue.
*** Bug 2174962 has been marked as a duplicate of this bug. ***
FEDORA-2023-e0df9e598e has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-e0df9e598e
*** Bug 2179015 has been marked as a duplicate of this bug. ***
FEDORA-2023-e0df9e598e has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-e0df9e598e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-e0df9e598e has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.