So I continue to propose that this is not due to the Today scope. There are three exceptions in the scope-registry log files, here are some comments on them.
== 1) scope-registrylog.3 has: Location object not found: "unity::scopes::NotFoundException: SearchMetadata::location() (name = location)" This is the normal log result by Day Scope when location data is disabled. The exception is caught, and the scope responds appropriately. This log message should be modified to indicate the exception is handled and it is a normal condition. == 2&3) scope-registrylog.1 has: unity::ResourceException: /build/buildd/net-cpp-1.2.0+15.04.20150415.2/src/core/net/http/impl/curl/request.h@220 - operator(): Timeout was reached query complete, status: error ReplyObject::push(VariantMap): unity::InvalidArgumentException: CategorisedResult::set_category(): Category must not be null 522 [2016-01-29 00:01:19.303367] ERROR: unity-scope-nearby: ReplyObject::push(): ReplyObject::push(VariantMap): unity::InvalidArgumentException: CategorisedResult::set_category(): Category must not be nul This one is a concern since a result must have a non-null category. But this in the nearby-scope (or quite possibly one of the child scopes that give it data), not the today scope. It appears to immediately follow a network error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539446 Title: Today scope hangs-on after OTA9 update To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
