Bug 265034 - Database corrupted after terminating frozen digikam
Summary: Database corrupted after terminating frozen digikam
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Migration (show other bugs)
Version: 1.8.0
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-01 02:31 UTC by Michal Thoma
Modified: 2017-07-26 17:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 2.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Thoma 2011-02-01 02:31:42 UTC
Version:           1.8.0 (using KDE 4.6.0) 
OS:                Linux

After digikam got frozen for unknown reason I terminated the proccess. Window appeared with message "Could not write to database." 

When starting application again, long dialog appears that database could not be converted from version 3 and 4 to 5. Terminal error output is as follows: QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work. 

Program then opens with no albums and I have to recover database from backup.

This happened for two times in two days since I upgraded to digikam 1.8.0 and KDE 4.6.

Reproducible: Sometimes
Comment 1 Martin Klapetek 2011-02-02 14:47:06 UTC
What were you doing just before it froze? Also, can you enable debug output (run kdebugdialog and enable all digiKam instances), run digiKam from console and when it freezes again, post the whole output here? Thanks!
Comment 2 Michal Thoma 2011-02-02 15:02:01 UTC
I don't have much idea as for the first time I was just checking running application and discovered 3 running instances of digikam while there were no windows. Second time I'm also unsure as I were actually working with RawTherapee adn Photoshop, digikam running at the background. I suspect the freezing could happened when I saved some new images from either RawTherapee or Adobe Photoshop and digikam attempted to automatically import that.

I will enable debugging as you suggest for case it happens again.
Comment 3 Francesco Riosa 2011-06-29 12:50:18 UTC
2.0.0-rc is out, please re-open if needed