onboard crashed with SIGSEGV in PyObject_GetAttrString()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
onboard (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Calling Onboard settings from the built-in Onboard keyboard shortcut or from the main menu when the Onboard keyboard is running causes the Onboard keyboard to crash but does not crash the Onboard settings menu.
Onboard keyboard otherwise functions correctly. It only crashes when the settings are called either from the built in Onboard shortcut or the main menu.
Further to above.
In 13.04 calling the Onboard settings from the main menu without the Onboard keyboard itself being open, resulted in any settings not being saved.
The work around was to open the Onboard settings menu directly from the built in Onboard keyboard shortcut.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: onboard 0.99.0~
ProcVersionSign
Uname: Linux 3.10.0-2-generic x86_64
NonfreeKernelMo
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
Date: Sat Jul 13 13:21:04 2013
ExecutablePath: /usr/bin/onboard
InstallationDate: Installed on 2013-07-07 (5 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130702)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/bin/onboard
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_GB.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: No upgrade log present (probably fresh install)
UserGroups: adm audio backup cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video
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.