Bug 204165 - akonadi googledata resources do not work
Summary: akonadi googledata resources do not work
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: GoogleData Resource (show other bugs)
Version: 4.3
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Adenilson Cavalcanti
URL:
Keywords:
: 218976 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-08-17 13:34 UTC by Ritesh Raj Sarraf
Modified: 2011-10-25 20:05 UTC (History)
10 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
screen shot (128.37 KB, image/jpeg)
2009-08-17 13:35 UTC, Ritesh Raj Sarraf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ritesh Raj Sarraf 2009-08-17 13:34:38 UTC
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    Debian testing/unstable Packages

When creating and feeding Akonadi Google Data resources with credentials, nothing happens.

The agent keeps complaining of "Invalid Password".
Comment 1 Ritesh Raj Sarraf 2009-08-17 13:35:19 UTC
Created attachment 36216 [details]
screen shot
Comment 2 Adenilson Cavalcanti 2009-08-24 18:26:02 UTC
Dear friend

Are you using special characters (e.g. {, [, %, &, ^, etc) in your password?

If so, please try again but this time using libgcal from git repository:
http://repo.or.cz/w/libgcal.git
Comment 3 Ritesh Raj Sarraf 2009-08-24 20:21:28 UTC
(In reply to comment #2)
> Are you using special characters (e.g. {, [, %, &, ^, etc) in your password?
>
Yes, I am. :-)
We need to keep passwords strong.
 
> If so, please try again but this time using libgcal from git repository:
> http://repo.or.cz/w/libgcal.git
Please provide me a patch.
I'm running version 0.9.2 from Debian. If you provide me a patch, I can rebuild the debian package that I'm using, with your patch applied.
Comment 4 Adenilson Cavalcanti 2009-08-26 13:32:33 UTC
If you can't download and compile libgcal from git repository, wait for Debian packagers to do that (I will pretty soon release a new version of libgcal).


Adenilson
Comment 5 Ritesh Raj Sarraf 2009-09-06 19:30:53 UTC
(In reply to comment #4)
> If you can't download and compile libgcal from git repository, wait for Debian
> packagers to do that (I will pretty soon release a new version of libgcal).

FYI,
Just tried 0.9.3 and the problem persists.
Comment 6 Ritesh Raj Sarraf 2009-09-06 19:32:59 UTC
You git log shows that the fix for this problem was part of the 0.9.3 release.
Comment 7 Adenilson Cavalcanti 2009-09-07 01:06:25 UTC
Are you sure that you have:

a) Removed older libgcal package from your system (apt-get remove)

b) exported LD_LIBRARY_PATH to the place where you installed libgcal

c) If you are behind a proxy, set it properly in system settings

I have fixed the library based in a patch of a user with precisely this problem and it worked fine.
Comment 8 Ritesh Raj Sarraf 2009-09-07 06:32:56 UTC
rrs@champaran:/tmp/kde-rrs $ apt-cache policy libgcal0
libgcal0:
  Installed: 0.9.3-1
  Candidate: 0.9.3-1
  Version table:
 *** 0.9.3-1 0
        990 http://ftp.debian.org testing/main Packages
        500 http://ftp.debian.org unstable/main Packages
        990 http://mirrors.kernel.org testing/main Packages
        500 http://mirrors.kernel.org unstable/main Packages
        100 /var/lib/dpkg/status


I don't have multiple versions of the same library. So I don't need the path manually.
Doing an ldd points to the correct libgcal library which when apt-cached shows the above version result.

Do you think there could be a leftover stale configuration ? But I had tried to create new akonadi googledata resource.
Comment 9 Andreas Jacob 2009-09-10 20:50:44 UTC
Exactly the same situation here. I'm also using debian sid and getting the "invalid password" error.

But the "invalid password" irritated me in some way, so i used wireshark to get closer look. And for me it seems a problem with TLS. When starting the akonadi plugins, the system tries to resolve www.l.google.com. In the next step one of the dns provided IPs is used to establish a TLS secured connection. But some packets later, there is a client side TLS error which sayes "Decrypt Error" (TLS error number: 51).
So i tried to manually view the address (https://www.l.google.com) in a normal browser. Et voila, it says, that the certificate presented by the google server is only valid for google.com and *.google.com (ssl_error_bad_cert_domain). IMHO www.l.google.com should be matched by *.google.com. But whether konqueror nor firefox thinks so. 
So there are two possibilities. It's a bug in the ssl/tls handling, or it's a google certificate fault. But then all users must have these problems, not only the debian ones. 

Hope these helps a bit in hunting for an solution.

Cheers Andreas
ps: I'm a german user of gmail an so i use username@googlemail.com as my username and my password contains special chars.
Comment 10 Adenilson Cavalcanti 2009-09-10 21:10:05 UTC
Install "ca-certificates" package and see if it work.
Comment 11 Andreas Jacob 2009-09-10 21:16:23 UTC
(In reply to comment #10)
> Install "ca-certificates" package and see if it work.

It's already installed, and additionally i added the certificate from "https://www.l.google.com" manually to the list. Some behavior. 

Cheers Andreas
Comment 12 Andreas Jacob 2009-09-11 00:29:17 UTC
Oh damn
I must apologize. I've had an additional, self compiled and earlier version of libgcal in /usr/local/lib/. After manually removing these old version, the "invalid password" error went away.
Hope you can forgive me. ;-)

Cheers Andreas
Comment 13 Ritesh Raj Sarraf 2009-10-18 08:42:47 UTC
> Do you think there could be a leftover stale configuration ? But I had tried to
> create new akonadi googledata resource.

This must have been some stale config issue in my user account somewhere. After doing a lot of clean-ups, the googledata resource works. Thanks.

But I am not sure which setting it was. I realized that it was a stale config issue somewhere because on another account, it was configured easily. So I went in the hunt to clean (remove) all akonadi stuff and retry.
Comment 14 dex 2009-10-28 23:14:43 UTC
I have exactly the same behaviour now in kde 4.3.2 + akonadi google calendar compiled from source.

How can I check if this is related to ssl problems or me not using the right version of libgcal (I'm using 0.9.3 release at the moment..)
Comment 15 Rein 2010-01-18 18:41:26 UTC
Same problem here, well, not exactly, it works for a while, and then after a few days I get: 
"Not yet authenticated for use of Google calendar"
Re-entering the password does nothing. Removing and than adding a new akonadi_gcal_resource_* fixes the problem for some time.

maybe related: https://bugs.kde.org/show_bug.cgi?id=218976

Using: Linux 2.6.30-2-686 GNU/Linux Debian Squeeze/sid
akonadi-kde-resource-googledata 1.0.1-1 akonadi-server 1.2.1-1+b1 libgcal0
0.9.3-1 kdelibs5 4:4.3.4-1 kontact 4:4.3.4-1 kaddressbook 4:4.3.4-1 libqtcore4
4:4.5.3-4
Comment 16 Rein 2010-02-17 13:49:17 UTC
my problem seems to be resolved.

I deleted my akonadi config files, and re-entered my info. Also upgraded to kernel 2.6.32

Linux 2.6.32-trunk-686 GNU/Linux Debian Squeeze/sid
akonadi-kde-resource-googledata      1.0.1-1
akonadi-server                       1.2.1-1+b1
kdepim-runtime                       4:4.3.4-1
kdepim-runtime-dbg                   4:4.3.4-1
libakonadiprivate1                   1.2.1-1+b1
libgcal0                             0.9.3-1
Comment 17 Tobias Koenig 2010-08-02 19:00:17 UTC
*** Bug 218976 has been marked as a duplicate of this bug. ***
Comment 18 Dion Moult 2011-01-31 09:43:06 UTC
Followed all of the potential "fixes" in this thread and also using libgcal 0.9.6. Still doesn't work for me and gives "Invalid Password" error. Kontact 2 (KDEPIM 4.6) and KDE 4.6.
Comment 19 Alexander Zaitsev 2011-08-01 09:33:10 UTC
I have the same issue on Ubuntu 11.04 x64
libgcal-0.9.6-1, KDE-4.7