onboard crashed with SIGSEGV in PyUnicode_InternFromString()

Bug #1196794 reported by Svi Roussanoff
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
onboard (Ubuntu)
New
Undecided
Unassigned

Bug Description

tried to start oboard after the last upgrade of 13.10. does not start

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: onboard 0.99.0~alpha1~tr1190-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
Uname: Linux 3.10.0-2-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.10.2-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Tue Jul 2 00:32:10 2013
ExecutablePath: /usr/bin/onboard
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/bin/onboard
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8131ef9 <PyUnicode_InternFromString+89>: movzbl 0x11(%esi),%edi
 PC (0x08131ef9) ok
 source "0x11(%esi)" (0x00000011) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: onboard
StacktraceTop:
 PyUnicode_InternFromString ()
 PyObject_GetAttrString ()
 PyObject_CallMethod ()
 ?? () from /usr/lib/python3/dist-packages/Onboard/osk.cpython-33m-i386-linux-gnu.so
 ?? () from /usr/lib/python3/dist-packages/Onboard/osk.cpython-33m-i386-linux-gnu.so
Title: onboard crashed with SIGSEGV in PyUnicode_InternFromString()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Svi Roussanoff (svi-roussanoff) 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 → Public
tags: removed: need-i386-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.