https://bugs.kde.org/show_bug.cgi?id=431497
tlangner+...@bitvalve.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tlangner+...@bitvalve.org
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
--- Comment #8 from tlangner+...@bitvalve.org ---
I can confirm this problem. It looks like it has to do with dangling entries in
the database. This problem is particularly annoying as face tags with an
unconfirmed count > 0 appear first in the list of tags, making it difficult to
find them when one searches alphabetically.
Would be nice if this bug is fixed.
Since I got a bit annoyed by this, I played around and found a rather ugly fix.
It involves meddling with digiKam's database directly, which can possibly mess
up things, so please only follow the steps if you know what you are doing, be
careful and make a backup before you try this.
1) Close digiKam to prevent any concurrent modification of the database.
Potentially unnecessary but does not hurt.
2) Create a copy of the file digikam4.db in your database directory.
3) Open digikam4.db with a sqlite DB editor, I use sqlitebrowser.
4) Run the following query on the database to check whether the counts
correspond to the wrong unconfirmed counts in the app:
SELECT name, COUNT(*) FROM ImageTagProperties AS itp LEFT JOIN Tags AS t ON
itp.tagid = t.id WHERE property = 'autodetectedPerson' GROUP BY name;
If that is the case, run the following query to get rid of them.
DELETE FROM ImageTagProperties WHERE property = 'autodetectedPerson'
If I understand the database contents correctly, entries in this table with
that property represent unconfirmed faces, which are exactly what we want to
get rid of.
After I run those steps, the unconfirmed counts return to zero as they should.
--
You are receiving this mail because:
You are watching all bug changes.
