Michi, the exception itself seems to be from https://bazaar.launchpad.net/~unity-team/unity-scopes- api/trunk/view/head:/src/scopes/internal/zmq_middleware/ZmqMiddleware.cpp and getting bubbled up through the bits.
Judging from the logs, what appears to happen is that the scope is started, and initialized, and we are then sent a Query(), and we have a Reply object to push results back through. At that point, the socket seems to get closed and the middleware is stopped. The scope then has results and tries to push(), but since the middleware is stopped, we get the exception from deep inside the scopes API. It's true that the scope itself could probably handle this very unexpected situation more gracefully on its own, but doing so won't really resolve the problem here of there not being any results, since the socket is closed and thus it's impossible for the scope to give any results back to the shell. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1645798 Title: No snaps appear in scope on Core 16 Status in Canonical System Image: Confirmed Status in Unity8 Session Snap: Confirmed Status in unity-api package in Ubuntu: Invalid Status in unity-scope-click package in Ubuntu: New Status in unity-scopes-api package in Ubuntu: In Progress Bug description: No snaps appear in scope on Core 16 whereas they do appear in unity8 snap on classic To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
