onboard crashed with SIGSEGV in PyObject_GetAttrString()

Bug #1205804 reported by Shamad
260
This bug affects 1 person
Affects Status Importance Assigned to Milestone
onboard (Ubuntu)
New
Undecided
Unassigned

Bug Description

bug with keyboard (onboard)

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: onboard 0.99.0~alpha1~tr1190-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
Uname: Linux 3.10.0-5-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Sun Jul 28 13:30:20 2013
ExecutablePath: /usr/bin/onboard
InstallationDate: Installed on 2013-07-27 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130717)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/bin/onboard
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x49bb7e <PyObject_GetAttrString+158>: movzbl 0x1d(%rcx),%r13d
 PC (0x0049bb7e) ok
 source "0x1d(%rcx)" (0x0000001d) not located in a known VMA region (needed readable region)!
 destination "%r13d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: onboard
StacktraceTop:
 PyObject_GetAttrString ()
 PyObject_CallMethod ()
 ?? () from /usr/lib/python3/dist-packages/Onboard/osk.cpython-33m-x86_64-linux-gnu.so
 ?? () from /usr/lib/python3/dist-packages/Onboard/osk.cpython-33m-x86_64-linux-gnu.so
 ?? () from /usr/lib/python3/dist-packages/Onboard/osk.cpython-33m-x86_64-linux-gnu.so
Title: onboard crashed with SIGSEGV in PyObject_GetAttrString()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Shamad (aplus12) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1196324, 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.

information type: Private Security → Public Security
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.