I am running on my primary system :Desk: i7-4790K Leap 42.3(x86_64)4.4.92-31 KF5 5.40.0 Plasma 5.11.4 Qt 5.9.3
with Digikam 5.7.0 loaded from the KDE:extras repo.
Digicam opens from the GUI desktop, no error messages, but Displays the albums tree with no images listed in the directory structure.
On the Digikam forum, I see some discussions related to issues with Qt 5.9.x, works on some distros, I think.
Anyone here seeing this issue, or better yet, has it working?
I have tried starting Digikam in a Konsole window, I get the same GUI window results, disconcerting messages in Konsole like “digikam.general: Cancel Main Thread”
but nothing waving a red flag declaring fatal errors.
I am assuming this is a Digikam build issue, but would be interested in others experience.
What Paul says. Plus, the issue is not with digikam, it’s your system, using repos other than the distro’s. The digikam package you’re trying to use is probably built agains another Qt version than you have installed.
Thanks for inputs.
Interestingly, I rechecked Digikam-Help-About-Libraries from within the running application and it reports
l Version 5.7.0
- KDE Frameworks 5.40.0
- Qt 5.9.3 (built against 5.9.3)
- The *xcb*
windowing system
As for using KDE Extra, I am using the Leap 42.3 version of KDE Extra
but do understand this is not the default Digikam version which is 5.5.0 from Leap-42.3-Oss
Looking at related chatter, it is not clear if the bug was/is in QT5.9.3 or hidden in Digikam 5.7.0 until QT5.9.3 was released.
It appears resolved, on Arch, with a package fix in Digikam.
Agreed, it’s not too clear where blame is being apportioned to. The final post indicates if digikam is built specifically against Qt 5.9.3 that solves the problem.
I’m not sure how that will impact leap. Looking at the (OBS KDE:Extra) changelog ( https://build.opensuse.org/package/view_file/KDE:Extra/digikam/digikam.changes?expand=1 ) it currently has “BuildRequire Qt >= 5.6.0”. If that’s bumped to 5.9.3 then I guess it would fail to build on leap, TW also at the moment, as that’s on 5.9.2. So I don’t know if those changes would (yet) be accepted.
Perhaps consider running digikam as an AppImage bundle? I’ve never used that method myself so don’t know if it would be a practical solution.
There are appimage versions of Digikam which can be tried and dont rely on the code you have installed. Try one of these (see their website) and see what happens. My 5.7 from normal repo works fine on TW, as do the appimage versions available.
Stuart - thanks for the added info.
As someone else points out above, TW is still at QT5.9.2, whereas Leap 42.3 with KDE:Qt repo is at Qt5.9.3.
If you follow the links above into Arch Linux forums, they hit, and I think resolved the issue a couple weeks back, but it is hard to tell if the resolution was in QT or Digikam. As I read it, Digikam 5.7.0 and Qt 5.9.3 do not play well.
FYI, “OSS” repo here on 42.3 is still Digikam 5.5.0.
I have been using KDE:Extra Repo to stay a bit more current.
And yup, every once in a while the cart gets in front of the horse