You can run the scope with U1_DEBUG=1 set, and it will spew more debug info.
I doubt it's threads. We're not using QtDBus here really. The ubuntu- download-manager code does use it, but we're no longer really using it in the scope, only the client object gets created on startup, and then never used. There is an MP to remove the dependency on ubuntu-download- manager and libclick in https://bileto.ubuntu.com/#/ticket/2306, and I asked Michael to build a snap with it and try, but it was still failing for him with that. I guess you'd need to run the scope manually under gdb to be able to get a trace, but I can't tell you how to do that on an all snaps system, unfortunately. -- 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 : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
