gkbd-keyboard-display crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libgnomekbd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
i don't know
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gkbd-capplet 3.26.0-2
ProcVersionSign
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 11:44:18 2017
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2016-08-24 (421 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcCmdline: gkbd-keyboard-
SegvAnalysis:
Segfault happened at: 0x7f56e19ebada: mov 0x40(%rax),%rdx
PC (0x7f56e19ebada) ok
source "0x40(%rax)" (0x00000040) not located in a known VMA region (needed readable region)!
destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libgnomekbd
StacktraceTop:
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
gtk_widget_
() at /usr/lib/
Title: gkbd-keyboard-
UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
information type: | Public Security → Public |
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 #1703277, 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.