ibus-ui-gtk3 crashed with SIGABRT in raise()

[sureshbabu]

ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

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-0ubuntu22
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 4 13:27:38 2020
ExecutablePath: /usr/libexec/ibus-ui-gtk3
InstallationDate: Installed on 2020-04-03 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcCmdline: /usr/libexec/ibus-ui-gtk3
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_IN
 SHELL=/bin/bash
Signal: 6
SourcePackage: ibus
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

StacktraceTop:
 raise () from /tmp/apport_sandbox_29jr6axy/lib/x86_64-linux-gnu/libc.so.6
 abort () from /tmp/apport_sandbox_29jr6axy/lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message.cold () from /tmp/apport_sandbox_29jr6axy/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1
 g_assertion_message_expr () from /tmp/apport_sandbox_29jr6axy/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1
 panel_construct ()

[Gunnar Hjalmarsson (gunnarhj)]

Called upstream's attention to this via:

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

[Launchpad Janitor (janitor)]

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

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

[Gunnar Hjalmarsson (gunnarhj)]

@Sebastien: Takao Fujiwara provided some hints about this and other similar crash reports at the upstream issue I submitted. I'm thinking that this may be something to look into post-release.