Description of problem: When using an institution gmail account (ending with berkeley.edu but served by gmail.com) A few days after the initial authorization, evolution refuses sending emails. After closing and restarting it keeps asking for google authorization on emails, contacts, calenders and everything in a loop, with errors like this in the console: ** Message: received an invalid or unencryptable secret ** Message: received an invalid or unencryptable secret ** Message: received an invalid or unencryptable secret ** Message: Remote error from secret service: org.freedesktop.DBus.Error.Failed: Couldn't create item: The secret was transferred or encrypted in an invalid way. (evolution:12414): e-data-server-ui-WARNING **: credentials_prompter_store_credentials_cb: Failed to store source credentials: Couldn't create item: The secret was transferred or encrypted in an invalid way. ** Message: received an invalid or unencryptable secret ** Message: received an invalid or unencryptable secret ** Message: received an invalid or unencryptable secret Version-Release number of selected component (if applicable): 3.20.5 How reproducible: I haven't reproduced this. It occured two days after my initial upgrade to F24. I shall be able to observe this again next monday. Steps to Reproduce: 1. Set up evolution with a gmail account. 2. authorize for the first time. 3. Keep evolution running and wait for two days. 4. try to send an email. It hangs. 5. close evolution and relaunch 6. prompt to authorize evolution inspite it is already authroized on google's management console. Actual results: Expected results: It shall work. This is a very disruptive bug. It essentially makes Evolution unusable. Additional info: If I remove the entry on 'Evolution Data Source[Google]' in Gnome keyring manually, and relaunch evolution, it asks me to authorize and I am able to send emails. Looks like the old authorization has expired, yet it is not correctly renewed by evolution data server. (I suspect this because there is an expiration time in the keyring entry) How is the authorization token renewed? How long does evolution request for the entry? Which library does evolution use to handle google authentication? Could it be a bug over there? Is there a way to reenable the old password based authentication?
This could be: https://bugzilla.gnome.org/show_bug.cgi?id=771547 I will installed the -4.4 version of RPM and test.
Thanks for a bug report. You can face two things, one is the upstream bug report which you referenced, for which I'm currently building F24 official update, the other is related to these messages: > Message: received an invalid or unencryptable secret which comes from libsecret or gnome-keyring-daemon. It's https://bugzilla.gnome.org/show_bug.cgi?id=681815 and eventually also https://bugzilla.gnome.org/show_bug.cgi?id=714128, which points to https://bugzilla.gnome.org/show_bug.cgi?id=769666.
Thanks for the information. I will resume email hoarding tomorrow, so I'll report back how bad the keyring bug affects evolution.
evolution-data-server-3.20.5-5.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-2c3c63bada
evolution-data-server-3.20.5-5.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.