Bug 351679

Summary: digikam does not find album library
Product: [Applications] digikam Reporter: Peter Glässel <glassel>
Component: Setup-CollectionsAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: grave CC: caulier.gilles
Priority: NOR    
Version: 3.5.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 4.13.0

Description Peter Glässel 2015-08-24 08:24:39 UTC
digikam had worked before with an album collection.
Now, on start, digikam gives the error message:
'No album library path has been found in the configuration file. Giving up the schema updating process. Please try with an empty database, or repair your configuration.'
After proceeding with 'ok', I tried to add a local collection in Settings->'configure digikam'. The previously used path  (on main system harddisk) is remembered. When trying to add this collection path ('ok'), the
message is: 'It was not possible to add a collection for the following paths: <name of path>'.
There is write access to the path. Trying other path names also fails.
Comment 1 caulier.gilles 2015-08-24 18:54:20 UTC
update to last 4.12.0 instead 3.5.0 and try again...

3.5.0 is very old now.

Gilles Caulier
Comment 2 Peter Glässel 2015-08-28 15:28:56 UTC
(In reply to Gilles Caulier from comment #1)
> update to last 4.12.0 instead 3.5.0 and try again...
> 
> 3.5.0 is very old now.
> 
> Gilles Caulier

updated to 4.12. Problem persists, no change in behaviour. What next? I am on
Ubuntu 14.04 LTS, by the way.

Regards ... Peter Glassel
Comment 3 caulier.gilles 2015-08-28 16:38:25 UTC
Follow instructions at "For hangs out or dysfunctions" section from https://www.digikam.org/contrib

Gilles Caulier
Comment 4 Peter Glässel 2015-08-29 07:23:08 UTC
(In reply to Gilles Caulier from comment #3)
> Follow instructions at "For hangs out or dysfunctions" section from
> https://www.digikam.org/contrib
> 
> Gilles Caulier

In the debug output there was a mention of database type 4 converted to 7. I removed the old database and digikamrc and started from scratch. Took quite a while to rebuild the database, but now everything works again.