Your message dated Mon, 29 Feb 2016 22:04:43 +1000
with message-id <[email protected]>
and subject line Closed upstream
has caused the Debian Bug report #814870,
regarding evolution: google accounts not working
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
814870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814870
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: evolution
Version: 3.18.3-1
Severity: normal
Tags: upstream
Details entered into evolution bugzilla:
I've entered my Google details into gnome-online-accounts. The mail /
calendar / address book appeared and worked immediately, but after a
restart Evolution said: "Failed to obtain an access token for
'[email protected]': Failed to retrieve credentials from the
keyring" and has remained that way ever since.
I've tried deleting and recreating the account in gnone-online-accounts,
but it has no effect.
Running on Debian Stretch, evolution_3.18.3-1_amd64
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages evolution depends on:
ii dbus 1.10.6-1
ii debconf [debconf-2.0] 1.5.58
ii evolution-common 3.18.3-1
ii evolution-data-server 3.18.3-1
ii libc6 2.21-7
ii libcamel-1.2-54 3.18.3-1
ii libclutter-gtk-1.0-0 1.6.6-1
ii libecal-1.2-19 3.18.3-1
ii libedataserver-1.2-21 3.18.3-1
ii libevolution 3.18.3-1
ii libglib2.0-0 2.46.2-3
ii libgtk-3-0 3.18.7-1
ii libical1a 1.0.1-0.1
ii libnotify4 0.7.6-2
ii libsoup2.4-1 2.52.2-1
ii libwebkitgtk-3.0-0 2.4.9-3
ii libxml2 2.9.3+dfsg1-1
ii psmisc 22.21-2.1+b1
Versions of packages evolution recommends:
ii bogofilter 1.2.4+dfsg1-4
ii evolution-plugins 3.18.3-1
ii yelp 3.16.1-1
Versions of packages evolution suggests:
pn evolution-ews <none>
pn evolution-plugins-experimental <none>
ii gnupg 1.4.20-1
ii network-manager 1.0.10-2+b1
-- no debconf information
--- End Message ---
--- Begin Message ---
The message I closed this with upstream is:
> The problem, whatever it was, has gone. The Google accounts have
> worked every boot for several days now. Maybe it went because Debian
> upgraded a package which is something that happens daily on Debian
> testing.
>
> FWIIW, I now believe the problem is gnome-keyring isn't being
> unlocked when I logged in despite the password being the same as my
> login password and the relevant entries being present in
> /etc/pam.d. (I use lightdm.)
>
> When it wasn't working gcr asked for the password to unlock the
> keyring when evolution started which meant evolution could not get to
> any of my email passwords during startup. It happily continued
> normally once the keyring password was entered for all the normal
> email accounts, but not for the GOA account which remained
> permanently disabled in evolution for the remainder of the login
> session. It remained disabled even if I restarted evolution.
>
> Now something is triggering gcr to ask for the keyring password as
> soon as I log in, which means when evolution starts it is already
> unlocked. Evolution is then happy.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
