Bug 150979 - Picasa Export tool does not work
Summary: Picasa Export tool does not work
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-WebService-Google (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-18 15:36 UTC by krienke
Modified: 2018-03-23 12:09 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In: 0.1.0


Attachments
Illustration of album names fetching problem (51.09 KB, image/png)
2008-01-25 09:12 UTC, Darek Borkowski
Details
My fix for basic functionality (157.72 KB, patch)
2008-04-28 03:35 UTC, Alexander Drozdov
Details
QObject errors seen on console during failed export from Digikam to Picasa (3.87 KB, text/plain)
2008-05-25 02:01 UTC, x3ri7yz02
Details

Note You need to log in before you can comment on or make changes to this bug.
Description krienke 2007-10-18 15:36:05 UTC
Version:           0.1.5beta1 (using KDE KDE 3.5.7)
Installed from:    SuSE RPMs
Compiler:          gcc 4.2.1 
OS:                Linux

I run digikam 0.9.3 beta1 as well as kipi-plugins 0.1.5-beta1 .  I would like 
to use the Picasa plugin. I can open the plugins dialog and I can download a 
list of Picasa-albums but I cannot create new albums via the plugin and most important, I cannot upload any photo to picasa web. I select a photo and say "start upload". Then a progress-bar appears but this progress-bar will 
never show any progress. I looked at the network traffic and I can see that there is some traffic for about 5 sec to td-in-f91.google.com but then this traffic stopps. I already disabled my firewall to exclude this as a reason.

I do not have any problems logging in and loading up photos to picasa web via 
http://picasaweb.google.de/  .
Comment 1 caulier.gilles 2007-10-18 16:01:56 UTC
Vardhman,

Are you few comments about this file ?

Gilles
Comment 2 Vardhman 2007-10-18 17:37:35 UTC
I could verify that new album issue. My guess is that the list of Albums returned by the server doesn't list empty albums or there might be issue in the way I parse  the returned data.

As far as uploading the photos is concerned I have tried uploading the photos many times but all my trial used login for picasaweb.google.com, I can't immediately think if the .com and .de may be working differently.
Comment 3 krienke 2007-10-19 08:50:08 UTC
Am Donnerstag, 18. Oktober 2007 17:37:36 schrieb Vardhman:
> ------- I could verify that new album issue. My guess is that the list of
> Albums returned by the server doesn't list empty albums or there might be
> issue in the way I parse  the returned data.
>
> As far as uploading the photos is concerned I have tried uploading the
> photos many times but all my trial used login for picasaweb.google.com, I
> can't immediately think if the .com and .de may be working differently.


Well after all I have no choice of selecting where the plugin does connect to 
(.com or .de). Perhaps this causes the trouble. On the other hand I tried to 
logon to picasaweb.google.com  with my browser which worked fine for me. I 
had no problems uploading a photo via the picasa webinterface using 
http://picasaweb.google.com . 

I just tried to export another photo on my suse10.3 system  and again the 
progress bar does not show any progress. Using netstat --inet I see that 
there is a connection:

bliss:~ # netstat --inet -n
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 141.26.64.65:38409      209.85.167.91:80        TIME_WAIT

I tried to telnet this host on port 80 and entered a get:

# telnet  209.85.167.91 80
Connected to 209.85.167.91.
Escape character is '^]'.
get


<html><head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>400 Bad Request</title>
<style><!--
...

So the connection works but the plugins connection remains in TIME_WAIT 
status.  Strange.

Rainer
Comment 4 krienke 2007-11-08 14:36:48 UTC
I had another idea to track the bug. Perhaps this info helps to isolate the problem. I started a photo upload and used wireshark to show whats going on. The host where data were uploaded to is 72.14.255.91 (td-in-f91.google.com). Using the follow tcp stream Method in wireshark I can see the following:

------start --------------------------------------------------------------------
POST /data/feed/api/user/krienke@uni-koblenz.de/album/Test HTTP/1.1
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.6) Gecko/20040113
Pragma: no-cache
Cache-control: no-cache
Accept: text/html, image/jpeg, image/png, text/*, image/*, */*
Accept-Encoding: x-gzip, x-deflate, gzip, deflate
Accept-Charset: iso-8859-15, utf-8;q=0.5, *;q=0.5
Accept-Language: de, en
Host: www.picasaweb.google.com
Cookie: rememberme=false; PREF=ID=b0045a98edc4465c:TM=1185257727:LM=1185257727:S=sUkSdTkFUMEGk0Ul
Authorization: GoogleLogin auth=
Content-Type: multipart/related; boundary=----------rcL6ZwtjEeQEUrxtcTZ8hC1MaxC2ITI73bBcX5KkjkyBat4AMdI1pIN
Connection: Keep-Alive
Content-Length: 134960

------------rcL6ZwtjEeQEUrxtcTZ8hC1MaxC2ITI73bBcX5KkjkyBat4AMdI1pIN
Content-Disposition: form-data; name="test"
Content-Type: application/atom+xml
Mime-version: 1.0 
Content-Length: 207

<entry xmlns='http://www.w3.org/2005/Atom'><title>dsc_3256.jpg</title><summary></summary><category scheme="http://schemas.google.com/g/2005#kind" term="http://schemas.google.com/photos/2007#photo" /></entry>
------------rcL6ZwtjEeQEUrxtcTZ8hC1MaxC2ITI73bBcX5KkjkyBat4AMdI1pIN
Content-Disposition: form-data; name="photo"; filename="dsc_3256.jpg"
Content-Length: 134295
Content-Type: image/jpeg

......JFIF..............Exif..MM.*.....
...................
.........................................(...........1.....
.....2.......................i..............NIKON CORPORATION.NIKON D80....,.......,....Ver.1.01 .2007:10:22 15:12:34.

....
<more binary data>
....

------------rcL6ZwtjEeQEUrxtcTZ8hC1MaxC2ITI73bBcX5KkjkyBat4AMdI1pIN--HTTP/1.1 500 Internal Server Error
Content-Type: text/plain
Content-Encoding: gzip
Transfer-Encoding: chunked
Cache-control: private, must-revalidate, max-age=0
Date: Thu, 08 Nov 2007 12:58:10 GMT
Server: GFE/1.3
Connection: Close
------end---------------------------------------------------------

So the photo (from my D80) is transferred until the http server repots an error.

After this try I uploaded a photo to picasa using the webinterface of google picase itself. Here too the upload server to which the photo was transferred was (shown by wireshark) td-in-f91.google.com and this time it worked just fine.

Rainer
Comment 5 Vardhman 2007-11-12 21:32:07 UTC
Hey Krienke,

Thanks for helping on isolating the bug, sorry for the delay in response. I
was on vacation. I guess I am understanding the problem now. Just a few
things I want to verify from you (inlined below):

> ------start
> --------------------------------------------------------------------
> POST /data/feed/api/user/krienke uni-koblenz de/album/Test HTTP/1.1
>

The string after user/ and before /album is username for this particular url
the username appears to be "krienke uni-koblenz de" which is a string with
atlesast 2 spaces and a '-', If I am not wrong this doesn't hold as a valid
user name. A user name is your google account name or your gmail id.  So
what I want to ask you here is that
1) Did you give your gmail id for the username field ?
2) Was the software able to fetch a list of albums for you given login ?

These two answers will greatly help me in understanding the problem better.


regards
Vardhman
Hey Krienke,<br><br>Thanks for helping on isolating the bug, sorry for the delay in response. I was on vacation. I guess I am understanding the problem now. Just a few things I want to verify from you (inlined below):<br><div class="gmail_quote">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div class="Wj3C7c">------start --------------------------------------------------------------------
<br>POST /data/feed/api/user/krienke uni-koblenz de/album/Test HTTP/1.1</div></div></blockquote><div>The string after user/ and before /album is username for this particular url the username appears to be &quot;krienke uni-koblenz de&quot; which is a string with atlesast 2 spaces and a &#39;-&#39;, If I am not wrong this doesn&#39;t hold as a valid user name. A user name is your google account name or your gmail id.&nbsp; So what I want to ask you here is that 
<br>1) Did you give your gmail id for the username field ?<br>2) Was the software able to fetch a list of albums for you given login ?<br><br>These two answers will greatly help me in understanding the problem better.<br>
 </div><div><br><br></div></div>regards<br>Vardhman<br>-- <br>Blogs: <a href="http://vardhman.blogspot.com">http://vardhman.blogspot.com</a><br>
Comment 6 krienke 2007-11-13 07:31:22 UTC
Am Montag, 12. November 2007 21:32:09 schrieb Vardhman:

Hello Vardhman,

My picasa user name is krienke <at> uni-koblenz.de (Replace at with @ and 
delete spaces). There are no spaces inside the whole string. When I start the 
picasa export plugin I am asked for the username and the name thats shown is 
correct. This time I also tried to click on "Change user" and then entered my 
picasa username again but this did not change a thing.  

Before this I created a new album in picasa using the picasa web interface. 
After I started the export-plugin it immedeately showed this new album. Next 
I again tried to uplad a photo but this simply hangs, nothing happens. Next I 
closed the export plugin reopened it and tried to create a new album. There 
is no error message when I say "Create" but the new album is not created when 
I look at my albums in the web interface nor is it shown in the export plugin 
after a "reload abums". 

Here ist a snapshot how the picasa export window looks like when uploading a 
photo just as an info:

http://www.uni-koblenz.de/~krienke/tmp/picasaexport.jpg

Thanks
Rainer Krienke
Comment 7 Darek Borkowski 2008-01-19 21:38:34 UTC
The same problem is with kipi plugins version 0.1.5-rc1.

The way to omit this problem is to prepare new album in picasa web interface. The album name cannot contain any spaces. In case some album names contain spaces the plugin cannot fetch album names from serwer (the "Not feteched" info is displaed in the album names list instead of actual names).
Comment 8 Darek Borkowski 2008-01-25 08:49:54 UTC
Lets vote for this bug to increase the possibility that developers will take it serious and check it in order to confirm.
Comment 9 Darek Borkowski 2008-01-25 09:07:39 UTC
The one thing is quite strange for me. I compared source files of kipi plugins  0.1.5-rc1 with 0.1.5beta1 (subdirectory oicassawebexport). The only files which are different in two versions are: Makefile, kipiplugin_picasawebexport.desktop and *.moc files). The sources *.c and headers *.h are identical, but some kind of regression is visible:
Before, I used 0.1.5beta1, compiled from sources, under opensuse 10.3 i586. The export worked propoely except for album names and album creation. I had to create album by www picasa interface (in web browser) and the name couldn't include any spaces. After all the plugin fetched album names and could export photos. 
Now I use 0.1.5-rc1, also compiled from sources, with the same version of digikam 0.9.3 (installed from rpm) under opensuse 10.3 but now x64 version.
The plugin cannot fetch album names nor can upload photos. Even if I select one (any) from album names list, the upload stalls at 0%.
I suppose that there may be some changes in API on the Google side. I think I should install again older kipi plugins 0.1.5beta1 and test it.
Comment 10 Darek Borkowski 2008-01-25 09:11:21 UTC
The one thing is quite strange for me. I compared source files of kipi plugins  0.1.5-rc1 with 0.1.5beta1 (subdirectory oicassawebexport). The only files which are different in two versions are: Makefile, kipiplugin_picasawebexport.desktop and *.moc files). The sources *.c and headers *.h are identical, but some kind of regression is visible:
Before, I used 0.1.5beta1, compiled from sources, under opensuse 10.3 i586. The export worked propoely except for album names and album creation. I had to create album by www picasa interface (in web browser) and the name couldn't include any spaces. After all the plugin fetched album names and could export photos. 
Now I use 0.1.5-rc1, also compiled from sources, with the same version of digikam 0.9.3 (installed from rpm) under opensuse 10.3 but now x64 version.
The plugin cannot fetch album names nor can upload photos. Even if I select one (any) from album names list, the upload stalls at 0%.
I suppose that there may be some changes in API on the Google side. I think I should install again older kipi plugins 0.1.5beta1 and test it.
Comment 11 Darek Borkowski 2008-01-25 09:12:25 UTC
Created attachment 23267 [details]
Illustration of album names fetching problem
Comment 12 Darek Borkowski 2008-01-25 09:13:42 UTC
sorry for duplicated comment :)
Comment 13 krienke 2008-01-25 09:23:36 UTC
Am Freitag, 25. Januar 2008 09:11:21 schrieb Darek Borkowski:

I can tell that a friend of mine lately had to upgrade to a newer version of 
picasa in order to upload his photos to google allthough he did not change 
anything and had been able to upload photos before. Because of your 
experience and what I saw with my friend it could be that google simply 
change part of the protocol.

Using 1.5.1-beta1 I am still unable to upload images and now even folders 
appear always as "Not fetched". Some time ago at least the folders were shown 
with their name. For me it does not help to create an album (without any 
space or special character in the web frontend of picasa. When I try to 
upload a photo the process still hangs.

Rainer
Comment 14 Angelo Naselli 2008-01-25 22:40:52 UTC
> Using 1.5.1-beta1 I am still unable to upload images and now even folders 

According to NEWS file nothing has been released concerning Picasa export plugin,
sorry.
Comment 15 Alexander Drozdov 2008-04-28 03:32:38 UTC
Hi all, 

I try to use picasawebuploader plugin and it does not work for me, I try to fix next functionality:

1. Display gallery list (it does not work for me in some cases)
2. In gallery list display all galleryes, instead public only
3. Uploading files to galley, that name contained from two or more latin words or from one or more Russian (try for Russian and English only) words.

My patch:
http://hatred.homelinux.net/~hatred/picasawebexport_patch.diff

Sorry for big size, my editor reformat files on saving. Patch is based on 0.1.5rc2.
Comment 16 Alexander Drozdov 2008-04-28 03:35:23 UTC
Created attachment 24540 [details]
My fix for basic functionality

My fix for basic functionality of picaseweb exporter
Comment 17 Vardhman 2008-04-28 09:48:09 UTC
Hey Alex,
  Thanks for the patch, I would love to review it and accept it but right
now the formatting has lead to a very big change list with almost all lines
being changes (every line has got some extra white spaces in the beginning
for e.g) please make sure only the lines which you modified show up in the
patch Change list.


Vardhman
On Sun, Apr 27, 2008 at 6:35 PM, Alexander Drozdov <adrozdoff@gmail.com>
wrote:

[bugs.kde.org quoted mail]



Hey Alex,<br>&nbsp; Thanks for the patch, I would love to review it and accept it but right now the formatting has lead to a very big change list with almost all lines being changes (every line has got some extra white spaces in the beginning for e.g) please make sure only the lines which you modified show up in the patch Change list.<br>
<br><br>Vardhman<br><div class="gmail_quote">On Sun, Apr 27, 2008 at 6:35 PM, Alexander Drozdov &lt;<a href="mailto:adrozdoff@gmail.com">adrozdoff@gmail.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">------- You are receiving this mail because: -------<br>
You are on the CC list for the bug, or are watching someone who is.<br>
<br>
<a href="http://bugs.kde.org/show_bug.cgi?id=150979" target="_blank">http://bugs.kde.org/show_bug.cgi?id=150979</a><br>
<br>
<br>
<br>
<br>
</div>------- Additional Comments From adrozdoff gmail com &nbsp;2008-04-28 03:35 -------<br>
Created an attachment (id=24540)<br>
&nbsp;--&gt; (<a href="http://bugs.kde.org/attachment.cgi?id=24540&amp;action=view" target="_blank">http://bugs.kde.org/attachment.cgi?id=24540&amp;action=view</a>)<br>
My fix for basic functionality<br>
<br>
My fix for basic functionality of picaseweb exporter<br>
</blockquote></div><br><br clear="all"><br>-- <br>Blogs: <a href="http://vardhman.blogspot.com">http://vardhman.blogspot.com</a><br>
Comment 18 Alexander Drozdov 2008-04-29 01:41:34 UTC
Hi Vardhman,

Ok, today I try to prepare new patch with my changes only and upload it to this bug-report.
Comment 19 x3ri7yz02 2008-05-25 02:01:45 UTC
Created attachment 24926 [details]
QObject errors seen on console during failed export from Digikam to Picasa

Testing with 0.9.4-beta5:

- Picasa export doesn't work.  Unable to list albums.
- lots of errors reported on the console - one example below, others in
attached document.

	
		QObject::connect: No such signal
KIPIPicasawebExportPlugin::PicasawebTalker::signalGetAlbumsListFailed(const
QString&msg)
		QObject::connect:  (sender name:   'unnamed')
		QObject::connect:  (receiver name: 'unnamed')
Comment 20 caulier.gilles 2008-05-25 10:45:36 UTC
*** Bug 157148 has been marked as a duplicate of this bug. ***
Comment 21 caulier.gilles 2008-05-25 11:17:48 UTC
To Tauri, #19: 

i have already fixed all broken signal/slots connections to svn. Are you use a fresh checkout of svn code. Also, i recommend to clean-up preview compilations using 'make clean'.

Gilles Caulier
Comment 22 Robert Munteanu 2008-06-20 21:52:08 UTC
*** This bug has been confirmed by popular vote. ***
Comment 23 Fabien 2008-06-26 17:33:30 UTC
Does someone use this plugin with success with latest svn version (kipi + digikam) ?

For me, when starting the upload, I have a stalled progress bar and no pictures get uploaded...
Comment 24 Vardhman 2008-06-26 19:28:46 UTC
I have used the same and works quite well for me. to verify I just uploaded
a photo again.

My digikam version: 0.9.4
Kipi library version: 0.1.6.

To understand the reason behind failure in you case, it would be great if
you launch the application from console and cut paste the logs (if compiled
in debug mode).
If its possible for you to help by tracing the problem using one of the
network traffic monitoring tools like ethereal or tcpdump it would be great
too.

BTW while verifying this bug I found that the plugin doesn't indicate the
login failure problem and shows the upload screen active even if you enter
wrong password. This is a new bug, I will try to put the patch asap.


Vardhman
On Thu, Jun 26, 2008 at 9:03 PM, Fabien <fabien.ubuntu@gmail.com> wrote:

[bugs.kde.org quoted mail]



I have used the same and works quite well for me. to verify I just uploaded a photo again. <br><br>My digikam version: 0.9.4<br>Kipi library version: <a href="http://0.1.6.">0.1.6.</a><br><br>To understand the reason behind failure in you case, it would be great if you launch the application from console and cut paste the logs (if compiled in debug mode). <br>
If its possible for you to help by tracing the problem using one of the network traffic monitoring tools like ethereal or tcpdump it would be great too.<br><br>BTW while verifying this bug I found that the plugin doesn&#39;t indicate the login failure problem and shows the upload screen active even if you enter wrong password. This is a new bug, I will try to put the patch asap.<br>
<br><br>Vardhman<br><div class="gmail_quote">On Thu, Jun 26, 2008 at 9:03 PM, Fabien &lt;<a href="mailto:fabien.ubuntu@gmail.com">fabien.ubuntu@gmail.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">------- You are receiving this mail because: -------<br>
</div>You are the assignee for the bug, or are watching the assignee.<br>
<div class="Ih2E3d"><br>
<a href="http://bugs.kde.org/show_bug.cgi?id=150979" target="_blank">http://bugs.kde.org/show_bug.cgi?id=150979</a><br>
<br>
<br>
<br>
<br>
------- Additional Comments From fabien.ubuntu gmail com &nbsp;2008-06-26 17:33 -------<br>
Does someone use this plugin with success with latest svn version (kipi + digikam) ?<br>
<br>
For me, when starting the upload, I have a stalled progress bar and no pictures get uploaded...<br>
</div><div><div></div><div class="Wj3C7c">_______________________________________________<br>
Kde-imaging mailing list<br>
<a href="mailto:Kde-imaging@kde.org">Kde-imaging@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-imaging" target="_blank">https://mail.kde.org/mailman/listinfo/kde-imaging</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Blogs: <a href="http://vardhman.blogspot.com">http://vardhman.blogspot.com</a><br>
Comment 25 Dragon 2008-08-18 07:31:00 UTC
For whatever info it can contribute I have this bug on Debian Lenny.  I have found that if I create or change a album on the Picassa site to be public vs. private I can load those folders in the list.  And while it takes a while to upload the photo ( due to compression?) it will upload to a public gallery.

I have also discovered that if a Picassa folder has spaces and is public it will show in the list but the upload will fail.  If you remove the spaces and leave it public the upload will complete.

So at least a work around is to create a public folder with no spaces in the name and upload.  If you desire to keep it private vs. public you will need to go into the web album and change properties.

While not technical I hope this helps the devs.  This is really such a shining example of a great Linux/KDE app, I enjoy it far better than Picassa and at least can now use it again.  I'm sure one day this will be fixed.
Comment 26 Vardhman 2008-08-27 20:24:33 UTC
Hey Dragon,
Based on your detailed explanation, I have just fixed the bug related to spaces in album names. 
Strangely the fix for the listing of private albums has been done quite long back ~2 months at least, I am not sure if the version of yours is older than that.

If someone can test the feature on the latest SVN checkout, and give a feedback, I would promise a quick turnaround :)
Comment 27 Philippe ROUBACH 2008-11-15 13:49:03 UTC
i discovered an interesting thing :

when i first used picasaweb i create a count with :

id : <name>@free.fr
password : <my password>

then

later

with my google count

i activated and explored the google tool gmail then google created
a new mail address  <first name>.<last name>@gmail.com

i don't use gmail address and i don't use it to connect to google

i use picasaweb and picasa soft with
id : <name>@free.fr
password : <my password>

this works well

now what happens with picasawebexport ?

if i use
id : <name>@free.fr
password : <my password>

picaswebexport does not list my album and freeze or crash if use "start
uploading"

if i use

id : <first name>.<last name>@gmail.com
pwd : <password2>

picasawebexport lists all my albums and i can upload a photo but not a video