Comment 22 for bug 1645798

It looks like click-scope is the only scope that is failing. Queries to the music scope work just fine, as do queries to remote scopes (via smartscopesproxy). All these scopes run the exact same code in the runtime.

I have no idea what exactly is going wrong, but I strongly suspect that it is in click scope or one of the dependencies it calls into.

Note that the messages about the closed socket may well be consequential if a thread that wasn't created by the scopes run time throws. (If click-scope uses QtDBus, possibly an exception could escape from one of its threads? Or maybe net-cpp underneath or some such?)

It would be really useful to have some trace from click scope to see what it is up to when it receives a query.

Also, it looks like I'm not getting any core dumps in the unity8-session. Is there a way to enable those? It might give us a chance at getting a stack trace from the click-scope.