Selecting the menu option "Export-> Export to flickr.." an error dialog box (localized) says "An error occurred: unknown error. Cannot continue". I then dismiss the error, select the "upload options" tab and then push the button "use a different account" (up to this point no account is selected), but the same message dialog pops up again. The only messages I see if I start digikam from a konsole are: Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work. but those are displayed before starting the upload. I saw this first in mageia 3, I just upgraded to 4 to see if it has been resolved. Reproducible: Steps to Reproduce:
Still happens with the version from updates testing (digikam-3.5.0-3.1.mga4, kipi-plugins-3.5.0-3.1.mga4, kipi-plugins-flickr-3.5.0-3.1.mga4)
Most probably it's this bug: https://bugs.kde.org/show_bug.cgi?id=336835
Definitely is that bug. I hexedited kipiplugin_flickrexport.so (I wasn't in the mood to patch and rebuild the digikam rpm) to use the urls in comment 5 of that bug and I can upload photos to flickr.
Source RPM: digikam-3.5.0-3.mga4.src.rpm => digikam-3.5.0-3.1.mga4.src.rpm
CC: (none) => fundawangAssignee: bugsquad => mageiaSummary: Unknown error exporting to flickr => Digikam: Unknown error exporting to flickr
This should be fixed in the latest version of digikam, 4.2.0. Maybe we could update digiKam to this version and push it in Backport repos.
CC: (none) => olivier.delaune
This bug should be fixed with kipi-plugins-flickr-3.5.0-3.2.mga4, soon available in core/updates_testing. It will be part of upcoming KDE 4.12.5 update for mga4. upstream patch backported http://commits.kde.org/kipi-plugins/1d4a95bc3d36060a025b8950aaaca467253532bc
CC: (none) => lmenutHardware: x86_64 => AllDepends on: (none) => 13221
Do we have any idea of a release date for either updated kipi plugins or Digikam 4.2? Having failed to install both of the above from rpms, neither of which seem happy to run on my system, no doubt because I am not running cualdron, I also attempted to install Digikam 4.2 from a tarball, again to no avail. Could someone give more detailed instructions of how to either install the backported version of kipi-plugins, or to manually edit the three URLs mentioned in the linked thread (https://bugs.kde.org/show_bug.cgi?id=336835) to make them https: I often wish I were somewhat more experienced in such matters - I still have to check how to install a tarball every friggin time...
CC: (none) => j.f.e.fleming
Jack, I see that the updated kipi-plugins-flickr-3.5.0-3.2.mga4 is available in updates_testing. In fact I just installed it and I can confirm it is working. Link for x86_64 http://ftp.sunet.se/pub/Linux/distributions/mageia/distrib/4/x86_64/media/core/updates_testing/kipi-plugins-flickr-3.5.0-3.2.mga4.x86_64.rpm Link for i586 http://ftp.sunet.se/pub/Linux/distributions/mageia/distrib/4/i586/media/core/updates_testing/kipi-plugins-flickr-3.5.0-3.2.mga4.i586.rpm
After adding updates_testing to my sources, kipi-plugins-flickr-3.5.0-3.1.mga4 is listed as available in rpm drake. Having deselected the older version (3.0.mga4), attempting to install 3.1 (which, being only 3.1, not 3.2, probably wont fix the flickr problem anyway), gives the error: 1 installation transactions failed There was a problem during the installation: ...retrieving failed: aria2 failed: exited with 3 So I can't even see if 3.1 might work (though I don't think it will). Any ideas what the error might mean, or why 3.2.mga4 is unavailable on my (seemingly) up-to-date system? If not, I am back at asking for advice for how to manually change the urls to https, or hoping for a quick release of digikam 4.2 on Mageia...
@Jack, could you try again. It should be a momentary problem. I installed kipi-plugins-flickr-3.5.0-3.2.mga4 on Mageia 4 64-bits and the export to flickr works fine. The update fixes the problem here.
Fixed in kipi-plugins-flickr 3.5.0-3.2
Status: NEW => RESOLVEDResolution: (none) => FIXED