Bug 246074

Summary: Can't export photos to Picasaweb
Product: [Applications] digikam Reporter: Grzegorz Golec <grzesiek.golec>
Component: Plugin-WebService-GoogleAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, nowardev
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In: 2.0.0
Sentry Crash Report:

Description Grzegorz Golec 2010-07-28 20:45:22 UTC
Version:           1.2.0 (using KDE 4.4.4) 
OS:                Linux

Can't export photos to Picasaweb album whilst gwenview works fine. 

Reproducible: Always

Steps to Reproduce:
precondition:
you can create new albums, and retrieve existing ones

steps:
1. select photos
2. export them to PicasaWeb 


Actual Results:  
Actual outcome:
I got the following message all the time:
"Failed to upload photo into Picasaweb: Failed to upload photo
Do you want to continue?"

Expected Results:  

Expected outcome:
Photos are exported sucessfully


Further information:
I don't have any problems login there. The same photos I can export under Gwenview successfully. Only Digikam return error, hence I guess that is not kipi-plugins problem.
Comment 1 caulier.gilles 2010-07-29 09:50:46 UTC
The error message come from the plugin, not digiKam. digiKam don't know how to deal with Picasaweb.

digiKam only set an interface to the plugin with local collection.

Which libkipi and kipi-plugins you use ? Go to Help/Components Info for details.

Can you update digiKam to last satble 1.3.0 ?

Gilles Caulier
Comment 2 Grzegorz Golec 2010-07-29 10:43:10 UTC
But there is something wrong with this interface to the plugin. As I mentioned earlier, Gwenview uses the same kipi-plugins package and I can upload photos every time successfully. How to explain it?
Is it really possible that problem causes kipi-plugins side?

my packages:
kde-base/libkipi-4.4.4
media-plugins/kipi-plugins-1.2.0-r2

I will try to update it to 1.3.0. Unfortunately there is no fresh gentoo ebuilds yet. I will try to compile manually from svn. I will give you update.

Anyway I still don't believe that kipi-plugins makes problem... :)
thanks for quick response!
Comment 3 Grzegorz Golec 2010-07-29 13:37:40 UTC
Update: I tried to compile but whether I compile it from svn or faked ebuild I got dependencies error to libkdcraw and libkexiv2.
Issue has been already reported. 
http://bugs.gentoo.org/show_bug.cgi?id=327245

If it's kipi-plugins issue, I have to wait for KDE-4.5 where is version 1.3.0.
Comment 4 nowardev 2011-03-13 14:11:46 UTC
again on kde 4.6.1 with kipi pliugins 1.9 compiled 

Failed to upload photo into Picasaweb: Failed to upload photo
Do you want to continue?
Comment 5 caulier.gilles 2011-04-06 13:50:06 UTC
Please enable kipi debug space with kdebugdialog and run digiKam from a console. Look if any error traces appear on the console when you run picasa tool

Gilles Caulier
Comment 6 nowardev 2011-04-06 16:49:18 UTC
hi , thank you for your answer ,but now i have reinstalled kubuntu , and so i have tried with the packaged version.

Now with digikam and it works, instead with ksnapshot no :S

so i have started ksnapshot and here it is with the debug as you said before 

and here it is 

http://paste.ubuntu.com/590285
Comment 7 nowardev 2011-04-06 16:52:24 UTC
here there is a screenshot of the situation :S https://bugs.kde.org/show_bug.cgi?id=270167  this was the bug report for ksnapshot maybe can be merger i dunno.
Comment 8 caulier.gilles 2011-04-06 19:10:52 UTC
I can see nothing special in the backtrace. All sound working fine when plugin talk with picasa web service.

The story continue to ksnapshot...

Gilles Caulier
Comment 9 Grzegorz Golec 2011-04-07 10:55:12 UTC
Hi,

Just for your information. I'm not sure is it valid bug at all. 
I reported it but... I use gentoo. I used to upgrade kipi/digikam continuously. This bug has been resolved for me by removing existing photo database and repeating scanning all media again. After that digikam could send photos to picasa. 
You can try it, perhaps helps. 
I guess that there is some incompatibility between following versions in database integrity or something, however I'm not expert.