Bug 10838 - Google account not working in GNOME
Summary: Google account not working in GNOME
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-25 15:42 CEST by Götz Waschk
Modified: 2015-03-31 16:07 CEST (History)
1 user (show)

See Also:
Source RPM: gnome-online-accounts-3.6.3-1.mga3
CVE:
Status comment:


Attachments

Description Götz Waschk 2013-07-25 15:42:02 CEST
This is after the upgrade from Mga2. The google account doesn't work in evolution and also not in empathy. This is a regression. I have tried to delete and readd the google account. The authentication on the google page worked fine, but not the usage of the account.

The error in evolution is "Zeitüberschreitung wurde erreicht" (timeout reached).

The error in empathy is "Legitimierung fehlgeschlagen" (Authentication failed).
Götz Waschk 2013-07-25 15:42:27 CEST

Source RPM: (none) => gnome-online-accounts-3.6.3-1.mga3

Pascal Terjan 2013-07-25 15:47:38 CEST

CC: (none) => pterjan

Comment 1 Götz Waschk 2013-07-25 16:09:12 CEST
I am using Google's 2-factor authentication, so maybe it is related to this? https://bugzilla.gnome.org/show_bug.cgi?id=688364
Comment 2 Marja Van Waes 2015-03-31 16:07:09 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.