onboard crashed with SIGSEGV in PyObject_GetAttrString()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
onboard (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
when login into unity
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: onboard 0.99.0~
ProcVersionSign
Uname: Linux 3.10.0-2-generic x86_64
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
Date: Wed Jul 10 20:52:23 2013
ExecutablePath: /usr/bin/onboard
InstallationDate: Installed on 2012-08-01 (343 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111220)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/bin/onboard --not-show-in=GNOME
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x49bb7e <PyObject_
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_
PyObject_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: onboard crashed with SIGSEGV in PyObject_
UpgradeStatus: Upgraded to saucy on 2013-07-10 (0 days ago)
UserGroups: adm cdrom dialout 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 #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.