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

[christopher glass]

switch user not working.

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: ibus 1.5.19-4ubuntu2
ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
Uname: Linux 5.2.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 2 18:03:59 2019
ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
InstallationDate: Installed on 2019-08-27 (12 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819)
ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: ibus
StacktraceTop:
 __vfprintf_internal (s=0x7f84e5081f5f, format=0x25 <error: Cannot access memory at address 0x25>, ap=0x7ffe1ea7fc20, mode_flags=2) at vfprintf-internal.c:1289
 __vfprintf_internal (s=0x4, format=0x7ffe1ea7fc20 "\030", ap=0x2, mode_flags=<optimized out>) at ../libio/libioP.h:947
Title: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

Stacktrace:
 #0 0x00007f84e4e5b95e in ?? () from /tmp/apport_sandbox_9_b2_nop/lib/x86_64-linux-gnu/libc.so.6
 No symbol table info available.
 #1 0x00007f84e4e5eb68 in ?? () from /tmp/apport_sandbox_9_b2_nop/lib/x86_64-linux-gnu/libc.so.6
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceSource:
 #0 0x00007f84e4e5b95e in ?? () from /tmp/apport_sandbox_9_b2_nop/lib/x86_64-linux-gnu/libc.so.6
 #1 0x00007f84e4e5eb68 in ?? () from /tmp/apport_sandbox_9_b2_nop/lib/x86_64-linux-gnu/libc.so.6
StacktraceTop:
 ?? () from /tmp/apport_sandbox_9_b2_nop/lib/x86_64-linux-gnu/libc.so.6
 ?? () from /tmp/apport_sandbox_9_b2_nop/lib/x86_64-linux-gnu/libc.so.6

[Gunnar Hjalmarsson (gunnarhj)]

Called upstream's attention to this via:

https://github.com/ibus/ibus/issues/2203

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.