onboard crashed with SIGSEGV in _atspi_dbus_handle_event()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Onboard |
New
|
Undecided
|
Unassigned | ||
onboard (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Onboard just crushed. This has been the 4th time it has crashed on me. Nothing special ... just kept crushing. business as usual.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: onboard 0.99.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Oct 10 02:48:10 2013
ExecutablePath: /usr/bin/onboard
InstallationDate: Installed on 2013-10-08 (1 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
ProcCmdline: /usr/bin/python3.3 /usr/bin/onboard --not-show-in=GNOME
SegvAnalysis:
Segfault happened at: 0x7f346e235d05 <_atspi_
PC (0x7f346e235d05) ok
source "0x50(%rdx)" (0x00000050) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: onboard
StacktraceTop:
_atspi_
_atspi_
g_main_
?? () from /lib/x86_
g_main_loop_run () from /lib/x86_
Title: onboard crashed with SIGSEGV in _atspi_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
tags: | removed: need-amd64-retrace |
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.