Bug 330978 - akonadi google contact not connected to google server,new contact not synced
Summary: akonadi google contact not connected to google server,new contact not synced
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Google Resource (show other bugs)
Version: 4.12
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-10 10:45 UTC by Philippe ROUBACH
Modified: 2016-12-23 13:43 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe ROUBACH 2014-02-10 10:45:04 UTC
select in kde proxy settings "use manual proxy settings"
don't fill the fields
then
restart system
then
open a kde session
then
launch kontact
akonadi google contact is not connected to google server because request via proxy fails
then
in kaddressbook in google addressbook create a new contact
then
go to mail.google.com then got to "contacts"
then
no new contact in gmail contacts
then
in kde proxy settings set "use system proxy setings"
then
ask a sync of google contacts in kaddressbook
when akonadi google contact asks for you to connect then do what it is needed 
then
go to mail.google.com then go to "contacts"
no new contact in gmail contacts
then
restart system open a kde session
launch kontact
we are at the step akonadi google contact is well connected to google server
then
go to mail.google.com then go to "contacts"
no new contact  in gmail contacts

then
create a second new contact
then
go to mail.google.com then go to "contacts"
this time the second new contact is in gmail contacts

résumé :
a new created contact when akonadi google contact is not connected to google server ,
even if akonadi google contact is connected again  will never synced to gmail contacts


Reproducible: Always
Comment 1 Denis Kurz 2016-09-24 20:45:36 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Philippe ROUBACH 2016-12-23 13:43:08 UTC
no more problem