[Bug 253062] New: Database of 80, 000+ images wiped out

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: [hidden email]
        ReportedBy: [hidden email]


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.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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


Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #1 from Gilles Caulier <caulier gilles gmail com>  2010-10-03 10:21:10 ---
I recommend to update to 1.4.0 and try again.

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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


Claudio Piombetti <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #2 from Claudio Piombetti <bugzilla affari to>  2010-10-03 14:06:18 ---
Updated to 1.4.0.
No improvement, the same error notification pops up.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

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





--- Comment #3 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-10-04 15:29:42 ---
Then please give us the backtrace and necessary information surrounding your
crash

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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





--- Comment #4 from Gilles Caulier <caulier gilles gmail com>  2010-10-06 15:48:25 ---
Claudio,

Do you see comment #3 ?

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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





--- Comment #5 from Claudio Piombetti <bugzilla affari to>  2010-10-07 11:04:26 ---
Gilles,
Digikam still cannot access the database, still the same error notification,
but Digikam does not crash anymore. I have not applied any changes to the
program; however, the OS has downloaded its usual tons of updates via Update
Manager.

This is what I get when I launch Digikam from the shell:

claudio@claudio-aspire-ubuntu:~$ digikam
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QMetaObject::invokeMethod: No such method
KUniqueApplication::loadCommandLineOptionsForNewInstance()
kbuildsycoca4 running...
kbuildsycoca4(11343) KBuildSycoca::checkTimestamps: checking file timestamps
kbuildsycoca4(11343) KBuildSycoca::checkTimestamps: timestamps check ok
kbuildsycoca4(11343) kdemain: Emitting notifyDatabaseChanged ()
QMetaObject::invokeMethod: No such method
KUniqueApplication::loadCommandLineOptionsForNewInstance()
params.c:OpenConfFile() - Unable to open configuration file
"/home/claudio/.smb/smb.conf":
    No such file or directory
params.c:OpenConfFile() - Unable to open configuration file
"/home/claudio/.smb/smb.conf.append":
    No such file or directory
Time elapsed: 254 ms
Model: Time elapsed: 346 ms
TextureColorizer: Time elapsed: 71 ms
Time elapsed: 3 ms
Model: Time elapsed: 29 ms
QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-31947232' is
still in use, all queries will cease to work.
claudio@claudio-aspire-ubuntu:~$ klauncher(11339)/kio (KLauncher): SlavePool:
No communication with slave.

QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-9247856' is
still in use, all queries will cease to work.
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-9247856' is
still in use, all queries will cease to work.
QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-9247856' is
still in use, all queries will cease to work.
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
klauncher(11339)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(11339)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(11339)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(11339)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(11339)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(11339)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(11339)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(11339)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(11339)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(11339)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(11339)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(11339)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(11339)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(11339)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(11339)/kio (KLauncher): SlavePool: No communication with slave.

typingToSeeIfThisShellIsStillAlive
typingToSeeIfThisShellIsStillAlive: command not found
claudio@claudio-aspire-ubuntu:~$

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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





--- Comment #6 from Gilles Caulier <caulier gilles gmail com>  2010-10-07 11:08:05 ---
It's typically an error from digiKam kioslave which crash outside digiKam
(kioslaves are external process used to query database)

this problem can be due to a broken external dependencies for example.

look if you can see any error message relevant in your ~./.xsession-errors

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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





--- Comment #7 from Claudio Piombetti <bugzilla affari to>  2010-10-07 11:23:35 ---
Created an attachment (id=52304)
 --> (http://bugs.kde.org/attachment.cgi?id=52304)
.session-errors, 2010.10.07

At lines 86-87 there are entries related to Digikam:

Window manager warning: Invalid WM_TRANSIENT_FOR window 0x5200004 specified for
0x520001c (digiKam).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x5200004 specified for
0x52001ce (digiKam).

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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





--- Comment #8 from Gilles Caulier <caulier gilles gmail com>  2010-10-07 11:32:51 ---
No this warnings message are not important there...

run kdebugdialog and set all digikam debug spaces, especially kioslave.

try also to set on all "kio (*)" (not kio_*). look all report on the console
when you run digiKam

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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





--- Comment #9 from Claudio Piombetti <bugzilla affari to>  2010-10-07 21:28:58 ---
Created an attachment (id=52323)
 --> (http://bugs.kde.org/attachment.cgi?id=52323)
Digikam output

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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





--- Comment #10 from Gilles Caulier <caulier gilles gmail com>  2010-10-08 09:18:57 ---
It's clear :

digikam(7905)/digikam (core) Digikam::DatabaseCoreBackend::execDBAction: Error
while executing DBAction [ "CreateDB" ] Statement [ "CREATE TABLE AlbumRoots
                            (id INTEGER PRIMARY KEY,
                            label TEXT,
                            status INTEGER NOT NULL,
                            type INTEGER NOT NULL,
                            identifier TEXT,
                            specificPath TEXT,
                            UNIQUE(identifier, specificPath))" ]

Marcel, Why ???

Gilles

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

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





--- Comment #11 from Marcel Wiesweg <marcel wiesweg gmx de>  2010-10-08 09:42:46 ---
startUpdates: Have a database structure version  "0"

There is no such thing as a database version 0. The first digikam version
writing this value, 0.8, wrote "1". 0.10 to 1.5 use version "5", 2.0 "6".

Following this broken information we make an attempt to create tables, which
fails correctly because they already exist:
"table AlbumRoots already exists" "Unable to execute statement"

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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





--- Comment #12 from Gilles Caulier <caulier gilles gmail com>  2010-11-24 09:13:00 ---
digiKam 1.6.0 is out:

http://www.digikam.org/drupal/node/550

Please update and check if this entry still valid.

Thanks in advance

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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





--- Comment #13 from Claudio Piombetti <bugzilla affari to>  2010-12-18 18:24:31 ---
I tried to cause the error and the consequent database loss without success. I
tagged about two hundreds images (JPEGs, 5Mb each), Digikam proceeded very
slowly with the tagging; after about 20 minutes, its progress status ("Writing
metadata to files. Please wait...") was stuck at 66% or 67%. Killed Digikam
with the system monitor. Restarted, no database loss.

Good. This seems solved. Thank you! Shall I update the call status to Resolved
/ Fixed?

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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


Claudio Piombetti <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED




--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Version Fixed In|                            |1.8.0

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Version Fixed In|1.8.0                       |5.7.0
          Component|Database                    |Database-Albums

--- Comment #14 from [hidden email] ---
This problem is relevant of digiKam KIO Slaves and all of these have been
dropped in favor of a multi-threaded interface to query the database.

--
You are receiving this mail because:
You are the assignee for the bug.