Version-Release number of selected component: ibus-1.5.22-7.fc32 Additional info: reporter: libreport-2.13.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-42.slice/session-c1.scope cmdline: ibus-daemon --panel disable -r --xim crash_function: bus_dbus_impl_connection_filter_cb executable: /usr/bin/ibus-daemon journald_cursor: s=f592520f518043e0bf22bcb1059f85fa;i=5f0d;b=e5641f6c2ed84e629455c7ec8e6a1276;m=1c9e25e;t=5a6dbe50f3604;x=b9e38dca02503832 kernel: 5.6.15-300.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 42 Potential duplicate: bug 1475710
Created attachment 1693626 [details] File: backtrace
Created attachment 1693627 [details] File: core_backtrace
Created attachment 1693628 [details] File: cpuinfo
Created attachment 1693629 [details] File: dso_list
Created attachment 1693630 [details] File: environ
Created attachment 1693631 [details] File: limits
Created attachment 1693632 [details] File: maps
Created attachment 1693633 [details] File: mountinfo
Created attachment 1693634 [details] File: open_fds
Created attachment 1693635 [details] File: proc_pid_status
Created attachment 1693636 [details] File: var_log_messages
I tried to fix the same backtrace in bug 1767976 with ibus-1.5.22-7.fc32 but you still reproduce the issue with the same version. I wait if others report the same backtrace.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
*** Bug 1900282 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-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 '35'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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.
*** This bug has been marked as a duplicate of bug 1767976 ***