Summary: | Baloo crashes during tagging | ||
---|---|---|---|
Product: | [Unmaintained] Baloo | Reporter: | Piotr <piotergmoter> |
Component: | General | Assignee: | Vishesh Handa <me> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | screen shot of digikam progress bar |
Description
Piotr
2015-05-31 09:33:35 UTC
Created attachment 92931 [details]
screen shot of digikam progress bar
Comment on attachment 92931 [details]
screen shot of digikam progress bar
The writing means: 'Saving metadata to files'
So the bug is outside digikam. What can I do to make digikam usable 'now'? PS The debug info I have sent was usefull? How have you discovered the origin of the bug ;-)? It crash in Qt Sqlite database plugin, especially in SQlite code... You must update sqlite3 AND Qt4 Sqlite plugin... Gilles Caulier Well, I'm on LTS Kubuntu and rely on their packages. SQLlite is not updated there. Not good. Are package maintainers of the sqlite3 and qt4 plugin aware of the problem? Ho, i just seen this in the GDB backtrace : #16 0x00007f2fe03b562c in Baloo::FileModifyJob::doStart (this=0x7f2f5c014fc0) at ../../../../src/file/lib/filemodifyjob.cpp:113 In fact, it's not the digiKam Database which is broken, but the Baloo DB. Go to setup/Metadata/Baloo dialog page and disable Baloo support. This must fix your problem. I forward this file to Baloo... Gilles Caulier Baloo... https://bugs.kde.org/show_bug.cgi?id=348417 Baloo is to young to work reliably I'm afraid. I can confirm that the problem after disabling baloo has gone. And I was on heavy tagging task ;-) Sorry baloo... Fixed with Baloo KF5. |