Bug 1326634 - GOA configured Google calendar not using OAuth2
Summary: GOA configured Google calendar not using OAuth2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution-data-server
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Milan Crha
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-13 09:14 UTC by Vladimir Benes
Modified: 2016-11-04 00:25 UTC (History)
2 users (show)

Fixed In Version: evolution-data-server-3.12.11-30.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 00:25:46 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2206 0 normal SHIPPED_LIVE evolution-data-server bug fix update 2016-11-03 13:23:16 UTC

Description Vladimir Benes 2016-04-13 09:14:42 UTC 
Description of problem:
there is an issue of connection to google calendar via GOA. It says that it doesn't have password from time to time. Should be related to:
https://bugzilla.gnome.org/show_bug.cgi?id=728496

Version-Release number of selected component (if applicable):
evolution-data-server-3.12.11-28.el7.x86_64

How reproducible:
sometimes
Comment 1 Milan Crha 2016-04-13 14:04:25 UTC 
I fixed this for evolution-data-server-3.12.11-30.el7 with a similar change as this one upstream [1].

[1] https://git.gnome.org/browse/evolution-data-server/commit/?id=4b14c7e
Comment 5 errata-xmlrpc 2016-11-04 00:25:46 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2206.html
Note You need to log in before you can comment on or make changes to this bug.