/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:unity::scopes::Variant::get_string

According to the trace, the problem seems to be caused by network failures, in index.cpp near line 214:

                    qDebug() << "Cannot get package details due to network error";
                    callback(PackageDetails(), click::Index::Error::NetworkError);

It seems that some of the new fields in the empty PackageDetails is not initialized properly and it's failing when the scope is trying to use it with unity::scopes::Variant::get_string.

This crash has not happened again the past month, so it looks like it's no longer valid.

Apparently this still happens! See https://errors.ubuntu.com/?package=unity-scopes-api&period=month

Re-opening because this is still happening:

https://errors.ubuntu.com/problem/5201e937d07d123ac9659e077a9a68de677ddfda

__terminate:std::terminate:__cxxabiv1::__cxa_throw:unity::scopes::Variant::get_string

That's a dead give-away: it looks like the code is trying to pull a string out of a Variant that doesn't contain a string, and the exception that is thrown because of this isn't caught, taking the program to terminate().

This bug was fixed in the package unity-scope-click - 0.1.1+15.04.20150114-0ubuntu1

---------------
unity-scope-click (0.1.1+15.04.20150114-0ubuntu1) vivid; urgency=low

  [ Alejandro J. Cura ]
  * Check Variant for null value (LP: #1357143)
 -- Ubuntu daily release <email address hidden> Wed, 14 Jan 2015 19:27:00 +0000

This bug was fixed in the package unity-scope-click - 0.1.1+15.04.20150119~rtm-0ubuntu1

---------------
unity-scope-click (0.1.1+15.04.20150119~rtm-0ubuntu1) 14.09; urgency=low

  [ Alejandro J. Cura ]
  * Check Variant for null value (LP: #1357143)
 -- Ubuntu daily release <email address hidden> Mon, 19 Jan 2015 13:09:06 +0000