scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()

Bug #1578640 reported by Fernando Fernandez
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libunity (Ubuntu)
New
Undecided
Unassigned

Bug Description

I think this was because I was installing Squirrel SQL at the time

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 5 14:23:40 2016
Dependencies:

ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
InstallationDate: Installed on 2014-09-07 (605 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
InterpreterPath: /usr/bin/python3.4
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s files/gdrive.scope
SegvAnalysis:
 Segfault happened at: 0x7f6f8250fc8e: cmp (%rax),%rbp
 PC (0x7f6f8250fc8e) ok
 source "(%rax)" (0x400000000) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: libunity
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libsignon-glib.so.1
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: scope-runner-dbus.py crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: Upgraded to wily on 2015-11-27 (159 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Fernando Fernandez (ferdez) 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 #1194465, 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-amd64-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.