| Summary: | Export to Piwigo not working - Dialog box not responding | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Bart <beurdy> |
| Component: | Plugin-WebService-Piwigo | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | caulier.gilles, frederic.coiffier, metzpinguin |
| Priority: | NOR | ||
| Version: | 5.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.1.0 | |
| Sentry Crash Report: | |||
| Attachments: |
Digikam output
Output GDB Digikam Output with kdebugdialog |
||
|
Description
Bart
2016-07-03 21:19:13 UTC
Please run digiKam in GDB and give us a backtrace to hack https://www.digikam.org/contrib Gilles Caulier Created attachment 99847 [details]
Digikam output
Here's the requested output frrom GDB. Not sure if i's of any use though..
There is no debug symbols in digiKam suitable with GDB. Install digiKam+kipiplugins debug packages and try again Gilles Caulier A log console (enabled with kdebugdialog5 if it still works with Digikam 5.0.0) could be also useful. 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 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)
Created attachment 99871 [details]
Output with kdebugdialog
Output with kdebugdialog. Output for digikam and kipi enabled.
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 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 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 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) Piwigo is in the kipiplugins packages not in the digiKam packages. Also updated? Maik 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 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 |