ibus-x11 crashed with SIGSEGV in __GI___poll()

[Barry Kolts]

This happened at start up after software updater requested a restart.I attached
unattended-upgrades.log
unattended-upgrades-dpkg.log
dpkg.log
to show what packages were installed before the restart.

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-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Apr 10 07:16:32 2020
ExecutablePath: /usr/libexec/ibus-x11
InstallationDate: Installed on 2020-03-14 (26 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7f6b2b2919f6 <__run_exit_handlers+198>: mov 0x10(%rax),%rdx
 PC (0x7f6b2b2919f6) ok
 source "0x10(%rax)" (0x1042f359537650) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: ibus
StacktraceTop:
 __GI___poll (fds=0x7f6af80067e0, nfds=3, timeout=1766) at ../sysdeps/unix/sysv/linux/poll.c:29
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ibus_main () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
 ?? ()
Title: ibus-x11 crashed with SIGSEGV in __GI___poll()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

separator:

[Apport retracing service (apport)]

StacktraceTop:
 __GI___poll (fds=0x7f6af80067e0, nfds=3, timeout=1766) at ../sysdeps/unix/sysv/linux/poll.c:29
 g_main_context_iterate.isra () from /tmp/apport_sandbox_t9_oeqnz/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1
 g_main_loop_run () from /tmp/apport_sandbox_t9_oeqnz/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1
 ibus_main () at ibusshare.c:318
 main ()

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.