evolution-source-registery needs a restart to pick newly activated uoa accounts

Bug #1523985 reported by Sebastien Bacher
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution-data-server
Won't Fix
Medium
evolution-data-server (Ubuntu)
Triaged
High
Alberto Mardegan
Xenial
Triaged
High
Alberto Mardegan

Bug Description

Using current xenial version
- go to the uoa settings
- add a google account

- > you get a notification that there is an auth issue (that's a weird workflow but needed because the application needs to auth but e-d-s can't do UI prompting)

- auth e-d-s in the settings

-> the new account should be active/listed in the indicator or gnome-calendar but is not

The issue is probably that e-d-s connect to the "account-created" signal on a AgManager object and adds the account correctly, but at this point the authentification/confirmation is not done yet so the account fails to active, and there is no following callback after the authentification is done.

It seems that AgManager doesn't provide an appropriate signal that can be used there so some work might be needed on the signon side

Changed in evolution-data-server (Ubuntu):
importance: Undecided → High
status: New → Triaged
assignee: nobody → Alberto Mardegan (mardy)
tags: added: rls-x-incoming
Changed in evolution-data-server:
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in evolution-data-server:
status: Confirmed → Incomplete
Iain Lane (laney)
tags: removed: rls-x-incoming
Changed in evolution-data-server:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.