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

[James Ferguson]

No idea - just told it happened, didn't notice any symptoms. Presumably Unity respawned.

Just installed from daily, retaining old /home partition from 12.04

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity-scopes-runner 7.1.4+14.04.20140210-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 10 21:10:51 2014
Dependencies:

EcryptfsInUse: Yes
ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py
InstallationDate: Installed on 2014-03-11 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140310)
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: 0x7fc033b339ae: cmp %rbp,(%rax)
 PC (0x7fc033b339ae) ok
 source "%rbp" ok
 destination "(%rax)" (0x900000001) not located in a known VMA region (needed writable region)!
SegvReason: writing 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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.