Description of problem: It has a conflict with tha app from flathub named app.drey.Warp. When I start app.drey.Warp, my ibus-table stop and I cannot use my input method (canjie5). After I stopped app.drey.Warp, the ibus-table works again and I can use my input method. Version-Release number of selected component: ibus-table-1.17.4-3.fc40 Additional info: reporter: libreport-2.17.15 type: CCpp reason: python3.12 killed by SIGABRT journald_cursor: s=b851438adea5488c9c2c2087cbad4e16;i=1a5736;b=16be98526b23462598842ccaa91bc721;m=3c46437d;t=61b1fbb08a027;x=4fab5ac69ab93a00 executable: /usr/bin/python3.12 cmdline: /usr/bin/python3 /usr/share/ibus-table/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.8.11-300.fc40.x86_64 package: ibus-table-1.17.4-3.fc40 runlevel: N 5 dso_list: /usr/bin/python3.12 python3-3.12.3-2.fc40.x86_64 (Fedora Project) 1715406510 backtrace_rating: 4 crash_function: tcache_thread_shutdown comment: It has a conflict with tha app from flathub named app.drey.Warp. When I start app.drey.Warp, my ibus-table stop and I cannot use my input method (canjie5). After I stopped app.drey.Warp, the ibus-table works again and I can use my input method. Truncated backtrace: Thread no. 1 (4 frames) #6 tcache_thread_shutdown at malloc.c:3231 #7 __malloc_arena_thread_freeres at /usr/src/debug/glibc-2.39-15.fc40.x86_64/malloc/arena.c:897 #8 __libc_thread_freeres at thread-freeres.c:41 #10 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Created attachment 2037647 [details] File: proc_pid_status
Created attachment 2037648 [details] File: maps
Created attachment 2037649 [details] File: limits
Created attachment 2037650 [details] File: environ
Created attachment 2037651 [details] File: open_fds
Created attachment 2037652 [details] File: mountinfo
Created attachment 2037653 [details] File: os_info
Created attachment 2037654 [details] File: cpuinfo
Created attachment 2037655 [details] File: core_backtrace
Created attachment 2037656 [details] File: backtrace
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-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 '40'. 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 40 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.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 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.