After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 759187 - evolution-source-registery needs a restart to pick newly activated uoa accounts
evolution-source-registery needs a restart to pick newly activated uoa accounts
Status: RESOLVED WONTFIX
Product: evolution-data-server
Classification: Platform
Component: Calendar
3.18.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2015-12-08 16:24 UTC by Sebastien Bacher
Modified: 2017-08-31 14:56 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastien Bacher 2015-12-08 16:24:42 UTC
Using e-d-s 3.18.2 with ubuntu-online-account

- 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
Comment 1 Milan Crha 2016-01-28 14:49:11 UTC
(In reply to Sebastien Bacher from comment #0)
> 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

Thanks for a bug report. I agree with the above, if there is no way to know that conditions for certain accounts changed, then the evolution-data-server cannot do anything about it.

Do you have filled a bug report against the signon, please? If no, could you do that and give a link here, please? Once it'll be done the evolution-data-server can be updated to use it and work with it. Thanks in advance.
Comment 2 Sebastien Bacher 2016-02-08 14:27:23 UTC
There is a bug on launchpad assigned to mardy, https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1523985 ... maybe it should be reported against the uoa stack as well though?
Comment 3 Milan Crha 2017-08-31 14:56:36 UTC
I've been told that UOA is (going to be) deprecated, then it doesn't make much sense to spend time on this.