Summary: | Baloo metadata not written out by Album | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Jeff Dooley <jfd5xte> |
Component: | Database-Baloo | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles, metzpinguin |
Priority: | NOR | ||
Version: | 5.0.0 | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.3.0 | |
Sentry Crash Report: |
Description
Jeff Dooley
2015-11-29 10:41:51 UTC
The problem is mostly in Ballo implementation. With KDE4 nothing is maintained and developers swith to KF5 to support Baloo. So i recommend to test with digiKam 5.0.0-beta1 which is KF5 based. Note : Baloo sound like more and more difficult to follow and make digiKam very unstable. digiKam team have talk seriously about the future to support Baloo, and if the situation do not change ASAP, well we will drop Baloo support as well... Gilles Caulier This file still valid using digiKam 5.0.0 ? Gilles Caulier (In reply to caulier.gilles from comment #2) > This file still valid using digiKam 5.0.0 ? Update to my now current setup: Kubuntu 16.04 Plasma 5.6.5 installed via ppa:/kubuntu-backports Frameworks 5.23.0 installed via ppa:/kubuntu-backports Qt 5.5.1 (unknown package source) Digikam 5.0.0 installed via ppa:/philip5/extra I attempted to reproduce test case #1 of a newly tagged file, and test case #2 of previously tagged files with metadata refreshed. Unfortunately, I am not currently seeing the metadata transferred to the file extended attributes at all, at least when testing using the Dolphin information panel. Could still be an installation/set-up issue, but I wanted to at least report my current findings. Thanks for following up. digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Best Regards Gilles Caulier Fixed with Bug 433984 and Bug 434060 Maik |