[Digikam-devel] [Bug 267686] digiKam crashed while moving pictures

Axel Krebs axel.krebs at t-online.de
Sun Sep 4 18:54:42 BST 2011


--- Comment #5 from Axel Krebs <axel krebs t-online de>  2011-09-04 17:54:41 ---
Am 04.09.2011 17:03, schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=267686
> Gilles Caulier <caulier.gilles at gmail.com> changed:
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |axel.krebs at t-online.de
> --- Comment #4 from Gilles Caulier <caulier gilles gmail com>  2011-09-04 15:03:54 ---
> *** Bug 281322 has been marked as a duplicate of this bug. ***
I checked this bug, not finding enough fit...

Anyway, thank you for proving!


I assume DK has reached some limits from data-organsation: I change the
choosen directories, and DK seems to keep the total database. OK I read
that DK erases dead entries. But how can work with several
databases/directories, next startup with _other_ directories and so on??

I suggest strongly to reduce database extent to metadata per pic. Under
this pre-condition, it could change the choosen directiories anytime
without any limitations.

Besides I had no thumbnail-databate with more than 7 GB(!!) slowing down
each work progress.

Last argument to do pic-based date-management: this would increase the
data-safety enormously: in worst case, there would be "risk" of single
pictures, not on a comlete database.

I beg developers, tho thinks about this suggestion. It is a matter of
data-safety, speeding up, and flexibility.

Maybe you have a best-practise tutoral for similar needs as me?

Last question: where can I get the recommended version 2.1 ("git") from?
It is not in my launchpad-repositories...

Thank you,


Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the Digikam-devel mailing list