onboard crashed with SIGSEGV in PyObject_CallObject()

Bug #1208723 reported by Andrew Diete
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
onboard (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crash report open after auto login on first seat.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: onboard 0.99.0~alpha1~tr1190-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3
Uname: Linux 3.10.0-6-generic x86_64
ApportVersion: 2.12-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Jul 31 19:31:33 2013
ExecutablePath: /usr/bin/onboard
InstallationDate: Installed on 2013-07-10 (26 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130627)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/bin/onboard --xid
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x5714bb <PyObject_CallObject+235>: mov 0x18(%rdi),%esi
 PC (0x005714bb) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: onboard
StacktraceTop:
 PyObject_CallObject ()
 ?? () from /usr/lib/python3/dist-packages/Onboard/osk.cpython-33m-x86_64-linux-gnu.so
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: onboard crashed with SIGSEGV in PyObject_CallObject()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Andrew Diete (adiete-adiete) 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 #1195857, 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 → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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