Ouch. We should indeed dig deeper into it. Don't think I can help much with interpreting stacktrace logs, though.
Want to remind of this attempt to get help from upstream: https://github.com/ibus/ibus/issues/2203 Can't tell if Takao's hints are helpful. Also, I noticed a comment Takao made as late as today at <https://github.com/ibus/ibus/issues/2163> (i.e. the issue I would like you to look at for another reason): "IBus no longer uses the binding in IBus GtkIMModule but moved the feature to ibus-extension-gtk3 which can customize the shortcut keys with ibus-setup." So upstream has done something with the code for UI and Gtk3, and most of these latest crash reports are related to just that. ** Bug watch added: github.com/ibus/ibus/issues #2203 https://github.com/ibus/ibus/issues/2203 ** Bug watch added: github.com/ibus/ibus/issues #2163 https://github.com/ibus/ibus/issues/2163 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871625 Title: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1871625/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
