ayatana-indicator-keyboard-service crashed with SIGSEGV in keyboard_GetLayout()

[Abram Daniel]

system went down with kernel panic, restarted to recover mode, went to shell ran the command:
apt-get update --fix-missing
then
apt-get dist-upgrade --fix-missing
then answered Yes to remove obsolete packages
system requested a restart, answered Yes
After a restart, this error popped-up requesting to send and to create this log.

Thanks for a great job you are doing?

ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: ayatana-indicator-keyboard 0.7.900-3
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Sun Feb 21 02:29:19 2021
ExecutablePath: /usr/libexec/ayatana-indicator-keyboard/ayatana-indicator-keyboard-service
InstallationDate: Installed on 2020-12-04 (78 days ago)
InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Alpha amd64 (20201112)
ProcCmdline: /usr/libexec/ayatana-indicator-keyboard/ayatana-indicator-keyboard-service
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x5597e0fa08d8 <keyboard_GetLayout+72>: cmpb $0x0,(%rdx)
 PC (0x5597e0fa08d8) ok
 source "$0x0" ok
 destination "(%rdx)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: ayatana-indicator-keyboard
StacktraceTop:
 keyboard_GetLayout ()
 ?? ()
 ?? ()
 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: ayatana-indicator-keyboard-service crashed with SIGSEGV in keyboard_GetLayout()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lxd plugdev sudo
separator:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1915492, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.