Bug 227075 - digikam3 database is not imported
Summary: digikam3 database is not imported
Status: RESOLVED DOWNSTREAM
Alias: None
Product: digikam
Classification: Applications
Component: Database-Sqlite (show other bugs)
Version: 1.1.0
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-15 21:41 UTC by hagg
Modified: 2017-07-26 05:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 1.2.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hagg 2010-02-15 21:41:54 UTC
Version:           1.1.0 (using KDE 4.3.3)
Compiler:          gcc (Gentoo 4.3.4 p1.0, pie-10.1.5) 4.3.4 
OS:                Linux
Installed from:    Gentoo Packages

All information in my digikam3.db, tags, ratings, album category e.t.c is missing after upgrading to kde4. I think this should be imported automatically when i start digikam and it finds a digikam3.db. Is this correct or did i miss something?

I checked the digikam3.db file with sqlite and it looks normal to me, nothing broken as far as i can see. 

I get a couple of error messages, but i think most of them are related to some unknown metadata formats (see list below). Maybe the last one is interesting:

QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-139025360' is still in use, all queries will cease to work.

I tried to google this one but could not find anything helpful.

Another message i got is this one:
Ihre Regionaleinstellungen wurden geändert, seitdem dieses Album das letzte Mal geöffnet wurde.
Alte Einstellung: ISO 8859-1, Neue Einstellung: ISO-8859-1

Since it changed from ISO 8859-1 to the same ISO with a dash after the ISO i guess it should not cause any problems with locating the correct file names.

I tried this initially with digikam-0.10.0 then i upgraded to the latest available in gentoo, but still the same effect.

Error log (extract, similar messages removed):
_______________________
Error: Offset of directory Sooo, entry 0x2001 is out of bounds: Offset = 0x003b7ff7; truncating the entry
Error: Directory Iop: Next pointer is out of bounds; ignored.
Warning: Directory Thumbnail, entry 0x0201: Data area exceeds data buffer, ignoring it.
Warning: Directory Image, entry 0x0001 has unknown Exif (TIFF) type 0; setting type size 1.
Warning: XMP toolkit support not compiled in.
Warning: Failed to decode XMP metadata.
Error: Directory Sooo: Next pointer is out of bounds; ignored.
Error: Directory Unknown with 8528 entries considered invalid; not read.
Error: Directory Canon: Next pointer is out of bounds; ignored.
Error: Directory Unknown with 52323 entries considered invalid; not read.
Warning: Directory Thumbnail, entry 0x0201: Data area exceeds data buffer, ignoring it.
Error: Directory Sooo: Next pointer is out of bounds; ignored.
Warning: Directory Sooo, entry 0xffff has unknown Exif (TIFF) type 65535; setting type size 1.
Error: Directory Sooo, entry 0xffff has invalid size 4278190079*1; skipping entry.
Warning: Directory Sooo, entry 0xafb8 has unknown Exif (TIFF) type 16333; setting type size 1.
Error: Offset of directory Sooo, entry 0xafb8 is out of bounds: Offset = 0xfc317e8a; truncating the entry
Error: Directory Iop: Next pointer is out of bounds; ignored.
Warning: Nicht unterstütztes Datumsformat
Warning: XMP toolkit support not compiled in.
Warning: Failed to decode XMP metadata.
Error: Directory Sooo: Next pointer is out of bounds; ignored.
QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-139025360' is still in use, all queries will cease to work.
Comment 1 Marcel Wiesweg 2010-02-16 19:03:53 UTC
When did you upgrade the first time from 0.9: Now or with an older version?
In which folder is your digikam3.db? Was a digikam4.db in the same folder at the first start after upgrading?
Comment 2 hagg 2010-02-18 00:18:12 UTC
First upgrade was with digikam-0.10.0 which did not work, then i tried with 1.1.0. In between i removed the newly created digikam4.db and replaced the digikam3.db with a copy i did before any upgrade. After the upgrade i had both, a digikam3.db and a digikam4.db in the folder.

The original location of digikam3.db was on a NFS share. Then i discovered that this might be a problem. I copied the digikam3.db to a local directory and did the import from this directory, e.g. specifying the local directory as the database location. Same result.

The first run wizard has two choices:
 1. use the old digikam3.db
      after this i have a digikam4.db and a digikam3.db
 2. create a new database
      after this i have a digikam4.db and a
       digikam3.db-backup-2010-02-17T23:43:59

with the 1. option i see some more things in the reporting window such as
   ...
   database copied
   ...

So the import somehow seems to start. But then looking at the digikam4.db (.dump Tags) my tags are not there. However, there are 2 tags listed, maybe from tags that are stored in the pictures.
Comment 3 Marcel Wiesweg 2010-02-18 17:24:55 UTC
Well something is going wrong here, and I suspect your digikam3.db is not found by the updating process, because neither the Tags nor the ImageTags table is touched by the upgrade procedure.
Please note that digikam3.db always needed to be in the same directory as the contained pictures.
Please check the path of the 0.9 collection and the "Album Path" and "Database File Path" entries in the [Album Settings] section of .kde4/share/config/digikamrc.
Album Path should, IIRC, point to the directory containing database and pictures.
Comment 4 hagg 2010-02-26 22:11:42 UTC
Thanks for the hint, the problem was as follows: My kde3 configuration used a symbolic link to the data while the kde4 configuration used the real path to the data. As a consequence digikam3.db was found but not the data referenced in the database file.

After fixing this i got another problem. While the album thumbnails are there, all JPEG's are missing when i start digikam. All movies are found. I checked the digikam4.db and found that the entries in ImageInformation are missing (they are only found for new pictures not in the kde3 database). When i add such an entry manually:
 INSERT INTO "ImageInformation" VALUES(8670,0,'2009-12-01T17:14:02','2009-12-01T17:14:02',1,2592,1944,'JPG',8,5);

the picture becomes visible in digikam. 

Do i maybe have a too old database?

sqlite> .dump Settings
...
 INSERT INTO "Settings" VALUES('DBVersion','1');
 INSERT INTO "Settings" VALUES('UpgradedFromSqlite2','yes');
...
Comment 5 Marcel Wiesweg 2010-02-26 22:33:54 UTC
Yes this is a known problem, bug #226853.
It's fixed for 1.2.0.