Bug 318242 - Deleting a tag crashes Digikam
Summary: Deleting a tag crashes Digikam
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Tags-Engine (show other bugs)
Version: 3.1.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-12 15:37 UTC by Marcus
Modified: 2016-07-14 09:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 5.1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcus 2013-04-12 15:37:57 UTC
Running digikam: deleting or moving a tag in the tag bar on the left side of the main window, it works fine. I can go ahead deleting or moving tags, no problem.

But.
If I tag pictures using the tag bar on the right first and than delete or move a tag in the left tag bar area, it very often, almost always crashes digikam. If the tag is related to the pictures just tagged or is actually used DOESN'T seem to matter. 

Maybe it is triggered by using the filter-tag-field on the right tags bar!!

Reproducible: Sometimes

Steps to Reproduce:
1. Start Digikam
2. Go to the right tags bar and add something to the filter-tags-field
3. Than go to the left side tags bar and move or delete a tag.
4. Confirm delete
5. CRASH 
(There must still be somthing else, as sometimes it doesn't crash this way)
Actual Results:  
Crashes Digikam.
The tag is not successfully moved.
Deleting works, even if digikam crashes.


maybe related to  bug 309061
Comment 1 Marcus 2013-04-12 15:43:17 UTC
Bug 310950 is very similar, as well Bug 310193 and Bug 317545
Comment 2 Jekyll Wu 2013-04-12 20:48:21 UTC
And where is the backtrace of the crash ?
Comment 3 caulier.gilles 2013-04-13 04:15:19 UTC
We need a GDB backtrace to investigate. Please look here for details :

http://www.digikam.org/contrib
Comment 4 caulier.gilles 2015-06-30 08:07:56 UTC
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?
Comment 5 caulier.gilles 2015-08-20 06:50:10 UTC
digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.

Gilles Caulier
Comment 6 Marcus 2015-08-20 08:14:43 UTC
Hello! For some reason I never got any message that I got answers here. Sorry for never answering you!

I have installed 4.12.0. I have some tags double so I was changing tags like Albert into Albert. The first tag Albert is under the tag people, the second under Personen (the german word for people). Actually I am changing from People/Albert to Personen/Albert. Before I beginn both tags have already pictures, so I can not move the tag. (Merge similar tags would be a good function actually)

Some tags have quite a lot of pictures tagged with it. I let the metadata write in the files and in the side files. Writing in RAW is disabled. 

Before the change of the tag is stored I continue with the next double exisiting tag, lets say People/Berta to Personen/Berta. And so on. After a while digikam crashes. Than digikam gets more sensible and crashes earlier. I think while crashing the tags are not written into the files, but stored into the database.

That is the same behavior digikam has since some versions. It was getting more usable with newer version, but crashing during tagging appeared with every version installed on this (my only) computer.

I have no time to further research this question or install the software for a backtrace at the moment. Sorry, I only maybe later can come back on this problem. :-(
Comment 7 caulier.gilles 2015-08-20 08:21:58 UTC
People tags a relevant of libkface database, not main digiKam database.

libkface have been fixed in the past to fix several commits problem which can corrupt DB integrity.

Solution : remove the libkface database file (you will lost people tags) and regenrate face tags from scratch.

About libkface DB file, read this :

http://api.kde.org/4.x-api/kdegraphics-apidocs/libs/libkface/libkface/html/index.html

Gilles Caulier
Comment 8 caulier.gilles 2016-07-14 09:21:48 UTC
With 5.0.0 stable release, this problem is not reproducible.
I close this file now. Don't hesitate to reopen if necessary.
Gilles Caulier