[Digikam-devel] [Bug 277928] New: DigiKam fails to start properly, lost albums (schema updating process from version 4 to 5 failed)

[Steve Toledo-Brown]

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

           Summary: DigiKam fails to start properly, lost albums (schema
                    updating process from version 4 to  5 failed)
           Product: digikam
           Version: 1.9.0
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Database
        AssignedTo: digikam-devel at kde.org
        ReportedBy: stevetldbrwn at gmail.com


Version:           1.9.0
OS:                Linux

Earlier today I could start DigiKam as normal, but now it's reporting
errors as below on startup, and failing to show any of my albums.

"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/joint/Pictures".) More probably you will want to report this
error to the digikam-devel at kde.org mailing list. As well, please have a
look at what digiKam prints on the console."

An attempt to re-configure, re-adding the root album folder, failed immediately
- IIRC, there was an error message related to the database access.

After a reboot, I got the same error, but this time with the possible
improvement that re-adding the root album folder seemed to be working - I got
the progress dialog, which was reporting progress for the first few minutes.
However, when I came back after half an hour, the dialog was gone without any
root album folder being shown.



Reproducible: Sometimes

Steps to Reproduce:
Difficult to reproduce properly as I can't get any albums back into digikam.
I suspect that the problem may have been caused by having 2 userids
simultaneously trying to use digikam (same database). One of these userids also
had several digikam processes running simultaneously, due to the user not being
sure whether digikam had already started or not.
Bug 265034 may also be relevant, but I only killed (kill -9) digikam processes
after I had already experienced the problem.

Actual Results:  
see Details section

output from running digikam in the bash shell is:
KGlobal::locale::Warning your global KLocale is being recreated with a valid
main component instead of a fake component, this usually means you tried to
call i18n related functions before your main component was created. You should
not do that since it most likely will not work 
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
Time elapsed: 32 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 11 ms
Time elapsed: 2 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 12 ms
digikam(2979)/KIPI (general) Plugin_DebianScreenshots::setup: virtual void
Plugin_DebianScreenshots::setup(QWidget*) 
Time elapsed: 2 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 10 ms
Time elapsed: 1 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 10 ms
Time elapsed: 1 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 10 ms
digikam(2979)/digikam (core)
Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for 
Digikam::ImagePropertiesSideBarDB(0xb398850)  is empty. Returning the default
config group 
digikam(2979)/digikam (core)
Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for 
Digikam::ImagePropertiesSideBarDB(0xb5c2940)  is empty. Returning the default
config group 
digikam(2979) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
digikam(2979) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
digikam(2979) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
digikam(2979) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
digikam(2979) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
digikam(2979) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
digikam(2979) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
digikam(2979) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
digikam(2979) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
digikam(2979) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
digikam(2979) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
digikam(2979) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets! 
digikam(2979)/digikam (core)
Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for 
Digikam::Sidebar(0xb5c2940)  is empty. Returning the default config group 
digikam(2979)/digikam (core)
Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for 
Digikam::Sidebar(0xb398850)  is empty. Returning the default config group 
QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-158633776' is
still in use, all queries will cease to work.


Expected Results:  
Restart of digikam should maintain the albums structure.

sqlite integrity check appears OK :

$ sqlite3 /home/joint/Pictures/digikam4.db
SQLite version 3.7.4
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> pragma integrity_check;
ok

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