Version: 0.7-beta1 (using KDE 3.3.1, Gentoo) Compiler: gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6) OS: Linux (i686) release 2.6.8-gentoo-r7 Digikam crashed when I selected my folder path, which was not writable by digikam. The following errors were printed in the console: digikam: WARNING: [void AlbumFolderView::loadAlbumState()] Failed to open albumtreestate.bin digikam: WARNING: [void AlbumDB::setDBPath(const QString&)] Cannot open database: unable to open database: /mnt/data-dump/fotos/digikam.db digikam: WARNING: [bool AlbumDB::execSql(const QString&, QStringList*, bool)] SQLite pointer == NULL digikam: WARNING: [bool AlbumDB::execSql(const QString&, QStringList*, bool)] SQLite pointer == NULL digikam: WARNING: [bool AlbumDB::execSql(const QString&, QStringList*, bool)] SQLite pointer == NULL digikam: WARNING: [bool AlbumDB::execSql(const QString&, QStringList*, bool)] SQLite pointer == NULL
Yes, i confirm this bug. I can reproduce it on my computer... Gilles Caulier
CVS commit by pahlibar: fixed crash when the album library path is unwritable. Note to users, at least make the album library path writable, otherwise none of the digikam tags or comments features will work. the actual photo directories don't have to be writable BUG: 91828 M +3 -0 albumdb.cpp 1.11 --- kdeextragear-3/digikam/digikam/albumdb.cpp #1.10:1.11 @@ -237,4 +237,7 @@ void AlbumDB::deleteAlbum(Album *a) void AlbumDB::readPAlbum(PAlbum *album) { + if (!m_db) + return; + QStringList values;
*** Bug 92624 has been marked as a duplicate of this bug. ***