[Digikam-devel] [Bug 253062] New: Database of 80, 000+ images wiped out
Claudio Piombetti
bugzilla at affari.to
Sat Oct 2 22:21:38 BST 2010
https://bugs.kde.org/show_bug.cgi?id=253062
Summary: Database of 80,000+ images wiped out
Product: digikam
Version: 1.2.0
Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: Database
AssignedTo: digikam-devel at kde.org
ReportedBy: bugzilla at affari.to
Created an attachment (id=52179)
--> (http://bugs.kde.org/attachment.cgi?id=52179)
Error message from Digikam regarding the schema updating process failure
Version: 1.2.0 (using KDE 4.4.5)
OS: Linux
After a crash, Digikam is left running as a zombie. Closing it and restarting
it, my database is gone. 80,000 pics.
Reproducible: Sometimes
Steps to Reproduce:
1) apply a tag to 200-300 hundred pics (JPEGs and Nikon D300 RAW files);
2) wait. It will crash;
3) after the crash, close Digikam using Force Quit (unless the program died
with an error message);
4) look at the system monitor, if Digikam is listed there as a zombie, kill it;
5) restart Digikam;
6) you will see an error message.
Actual Results:
Error message:
The schema updating process from version 4 to 5 failed, caused by an error that
we did not expect. You can try to discard your old database and start with an
empty one. (In this case, please move the database files "digikam3.db" and
"digikam4.db" from the directory "/home/claudio/Pictures"). More probably you
will want to report this error to (blah blah).
Click OK on the error window. Digikam starts, and instead of showing my album's
data structure, there is nothing, not one folder or image. All gone.
Expected Results:
Not to see my database wiped out for the umpteenth time in the last few weeks.
I do not know what I am doing wrong, if anything, but this is beginning to cost
me money and "face", since I have recommended Digikam on my websites.
--
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