digiKam › digikam-users

All tagging lost

Classic

List

Threaded

4 messages Options

SkyDiver

All tagging lost

Haven't used digiKam (5.6) for a while and when I launched it today I saw
that 5.7 is out.
After upgrading to 5.7 the Tags/People trees are empty.
(*) Since I haven't used the app in a while, I can't tell if this is a
direct result of the upgrade or not.

I rolled back to 5.6 and the behavior persisted so I re-installed 5.7.

I already lost all taging once in v5.6 and had to re-tag everything. This
time I first took a look at the database and noticed that all the data is
there, well organized in the various tables.

My configuration is:
OS: Windows 10 64-bit
MySQL: External instance, running on the same OS.

Here's a dump of the statistics from digiKam's Help menu:
digikam version 5.7.0
Images:
BMP: 4
JPG: 29108
PNG: 28
total: 29140
:
Videos:
AVI: 4
MOV: 255
MP4: 1066
MTS: 24
total: 1349
:
Total Items: 30489
Albums: 190
Tags: 46
:
Database backend: QMYSQL
Host Name: 127.0.0.1
Host Port: 3306
User account: digikam
Connect options:
Core Db name: digikam
Thumbs Db name: digikam
Face Db name: digikam

Your help is appreciated.

--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

SkyDiver

Re: All tagging lost

If no one will help me I'll have to help myself.
So I dug deeper into the website and found how to get a dump of the trace
messages (DbgView.exe as I'm running on Windows), and then found the
following suspicious lines:

[18488] digikam.general: Failed to find parent tag for tag
"_Digikam_Internal_Tags_" with pid -1
[18488] digikam.general: Failed to find parent tag for tag "People" with
pid -1

Took a look at the tags table, and assuming pid = parent id and assuming
only _Digikam_root_tag_ I modified the above error tags' pid to 0
(_Digikam_root_tag_).

This fixed my issue and tags are now back.

One question remains: why were these values changed to -1 instead of 0?
I can promise I didn't mess with the DB up until today.

--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

AndriusWild

Re: All tagging lost

In reply to this post by SkyDiver

Could you please post here:

https://bugs.kde.org/show_bug.cgi?id=375346

I switched to mysql awhile ago, got this issue, got freaked out and switched back to sqlite and never looked back :)

Your database digging might actually help to find what is causing the issue.

Sent from my Samsung Galaxy smartphone.

-------- Original message --------

From: SkyDiver <[hidden email]>

Date: 2017-10-17 12:11 PM (GMT-07:00)

To: [hidden email]

Subject: Re: All tagging lost

SkyDiver

Re: All tagging lost

Hey Andrey, sorry but I totally missed your request. I bumped into it
now so I posted my findings in
https://bugs.kde.org/show_bug.cgi?id=375346
The bug's status is RESOLVED FIXED, but judging from the comments it
doesn't seem to be.
Please see if you can get some from development to take another look at it.
10x.

On Tue, Oct 17, 2017 at 9:36 PM, Andrey Goreev <[hidden email]> wrote:

> Could you please post here:
>
> https://bugs.kde.org/show_bug.cgi?id=375346
>
> I switched to mysql awhile ago, got this issue, got freaked out and switched
> back to sqlite and never looked back :)
>
> Your database digging might actually help to find what is causing the issue.
>
>
>
> Sent from my Samsung Galaxy smartphone.
>
> -------- Original message --------
> From: SkyDiver <[hidden email]>
> Date: 2017-10-17 12:11 PM (GMT-07:00)
> To: [hidden email]
> Subject: Re: All tagging lost
>
> If no one will help me I'll have to help myself.
> So I dug deeper into the website and found how to get a dump of the trace
> messages (DbgView.exe as I'm running on Windows), and then found the
> following suspicious lines:
>
> [18488] digikam.general: Failed to find parent tag for tag
> "_Digikam_Internal_Tags_" with pid -1
> [18488] digikam.general: Failed to find parent tag for tag "People" with
> pid -1
>
> Took a look at the tags table, and assuming pid = parent id and assuming
> only _Digikam_root_tag_ I modified the above error tags' pid to 0
> (_Digikam_root_tag_).
>
> This fixed my issue and tags are now back.
>
> One question remains: why were these values changed to -1 instead of 0?
> I can promise I didn't mess with the DB up until today.
>
>
>
> --
> Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html