ayatana-indicator-keyboard-service crashed with SIGSEGV in keyboard_GetLayout()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ayatana-indicator-keyboard (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Crashed on first login.
ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: ayatana-
ProcVersionSign
Uname: Linux 5.8.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu57
Architecture: amd64
CasperMD5CheckR
CrashCounter: 1
CurrentDesktop: MATE
Date: Fri Feb 12 22:45:29 2021
ExecutablePath: /usr/libexec/
InstallationDate: Installed on 2021-02-12 (0 days ago)
InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210212)
ProcCmdline: /usr/libexec/
SegvAnalysis:
Segfault happened at: 0x55c5f98e68d8 <keyboard_
PC (0x55c5f98e68d8) 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-
StacktraceTop:
keyboard_GetLayout ()
?? ()
?? ()
g_type_
?? () from /lib/x86_
Title: ayatana-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
XsessionErrors:
mate-session[
(process:1463): ayatana-
(caja:1418): Gtk-WARNING **: 22:45:27.530: Failed to register client: GDBus.Error:
separator:
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.