online-accounts-service delivers no reply if trust session can't be setup

Bug #1420847 reported by Alberto Mardegan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Online Accounts setup for Ubuntu Touch
High
Alberto Mardegan

Bug Description

If the trust session cannot be setup for a SignOnUI request, online-accounts-service doesn't return an error. This results in signond (and therefore the client) keeping waiting, and potentially blocking future requests on the same account.

Related branches

Revision history for this message
Alberto Mardegan (mardy) wrote :

Output from online-accounts-service:

utils.cpp 49 apparmorProfileOfPeer App ID: "unconfined"
request-manager.cpp 113 runQueue Head: OnlineAccountsUi::Request(0x1d33640)
Invalid prompt session: /build/buildd/mir-0.10.0+15.04.20150107.2/src/server/scene/prompt_session_manager_impl.cpp(137): Throw in function virtual std::shared_ptr<mir::scene::PromptSession> mir::scene::PromptSessionManagerImpl::start_prompt_session_for(const std::shared_ptr<mir::scene::Session>&, const mir::scene::PromptSessionCreationParameters&) const
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_errorEEEE
std::exception::what: Could not identify application session

Invalid prompt session: /build/buildd/mir-0.10.0+15.04.20150107.2/src/server/scene/prompt_session_manager_impl.cpp(137): Throw in function virtual std::shared_ptr<mir::scene::PromptSession> mir::scene::PromptSessionManagerImpl::start_prompt_session_for(const std::shared_ptr<mir::scene::Session>&, const mir::scene::PromptSessionCreationParameters&) const
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_errorEEEE
std::exception::what: Could not identify application session

Couldn't setup prompt session

Alberto Mardegan (mardy)
Changed in ubuntu-system-settings-online-accounts:
assignee: nobody → Alberto Mardegan (mardy)
importance: Undecided → High
status: New → In Progress
Revision history for this message
David Barth (dbarth) wrote :

Technically this is the same bug as #1420934 which is the user facing part of it, which has been approved for landing.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers