| Summary: | Tagging images can change the sorted view | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Jérôme DEMEULLE <jdemeulle.photo> |
| Component: | Searches-Labels | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | https://invent.kde.org/graphics/digikam/-/commit/82637fd007e1f72ded2e538b72d20d0cfaae1686 | Version Fixed/Implemented In: | 8.5.0 |
| Sentry Crash Report: | |||
|
Description
Jérôme DEMEULLE
2024-08-21 18:25:39 UTC
I can't reproduce that here. We have a bug in digiKam-8.4.0 that means that the correct rating or creation date is not saved in the database during the first scan. When assigning metadata, a re-read takes place and the correct creation date is set. Please use digiKam-8.5.0 from here as a pre-release: https://files.kde.org/digikam/ Maik Hi Maik, Thank you for effort I just tested with the 8.5 compiled today and I have exactly the same behaviour. Do I should to roll back to 8.4 with my data base saved ? No, you don't need to go back, as digiKam-8.5.0 already fixes some important bugs. However, you will need to re-read the metadata from the images in question so that the problem doesn't occur again. Maik Ok, I tried again with a different set of photos and can actually reproduce this behavior... Maik Git commit 82637fd007e1f72ded2e538b72d20d0cfaae1686 by Maik Qualmann. Committed on 21/08/2024 at 21:08. Pushed by mqualmann into branch 'master'. fix missing set UTC time spec in the tag item lister FIXED-IN: 8.5.0 M +2 -2 core/libs/database/item/lister/itemlister_talbum.cpp https://invent.kde.org/graphics/digikam/-/commit/82637fd007e1f72ded2e538b72d20d0cfaae1686 Thank's, Y're a magician... Hi Maik, should I do something with the ticket status when I see that the issue is resolved (tested with the latest available version) ? no more, file is closed now... |