Flickr API changed to https-only, Flickr export from kipi-plugins only uses http

[Torben Früchtenicht]

When trying to export pictures from Digikam to my Flickr account, I get a popup telling me that my token has expired. Telling Digikam to go ahead fetching a new token only results in another popup for "An error occurred: Unknown error. Cannot proceed" (rough translation from German popup). If I close that popup the progress bar popup remains visible, hanging at 50% (last message in that popup is "Getting frob".

Digikam did not give me any hints about what might be going wrong. But it seems like the latest change of the Flickr API - https is now the only allowed protocol - might be the issue here: See this bug report in KDE bug tracking: https://bugs.kde.org/show_bug.cgi?id=336835 (see comment 5) and there is this announcement from Flickr: https://www.flickr.com/help/forum/en-us/72157645440333073/

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: kipi-plugins 4:3.5.0-0ubuntu10
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Jul 6 23:07:26 2014
InstallationDate: Installed on 2014-06-01 (35 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
SourcePackage: digikam
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Deedot Dabbeljuh (wess-ubone-de)]

Problem in KDE tracking seems solved:

https://bugs.kde.org/show_bug.cgi?id=336835

[Torben Früchtenicht (tf-r)]

So this means we can expect a fix for the Digikam version in the Ubuntu repos in the near future?

[Rob Bruce (r-bruce)]

"So this means we can expect a fix for the Digikam version in the Ubuntu repos in the near future?"

I hope I'm reading this wrong, but from the kde.org bug tracker, it looks like this issue is fixed in kipi version 4.2.0. And 4.2.0 is in Utopic (and later) distro versions. For *Ubuntu LTS users, that means a fix should appear in the 2nd quarter of 2016 with the 16.04 release, right? Xeric Xolo, maybe? That's less than a year and a half.