Update schema version 4 to 5 failed - "connection 'ConnectionTest' is still in use"

[Helmut Steeb]

Hi,

following the advice in the message below shown by digikam (after I
rebooted, compacted the database in the Firefox SQLite manager,
re-installed digiKam, searching for the error message in the web - to no
effect):

Die Aktualisierung des Schemas von Version 4 nach 5 ist durch einen für
das Programm unerwarteten Fehler fehlgeschlagen. Sie können Ihre alte
Datenbank wegwerfen und mit einer leeren neu anfangen. In diesem Fall
verschieben Sie bitte die Datenbankdateien „digikam3.db“ und
„digikam4.db“ aus dem Ordner „XXX“. Höchstwahrscheinlich möchten Sie
aber lieber diesen Fehler an die Mailingliste [hidden email] (auf
Englisch) berichten. Betrachten Sie bitte zusätzlich, was digiKam auf
der Konsole ausgibt.

$ /usr/bin/digikam --version
Qt: 4.7.0
KDE: 4.5.1 (KDE 4.5.1)
digiKam: 1.4.0


$ /usr/bin/digikam
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is
still in use, all queries will cease to work.
Time elapsed: 28 ms
Model: Time elapsed: 67 ms
TextureColorizer: Time elapsed: 39 ms
Time elapsed: 3 ms
Model: Time elapsed: 88 ms
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed:
Datei oder Verzeichnis nicht gefunden
QFileSystemWatcher: failed to add paths: /home/helmut/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon


$ sudo apt-get install libkdcraw8
...
$ sudo apt-get install libkexiv2-8
...
libkexiv2-8 ist schon die neueste Version.
$ sudo apt-get install libkipi7
...
libkipi7 ist schon die neueste Version.


Thanks,
Helmut
--
Helmut Steeb
[hidden email] (akt. Jahr einsetzen / insert current year)
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

Hi,

ok,
from which digikam version did you upgrade to which version?
Or did you not upgrade at all, but the error appeared from nowhere?

I assume you have valuable information in the database, such as tags ratings
or comments not written to the image files' metadata?

As it says, the error is unexpected, meaning it normally does not occur,
unless there is some sort of damage or other error.
Did you have any harddisk problems?

How large is the database? If it's not too much, you can send it to me by
private mail for inspection.

Marcel
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Helmut Steeb]

Hi,

thanks for quick reply!

The error appeared from nowhere. I have no idea why digikam would update
its schema from 4 to 5 right now.

I upgraded digikam a month ago:

  dpkg.log.1:2010-12-27 13:26:03 upgrade digikam 2:1.2.0-0ubuntu2
2:1.4.0-0ubuntu1

... but it still worked without a problem (database time-stamp is
2011-01-13).

The database is ca. 3MB, 11K files. I guess that's too much to send?
I have no valuable info in there (except some 30 ratings and some test
tags).
I have no known harddisk problems.

I'm just shocked by the software that advices me first to throw away the
database. I've been using digiKam for years just to download images from
the camera - only this january I had a closer look to use it for
managing the images, read half of the manual :-) and added some first
ratings. Now if this happens from nowhere, I hesitate to start entering
real comments and ratings :-(

Via google I found some notice where "connection 'ConnectionTest' is
still in use..." was a bug (object de-construction), or an issue of
library incompatibility. Therefore I checked libkdcraw8 etc., but the
libraries seem current.

Helmut



Am 24.01.2011 13:54, schrieb Marcel Wiesweg:

> Hi,
>
> ok,
> from which digikam version did you upgrade to which version?
> Or did you not upgrade at all, but the error appeared from nowhere?
>
> I assume you have valuable information in the database, such as tags ratings
> or comments not written to the image files' metadata?
>
> As it says, the error is unexpected, meaning it normally does not occur,
> unless there is some sort of damage or other error.
> Did you have any harddisk problems?
>
> How large is the database? If it's not too much, you can send it to me by
> private mail for inspection.
>
> Marcel

--
Helmut Steeb
[hidden email] (akt. Jahr einsetzen / insert current year)
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

> The error appeared from nowhere. I have no idea why digikam would update
> its schema from 4 to 5 right now.
>
> I upgraded digikam a month ago:
>
>   dpkg.log.1:2010-12-27 13:26:03 upgrade digikam 2:1.2.0-0ubuntu2
> 2:1.4.0-0ubuntu1
>
> ... but it still worked without a problem (database time-stamp is
> 2011-01-13).

Ok, probably the database file is damaged somehow. Good that you dont have
valuable information in there. One would think that Sqlite it very safe, and I
assume it is, but very rarely something like this seems to happen.

>
> The database is ca. 3MB, 11K files. I guess that's too much to send?
> I have no valuable info in there (except some 30 ratings and some test
> tags).
> I have no known harddisk problems.

For me it's all right to receive this by mail. Not via the mailing list of
course.

>
> Via google I found some notice where "connection 'ConnectionTest' is
> still in use..." was a bug (object de-construction), or an issue of
> library incompatibility. Therefore I checked libkdcraw8 etc., but the
> libraries seem current.

You can completely ignore this ConnectionTest message.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

> Ok, probably the database file is damaged somehow. Good that you dont have
> valuable information in there. One would think that Sqlite it very safe, and I
> assume it is, but very rarely something like this seems to happen.

I have seen it once (Linux on netbook).

I think it was related to multiple instances of Digikam starting up at
the same time. (Ow was it digikam failure to close up?)

If I remember correctly was able to recover from situation just by
adding required entries to settings table using SQLite browser.

Gert
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel