Bug 365049 - Export to Piwigo not working - Dialog box not responding
Summary: Export to Piwigo not working - Dialog box not responding
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-WebService-Piwigo (show other bugs)
Version: 5.0.0
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-03 21:19 UTC by Bart
Modified: 2018-02-01 05:22 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.1.0


Attachments
Digikam output (7.97 KB, text/plain)
2016-07-04 15:45 UTC, Bart
Details
Output GDB Digikam (5.77 KB, text/plain)
2016-07-05 20:31 UTC, Bart
Details
Output with kdebugdialog (2.91 KB, text/plain)
2016-07-05 20:33 UTC, Bart
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bart 2016-07-03 21:19:13 UTC
When connecting to Piwigo, nothing happens after entering the Piwigo URL, username and password. Digikam is not connecting to Piwigo, and cancelling the operation does not work

Reproducible: Always

Steps to Reproduce:
1. In Digikam, select export -> Piwigo
2. Enter Piwigo URL, username and password
3. Nothing happens

Actual Results:  
Nothing happens, neither can the action be cancelled

Expected Results:  
Succesfull connection to Piwigo

- Fedora 26 x86_64
- Digikam 5.0.0 BETA 7
Comment 1 caulier.gilles 2016-07-04 04:34:15 UTC
Please run digiKam in GDB and give us a backtrace to hack

https://www.digikam.org/contrib

Gilles Caulier
Comment 2 Bart 2016-07-04 15:45:59 UTC
Created attachment 99847 [details]
Digikam output

Here's the requested output frrom GDB. Not sure if i's of any use though..
Comment 3 caulier.gilles 2016-07-04 15:48:34 UTC
There is no debug symbols in digiKam suitable with GDB. Install digiKam+kipiplugins debug packages and try again

Gilles Caulier
Comment 4 Frédéric COIFFIER 2016-07-04 15:55:16 UTC
A log console (enabled with kdebugdialog5 if it still works with Digikam 5.0.0) could be also useful.
Comment 5 Maik Qualmann 2016-07-05 10:26:14 UTC
The question is which version of kipiplugins you in Fedora exactly use? Piwigo is now ported to the QNetworkAccessManager. I have just tested it again with my server. It works as expected. Also incorrect entries are correctly displayed with a message box.

Maik
Comment 6 Bart 2016-07-05 20:31:57 UTC
Created attachment 99869 [details]
Output GDB Digikam

Installed packages:

[bart@localhost ~]$ rpm -aq | grep digikam
digikam-libs-5.0.0-0.12.beta7.fc24.x86_64
digikam-debuginfo-5.0.0-0.12.beta7.fc24.x86_64
digikam-5.0.0-0.12.beta7.fc24.x86_64
[bart@localhost ~]$ rpm -aq | grep kipi
kf5-libkipi-16.04.2-2.fc24.x86_64
kf5-kipi-plugins-libs-5.0.0-0.12.beta7.fc24.x86_64
kf5-libkipi-debuginfo-16.04.2-2.fc24.x86_64
kf5-kipi-plugins-5.0.0-0.12.beta7.fc24.x86_64
[bart@localhost ~]$

Attached are new loggings with debugpackages installed ([root@localhost ~]# dnf debuginfo-install digikam-5.0.0-0.12.beta7.fc24.x86_64)
Comment 7 Bart 2016-07-05 20:33:42 UTC
Created attachment 99871 [details]
Output with kdebugdialog

Output with kdebugdialog. Output for digikam and kipi enabled.
Comment 8 Maik Qualmann 2016-07-05 21:05:48 UTC
The log is incomplete, it does not contains the start of Piwigo.

Are in your Piwigo installation already albums created? This albums do not appear in the list? Piwigo cannot create albums, this must be done via the web interface.

Maik
Comment 9 Bart 2016-07-05 21:26:18 UTC
I think the problem is that nothing is being initiated when I press the OK-button on the diaglogbox (the one that requires the URL to Piwigo and username/pass). Nothing is written to the logs, but Digikam is no longer responding either. I cannot even cancel the current dialogbox.

I succesfully managed my Piwigo photo's with Digikam in Fedora 23
Comment 10 Maik Qualmann 2016-07-06 04:57:21 UTC
After looking into the last changes I remember now that since I had same problem and had fixed it. Wait until Fedora has the packages for final digiKam and kipiplugins 5.0.0 available. The problem is fixed in any case in the current version.

Maik
Comment 11 Bart 2016-07-12 15:43:57 UTC
Just updated Digikam from van Fedora testing repo. Result:

[bart@laptop ~]$ rpm -aq | grep digikam
digikam-doc-5.0.0-1.fc24.noarch
digikam-libs-5.0.0-1.fc24.x86_64
digikam-5.0.0-1.fc24.x86_64

However, the bug is still there...

About Digikam shows: Build date: Jul 11 2016 (target: release)
Comment 12 Maik Qualmann 2016-07-12 16:12:53 UTC
Piwigo is in the kipiplugins packages not in the digiKam packages. Also updated?

Maik
Comment 13 Bart 2016-07-12 20:17:15 UTC
Thanks for that, works!

One small note: It's now required to enter a complete URI (http://etc.etc.com). It would be nice if the http:// could be omitted
Comment 14 Maik Qualmann 2016-07-12 20:44:16 UTC
Yes, the QNetworkAccessManager required http:// for work, but it's easy this internally to complete. I'll do it for digiKam-5.1.0. I close now this bug.

Maik