onboard crashed with SIGSEGV in _atspi_dbus_handle_event()

Bug #1237707 reported by richard king
8
This bug affects 1 person
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
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
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_dbus_handle_event+789>: mov 0x50(%rdx),%rdi
 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_dbus_handle_event () from /usr/lib/x86_64-linux-gnu/libatspi.so.0
 _atspi_process_deferred_messages () from /usr/lib/x86_64-linux-gnu/libatspi.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
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: onboard crashed with SIGSEGV in _atspi_dbus_handle_event()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
richard king (richard-bonsu) wrote :
tags: removed: need-amd64-retrace
Revision history for this message
Seth Arnold (seth-arnold) wrote : Bug is not a security issue

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.

information type: Private Security → Public
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.