ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

[Hadrien]

There is a similar bug but it is on 19.10. I got this on 20.04 after I closed and reopened my session.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: ibus 1.5.22-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 8 14:46:26 2020
ExecutablePath: /usr/libexec/ibus-ui-gtk3
InstallationDate: Installed on 2018-04-07 (732 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
ProcCmdline: /usr/libexec/ibus-ui-gtk3
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fdcf7d9b9e1 <__vfprintf_internal+1>: nop %edx
 PC (0x7fdcf7d9b9e1) ok
 source "%edx" ok
 Stack memory exhausted (SP below stack segment)
 SP (0x7fff10ee8da0) not located in a known VMA region (needed readable region)!
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: ibus
StacktraceTop: __vfprintf_internal (s=0x7fff10ee9340, format=0x7fdcf818e0e9 "%s\n", ap=0x7fff10eeba00, mode_flags=2) at vfprintf-internal.c:1289
Title: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()
UpgradeStatus: Upgraded to focal on 2020-04-04 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
separator:

[Apport retracing service (apport)]

StacktraceSource:
 #0 0x00007fdcf7d9b9e1 in __vfprintf_internal (s=0x7fff10ee9340, format=0x7fdcf818e0e9 "%s\n", ap=0x7fff10eeba00, mode_flags=2) at vfprintf-internal.c:1289
   [Error: vfprintf-internal.c was not found in source tree]
StacktraceTop: __vfprintf_internal (s=0x7fff10ee9340, format=0x7fdcf818e0e9 "%s\n", ap=0x7fff10eeba00, mode_flags=2) at vfprintf-internal.c:1289

[Sebastien Bacher (seb128)]

Gunnar, any clue about this?

It looks similar to that report which is close from the current top 10 on focal
https://errors.ubuntu.com/problem/3a012dedb557f699d32a1f5c166d0c6e0ecd2c70

It seems to have started recently as well (or the retracing changed and made a new report).
We should probably try to understand what's going on there

[Gunnar Hjalmarsson (gunnarhj)]

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.