Michi, in that scope-registry.log you pastebinned, it looks like the ZMQ socket is getting closed/removed in the middle of calling Query in the scope:
(process:2658): ubuntu-app-launch-DEBUG: Initialized Click DB [2016-12-09 05:20:22.797] ERROR: clickscope: ObjectAdapter: error unmarshaling request header (id: , adapter: clickscope-c, op: ): ZmqReceiver::receive(): socket was closed <messages from UAL as we query for apps> [2016-12-09 05:20:22.807] ERROR: clickscope: ReplyImpl::error(): unity::scopes::MiddlewareException: Cannot invoke operations while middleware is stopped I'm not sure why this would happen, and I didn't realize we need to handle exceptions in the middleware, within the scope itself. Any idea why the socket would be getting destroyed from the other end? This seems to be why the scope is blank. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645798 Title: No snaps appear in scope on Core 16 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
