gsd-keyboard crashed with SIGSEGV

[Artyom Pozharov]

Bug from /var/crash

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gnome-settings-daemon 3.33.90-1ubuntu2
ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
Uname: Linux 5.2.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 25 22:04:39 2019
Disassembly: => 0x7f2b24cddd44: Cannot access memory at address 0x7f2b24cddd44
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard
ExecutableTimestamp: 1561028231
InstallationDate: Installed on 2019-08-25 (2 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819)
ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard
ProcCwd: /home/ubuntenok
ProcEnviron:
 LANGUAGE=ru_UA:ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

StacktraceSource:
 #0 0x00007f2b24cddd44 in ?? ()
 #1 0x00007f2b24cdcdb3 in ?? ()
 #2 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

[Launchpad Janitor (janitor)]

[Expired for gnome-settings-daemon (Ubuntu) because there has been no activity for 60 days.]