Comment 0 for bug 1718736

I was using chromium-browser when first a general freeze has happened.
Gnome-tweak-tool was not opened nor used previously. I have tried hitting Esc & other keyboard combinations to unlock the wayland session, but i only got that crash. And then relogin to a wayland session has failed, but a xorg one is ok. (not rebooted at time)

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-settings-daemon 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Sep 21 19:01:49 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-keyboard
ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-keyboard
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f6714b10d81 <g_type_check_instance_is_fundamentally_a+49>: movzbl 0x14(%rdx),%eax
 PC (0x7f6714b10d81) ok
 source "0x14(%rdx)" (0x200000014) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gsd-keyboard crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo