[Digikam-devel] [Bug 276052] New: Failed to update the database schema from version 5 to version 6

[Frederic Grelot]

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

           Summary: Failed to update the database schema from version 5 to
                    version 6
           Product: digikam
           Version: 2.0.0
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: Database
        AssignedTo: digikam-devel at kde.org
        ReportedBy: fredericg_99 at yahoo.fr


Version:           2.0.0 (using KDE 4.6.4) 
OS:                Linux

Since my upgrading from 1.9.0 to 2.0.0b6, when I launch digikam, I get the
following error :
"Failed to update the database schema from version 5 to version 6. Please read
the error messages printed on the console and report this error as a bug at
bugs.kde.org."
There is nothing but this on the console :
>QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work.
>digikam(20875)/digikam (core): Schema update to V6 failed! 
the first one (connection still in use) was already present before the upgrade.

Once digikam is started, my collections are lost. If I add them, the images get
scanned (long process), and my collections are back. Fortunately, tags and
ratings are not lost. However, I must do it at every launch and it lasts few
minutes (between 2 and 5 minutes are necessary to scan my collections...).

I marked this bug as "causes data loss", since the collection list is lost...
However, manually adding the collection back "recovers" the data...

Reproducible: Always

Steps to Reproduce:
Install and create everything with 1.9.0, then install 2.0.0b6 and start
digikam

Actual Results:  
The above-mentioned message appears


I built and installed digikam 2.0.0b6 from tarball.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.