Bug 204165

Created attachment 36216 [details]
screen shot

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

(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.

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

(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.

You git log shows that the fix for this problem was part of the 0.9.3 release.

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.

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.

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.

Install "ca-certificates" package and see if it work.

(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

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

> 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.

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..)

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

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

*** Bug 218976 has been marked as a duplicate of this bug. ***

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.

I have the same issue on Ubuntu 11.04 x64
libgcal-0.9.6-1, KDE-4.7