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

Bug #1915492 reported by Bill (franksmcb)
60
This bug affects 12 people
Affects Status Importance Assigned to Milestone
ayatana-indicator-keyboard (Ubuntu)
Fix Released
Critical
Martin Wimpress 
ubuntu-mate-settings (Ubuntu)
Fix Released
High
Martin Wimpress 

Bug Description

Ubuntu MATE 21.04 current daily

Expected outcome:
Install Ubuntu MATE and reboot with no errors

Actual outcome:
Install Ubuntu MATE and reboot. On login, ayatana-indicator-keyboard-service crashed
with crash files in /var/crash

_usr_libexec_ayatana-indicator-keyboard_ayatana-indicator-keyboard-service.1000.crash
_usr_libexec_ayatana-indicator-keyboard_ayatana-indicator-keyboard-service.115.crash

ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: ayatana-indicator-keyboard 0.7.900-3
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu57
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Thu Feb 11 22:26:56 2021
ExecutablePath: /usr/libexec/ayatana-indicator-keyboard/ayatana-indicator-keyboard-service
InstallationDate: Installed on 2021-02-12 (0 days ago)
InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210211)
ProcCmdline: /usr/libexec/ayatana-indicator-keyboard/ayatana-indicator-keyboard-service
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x562775ce28d8 <keyboard_GetLayout+72>: cmpb $0x0,(%rdx)
 PC (0x562775ce28d8) 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 lpadmin lxd plugdev sambashare sudo
XsessionErrors:
 mate-session[1385]: WARNING: Unable to find provider '' of required component 'dock'
 (process:1873): ayatana-indicator-sound-WARNING **: 22:26:56.285: volume-control-pulse.vala:745: Unable to connect to dbus server at 'unix:path=/run/user/1000/pulse/dbus-socket': Could not connect: No such file or directory
 (caja:1684): Gtk-WARNING **: 22:26:56.470: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
separator:

Revision history for this message
Bill (franksmcb) (franksmcb) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 keyboard_GetLayout (pKeyboard=0x562777445860, nLayout=0, nLayout@entry=-1, pLanguage=pLanguage@entry=0x7fff61757ad8, pDescription=pDescription@entry=0x0) at ./src/keyboard.c:226
 createHeaderState (self=self@entry=0x5627774430c0) at ./src/service.c:84
 initActions (self=0x5627774430c0) at ./src/service.c:270
 indicator_keyboard_service_init (self=0x5627774430c0) at ./src/service.c:400
 g_type_create_instance (type=<optimized out>) at ../../../gobject/gtype.c:1867

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in ayatana-indicator-keyboard (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1915492

tags: added: iso-testing
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ayatana-indicator-keyboard (Ubuntu):
status: New → Confirmed
information type: Private → Public Security
information type: Public Security → Public
Revision history for this message
Norbert (nrbrtx) wrote :

Still happens on beta iso.

Revision history for this message
Earl (2104-amdgpu) wrote :

Still happens on Hirsute build 30 March.

Changed in ayatana-indicator-keyboard (Ubuntu):
milestone: none → ubuntu-21.04
Revision history for this message
Andrew Hayzen (ahayzen) wrote :
Changed in ayatana-indicator-keyboard (Ubuntu):
status: Confirmed → Fix Committed
assignee: nobody → Martin Wimpress  (flexiondotorg)
Changed in ubuntu-mate-settings (Ubuntu):
status: New → In Progress
assignee: nobody → Martin Wimpress  (flexiondotorg)
Changed in ayatana-indicator-keyboard (Ubuntu):
importance: Medium → Critical
Changed in ubuntu-mate-settings (Ubuntu):
importance: Undecided → High
milestone: none → ubuntu-21.04
Changed in ubuntu-mate-settings (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Norbert (nrbrtx) wrote :

Package from -proposed fixes the issue.

Revision history for this message
Bill (franksmcb) (franksmcb) wrote :

Can confirm that updated package resolves this issue.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-mate-settings - 21.04.5

---------------
ubuntu-mate-settings (21.04.5) hirsute; urgency=medium

  * Only show one keyboard indicator (LP: #1918076)

 -- Martin Wimpress <email address hidden> Thu, 01 Apr 2021 12:09:46 +0100

Changed in ubuntu-mate-settings (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote :

Is the ayatana-indicator-keyboard task still necessary or can it to be closed?

Norbert (nrbrtx)
Changed in ayatana-indicator-keyboard (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Bill (franksmcb) (franksmcb) wrote :

Brian the task can be closed. Thank you.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.