Version-Release number of selected component: ibus-1.5.25-4.fc35 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-com.redhat.imsettings cmdline: /usr/libexec/ibus-ui-gtk3 crash_function: g_log_structured_standard executable: /usr/libexec/ibus-ui-gtk3 journald_cursor: s=93f0c87a5ddb40c180fefc14bbe21365;i=9dd0;b=48c1555f43f7445d810a696a82d4b428;m=23e8648540;t=5cd441c384ba2;x=2fcb064bfdc1db89 kernel: 5.14.7-300.fc35.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1626760
Created attachment 1827934 [details] File: backtrace
Created attachment 1827935 [details] File: core_backtrace
Created attachment 1827936 [details] File: cpuinfo
Created attachment 1827937 [details] File: dso_list
Created attachment 1827938 [details] File: environ
Created attachment 1827939 [details] File: limits
Created attachment 1827940 [details] File: maps
Created attachment 1827941 [details] File: mountinfo
Created attachment 1827942 [details] File: open_fds
Created attachment 1827943 [details] File: proc_pid_status
Similar problem has been detected: When restarting Plasma Wayland after setting up ibus with imsettings/im-chooser reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-com.redhat.imsettings cmdline: /usr/libexec/ibus-ui-gtk3 crash_function: g_log_structured_standard executable: /usr/libexec/ibus-ui-gtk3 journald_cursor: s=5ab4b1bae590447fa7ccec2d62df873c;i=eea;b=75fb0f7775924f29a1b040ed489928c4;m=3603ecdd;t=5d30316e9586a;x=5f48ed0015a7c2d6 kernel: 5.15.5-200.fc35.x86_64 package: ibus-1.5.25-5.fc35 reason: ibus-ui-gtk3 killed by SIGTRAP rootdir: / runlevel: N 5 type: CCpp uid: 1000
This seems reproducible in KDE Plasma Wayland at least. 1. Start session for new Japanese user (Anthy is setup and ibus running) 2. restart Plasma session and ibus-ui-gtk crashes (and seems to take down ibus if I am not mistaken) 3. restarting a second time and no crash is observed.
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.
I haven't seen this yet with F37
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.