Bug 230201 - error when trying export to picasa
Summary: error when trying export to picasa
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-WebService-Google (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-10 15:28 UTC by Bartek Pietrasiak
Modified: 2018-01-30 21:26 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In: 1.3.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bartek Pietrasiak 2010-03-10 15:28:29 UTC
Version:           1099942 (using KDE 4.3.4)
OS:                Linux
Installed from:    Fedora RPMs

"Picasaweb Call Failed: Failed to fetch photo-set list" when @gmail.com in user id.
Comment 1 caulier.gilles 2010-03-10 15:31:10 UTC
which kipi-plugins version you use ?

I think it's fixed in current implementation from svn (next 1.2.0)

Gilles Caulier
Comment 2 Bartek Pietrasiak 2010-03-10 16:39:06 UTC
Qt: 4.5.3
KDE: 4.3.4 (KDE 4.3.4)
digiKam: 1.2.0 (rev.: 1099942)
Comment 3 Jens Mueller 2010-03-10 18:50:11 UTC
That's all in all a litlle bit confusing.

First of all, providing your google username without '@gmail.com' will let you log in. It works this way at least since I use it (Jan 2010).

Looking for the reason why you can not login with your full gmail address shows the following:
- it let you log in through the auth process and give you a normal looking auth response back
- submit a picasaweb api call using this auth response will result in the error "Unable to find user with email xxx%40gmail.com@gmail.com" - it looks like that google append a second '@gmail.com'
- walking through the revision tree shows that jaiva removed the appending of '@gmail.com' here: http://websvn.kde.org/trunk/extragear/graphics/kipi-plugins/picasawebexport/picasawebtalker.cpp?r1=881009&r2=884771 - interesting
Comment 4 Bartek Pietrasiak 2010-03-10 23:33:57 UTC
"Target request failed: Target is not responding (timed out)" - this you will get with a brand new google account on which you haven't "actived" picasa web (== used at least once via web).

BTW, funny that web services give a response with a plain text ;)
Comment 5 Jens Mueller 2010-04-08 17:45:40 UTC
*** Bug 233727 has been marked as a duplicate of this bug. ***
Comment 6 Philippe ROUBACH 2010-04-11 20:40:15 UTC
sumup :
from picasawebexport
- i can't connect with
. <mailbox>@<site of my isp> (that was working)
. <gmailbox>@gmail.com (that was working)
. my picasaweb alias

- i can connect with
. <gmailbox> from <gmailbox>@gmail.com

even in this case the link "picasweb"  in picasawebexport is not good
because it is not a rule that <gmailbox> is the name of my picasweb site at picasaweb.google.com
Comment 7 Jens Mueller 2010-04-12 20:50:33 UTC
SVN commit 1114104 by jmueller:

problem found: picasaweb do not like percentencodings in urls, what about standards?

BUGS: 230201

 M  +2 -1      NEWS  
 M  +10 -4     picasawebexport/picasawebtalker.cpp  
 M  +4 -3      picasawebexport/picasawebwindow.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1114104
Comment 8 Jens Mueller 2010-04-15 07:44:53 UTC
*** Bug 234395 has been marked as a duplicate of this bug. ***
Comment 9 Ian Hubbertz 2010-04-15 09:23:03 UTC
Hi! The fix is working for me (I already did the same yesterday evening), but I think there still may be problems left for some users.

The problem is not the percent-encoding, it is that the URL is encoded twice.

So the "@" ist quoted to "%40" which is then quoted to "%2540", so Google decodes "%40".

So first I thought, maybe KUrl quotes itself, but this may not the be the case:

With the current solution no quoting is done at all (I had a look at wireshark-capture).

So maybe, KUrl quotes "%" automatically, but accepts "@"?
Comment 10 Jens Mueller 2010-04-17 09:12:26 UTC
Ian, you are right here. Adding a path to a KUrl which contains a '@' is not encoded to percentencoding. But adding a path which contains a '%' then the '%' is encoded to percentencoding. So you can't really add correct a path with a '@'. Is this a kdelibs-bug?

Jens
Comment 11 Jens Mueller 2010-04-17 09:12:27 UTC
Ian, you are right here. Adding a path to a KUrl which contains a '@' is not encoded to percentencoding. But adding a path which contains a '%' then the '%' is encoded to percentencoding. So you can't really add correct a path with a '@'. Is this a kdelibs-bug?

Jens
Comment 12 caulier.gilles 2010-04-17 11:39:59 UTC
Jens, 

Ask to #kde-devel IRC chanel to be sure if it's KDELibs problem.

Gilles Caulier
Comment 13 Jens Mueller 2010-04-22 21:42:59 UTC
*** Bug 235026 has been marked as a duplicate of this bug. ***
Comment 14 Jens Mueller 2010-05-25 20:08:47 UTC
*** Bug 238766 has been marked as a duplicate of this bug. ***
Comment 15 Jens Mueller 2010-08-25 21:53:03 UTC
*** Bug 244980 has been marked as a duplicate of this bug. ***
Comment 16 Jens Mueller 2010-08-25 21:59:30 UTC
*** Bug 241671 has been marked as a duplicate of this bug. ***