Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Switching between X11 and Wayland provokes these all the time. I got serious keyboard issues with keys 'n', 'b', 'caps lock' and 'f1', they sometimes get stuck so bad, get ignored or repeated, so constantly and so bad after playing a game like WoW in Lutris. I hope this is close to the problem Version-Release number of selected component: ibus-typing-booster-2.26.8-1.fc41 Additional info: reporter: libreport-2.17.15 type: CCpp reason: python3.13 killed by SIGABRT journald_cursor: s=591db716e92c4be4b4be69dcae179483;i=292599;b=c8be905267374bac9f025aaa31014421;m=4039cb539;t=6272e72d6223d;x=7b92b077f6a5b5d1 executable: /usr/bin/python3.13 cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py --ibus cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.freedesktop.IBus.session.GNOME.service rootdir: / uid: 1000 kernel: 6.11.7-300.fc41.x86_64 package: ibus-typing-booster-2.26.8-1.fc41 runlevel: N 5 backtrace_rating: 4 crash_function: Py_Exit comment: Switching between X11 and Wayland provokes these all the time. I got serious keyboard issues with keys 'n', 'b', 'caps lock' and 'f1', they sometimes get stuck so bad, get ignored or repeated, so constantly and so bad after playing a game like WoW in Lutris. I hope this is close to the problem Truncated backtrace: Thread no. 1 (36 frames) #5 Py_Exit at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pylifecycle.c:3396 #6 handle_system_exit at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:635 #7 _PyErr_PrintEx at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:644 #8 PyErr_PrintEx at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:721 #9 pygi_signal_closure_marshal at ../gi/pygi-signal-closure.c:202 #11 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3887 #12 signal_emit_valist_unlocked at ../gobject/gsignal.c:3519 #16 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3887 #17 signal_emit_valist_unlocked at ../gobject/gsignal.c:3519 #20 emit_closed_in_idle at ../gio/gdbusconnection.c:1502 #23 g_main_context_dispatch_unlocked at ../glib/gmain.c:4208 #24 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4273 #26 ffi_call_unix64 at ../src/x86/unix64.S:104 #27 ffi_call_int at ../src/x86/ffi64.c:673 #28 ffi_call at ../src/x86/ffi64.c:710 #29 pygi_invoke_c_callable at ../gi/pygi-invoke.c:684 #30 pygi_function_cache_invoke at ../gi/pygi-cache.c:862 #31 pygi_callable_info_invoke at ../gi/pygi-invoke.c:727 #32 _wrap_g_callable_info_invoke at ../gi/pygi-invoke.c:764 #33 _callable_info_call at ../gi/pygi-info.c:548 #35 _PyObject_MakeTpCall at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Objects/call.c:242 #36 _PyEval_EvalFrameDefault at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/generated_cases.c.h:813 #37 PyEval_EvalCode at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/ceval.c:596 #38 run_eval_code_obj at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:1323 #39 run_mod at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:1408 #40 pyrun_file at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:1241 #41 _PyRun_SimpleFileObject at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:490 #42 _PyRun_AnyFileObject at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Python/pythonrun.c:77 #43 pymain_run_file_obj at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Modules/main.c:409 #44 pymain_run_file at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Modules/main.c:428 #45 pymain_run_python at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Modules/main.c:696 #46 Py_RunMain at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Modules/main.c:775 #47 Py_BytesMain at /usr/src/debug/python3.13-3.13.0-1.fc41.x86_64/Modules/main.c:829 #48 __libc_start_call_main at ../sysdeps/nptl/libc_start_call_main.h:58 #49 __libc_start_main_impl at ../csu/libc-start.c:360 #50 _start Potential duplicate: bug 2185830
Created attachment 2058478 [details] File: proc_pid_status
Created attachment 2058479 [details] File: maps
Created attachment 2058480 [details] File: limits
Created attachment 2058481 [details] File: environ
Created attachment 2058482 [details] File: open_fds
Created attachment 2058483 [details] File: mountinfo
Created attachment 2058484 [details] File: os_info
Created attachment 2058485 [details] File: cpuinfo
Created attachment 2058486 [details] File: core_backtrace
Created attachment 2058487 [details] File: dso_list
Created attachment 2058488 [details] File: backtrace
I cannot reproduce this. Can you still reproduce the problem on Fedora 42? If so, how?
Let's close this. If reporter want to give more details he can reopen this bug or report a fresh bug against later Fedora releases.