If this is with boost 1.61, either the problem is still present in boost or, if the local files were messed up somehow, the exception would legitimately be raised because the locale definition is broken.
Comment #9 seems to indicate that the problem was fixed after regenerating the locale. In that case, the exception is perfectly legitimate, and there is no bug at all. If the locale info is broken, we can't parse essential configuration files in scopes-api, which prevents the runtime from being started. In that case, all scopes are inaccessible, period. If the problem indeed went away after regenerating the local info, there is no bug here. In that case, can you close as invalid please? -- 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/1615614 Title: dash is empty, scopes are missing Status in boost package in Ubuntu: New Status in unity-scopes-api package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 16.10 dash is empty, scopes are missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boost/+bug/1615614/+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
