kazam crashed with SIGSEGV in XkbGetUpdatedMap

[Zied ALAYA]

it crashes every time I try to launch it.
I am under the new default Ubuntu desktop environment for 17.10

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: kazam 1.4.5-2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 10 16:04:20 2017
ExecutablePath: /usr/bin/kazam
InstallationDate: Installed on 2017-02-03 (249 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/kazam
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
SegvAnalysis:
 Segfault happened at: 0x1573bb0: add (%rax),%al
 PC (0x01573bb0) in non-executable VMA region: 0x012fe000-0x01c3b000 rw-p [heap]
 source "(%rax)" (0x01573c20) ok
 destination "%al" ok
SegvReason: executing writable VMA [heap]
Signal: 11
SourcePackage: kazam
StacktraceTop:
 ()
 XkbGetUpdatedMap () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 XkbGetMap () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 () at /usr/lib/x86_64-linux-gnu/libkeybinder-3.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libkeybinder-3.0.so.0
Title: kazam crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-10-05 (5 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 XkbGetUpdatedMap (dpy=0x15730d0, which=7, xkb=0x1a29690) at ../../../src/xkb/XKBGetMap.c:580
 XkbGetMap (dpy=0x15730d0, which=which@entry=7, deviceSpec=deviceSpec@entry=256) at ../../../src/xkb/XKBGetMap.c:603
 grab_ungrab (rootwin=rootwin@entry=0x1575020, keyval=114, modifiers=67108932, grab=grab@entry=1) at bind.c:203
 do_grab_key (binding=binding@entry=0x1a22910) at bind.c:326

[Launchpad Janitor (janitor)]

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