kazam crashed with SIGSEGV in XkbUseExtension()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kazam (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Après installation de Ubuntu 17.10
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: kazam 1.4.5-2
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 15:45:56 2017
ExecutablePath: /usr/bin/kazam
InstallationDate: Installed on 2016-04-27 (544 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
InterpreterPath: /usr/bin/python3.6
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/bin/kazam
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
SegvAnalysis:
Segfault happened at: 0x7f75a3d58ad4 <XkbUseExtensio
PC (0x7f75a3d58ad4) ok
source "%rcx" ok
destination "0x40(%rax)" (0x00000042) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: kazam
StacktraceTop:
XkbUseExtension () from /usr/lib/
XkbGetUpdatedMap () from /usr/lib/
XkbGetMap () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: kazam crashed with SIGSEGV in XkbUseExtension()
UpgradeStatus: Upgraded to artful on 2017-10-22 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1723268, 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.