Digikam worked fine for ages. Since I upgraded to 0.8, merely everything
fails, finally resulting in a crash upon startup. KDE gives me the following debugging log: <<< (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) [...] (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1238931776 (LWP 6998)] (no debugging symbols found) [...] (no debugging symbols found) [KCrash handler] #3 0xb7d0248c in sqlite3pager_lookup () from /usr/lib/libsqlite3.so.0 #4 0xb7ceaddf in sqlite3BtreePrevious () from /usr/lib/libsqlite3.so.0 #5 0xb7ceaf27 in sqlite3BtreePrevious () from /usr/lib/libsqlite3.so.0 #6 0xb7cec2f4 in sqlite3BtreePrevious () from /usr/lib/libsqlite3.so.0 #7 0xb7ceb553 in sqlite3BtreePrevious () from /usr/lib/libsqlite3.so.0 #8 0xb7ceccd8 in sqlite3BtreeInsert () from /usr/lib/libsqlite3.so.0 #9 0xb7d173e5 in sqlite3VdbeExec () from /usr/lib/libsqlite3.so.0 #10 0xb7d19b8c in sqlite3_step () from /usr/lib/libsqlite3.so.0 #11 0xb7dcc1fc in AlbumDB::execSql () from /usr/lib/libdigikam.so.0 #12 0xb7dcd025 in AlbumDB::addItem () from /usr/lib/libdigikam.so.0 #13 0xb7e2214b in ScanLib::storeItemInDatabase () from /usr/lib/libdigikam.so.0 #14 0xb7e22c10 in ScanLib::allFiles () from /usr/lib/libdigikam.so.0 #15 0xb7e22914 in ScanLib::allFiles () from /usr/lib/libdigikam.so.0 #16 0xb7e22914 in ScanLib::allFiles () from /usr/lib/libdigikam.so.0 #17 0xb7e22914 in ScanLib::allFiles () from /usr/lib/libdigikam.so.0 #18 0xb7e22914 in ScanLib::allFiles () from /usr/lib/libdigikam.so.0 #19 0xb7e23704 in ScanLib::findMissingItems () from /usr/lib/libdigikam.so.0 #20 0xb7e24329 in ScanLib::startScan () from /usr/lib/libdigikam.so.0 #21 0xb7dc0976 in AlbumManager::setLibraryPath () from /usr/lib/libdigikam.so.0 #22 0x08049f40 in main () >>> I have *absolutely no clue* what the problem is. Any ideas? stefan@bebakus:~$ digikam --version Qt: 3.3.5 KDE: 3.4.2 digiKam: 0.8.0 stefan@bebakus:~$ uname -a Linux bebakus 2.6.14-1-686 #1 Fri Oct 28 16:55:18 JST 2005 i686 GNU/Linux -- Stefan Walter | Graz, Austria http://www.steptrev.org "Batze spaare, Drämmli fahre!" _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Le Mardi 6 Décembre 2005 16:35, Stefan Walter a écrit :
> Digikam worked fine for ages. Since I upgraded to 0.8, merely everything > fails, finally resulting in a crash upon startup. KDE gives me the > following debugging log: > > <<< > (no debugging symbols found) > Using host libthread_db library "/lib/tls/libthread_db.so.1". > (no debugging symbols found) > [...] > (no debugging symbols found) > [Thread debugging using libthread_db enabled] > [New Thread -1238931776 (LWP 6998)] > (no debugging symbols found) > [...] > (no debugging symbols found) > [KCrash handler] > #3 0xb7d0248c in sqlite3pager_lookup () from /usr/lib/libsqlite3.so.0 > #4 0xb7ceaddf in sqlite3BtreePrevious () from /usr/lib/libsqlite3.so.0 > #5 0xb7ceaf27 in sqlite3BtreePrevious () from /usr/lib/libsqlite3.so.0 > #6 0xb7cec2f4 in sqlite3BtreePrevious () from /usr/lib/libsqlite3.so.0 > #7 0xb7ceb553 in sqlite3BtreePrevious () from /usr/lib/libsqlite3.so.0 > #8 0xb7ceccd8 in sqlite3BtreeInsert () from /usr/lib/libsqlite3.so.0 > #9 0xb7d173e5 in sqlite3VdbeExec () from /usr/lib/libsqlite3.so.0 > #10 0xb7d19b8c in sqlite3_step () from /usr/lib/libsqlite3.so.0 > #11 0xb7dcc1fc in AlbumDB::execSql () from /usr/lib/libdigikam.so.0 > #12 0xb7dcd025 in AlbumDB::addItem () from /usr/lib/libdigikam.so.0 > #13 0xb7e2214b in ScanLib::storeItemInDatabase () > from /usr/lib/libdigikam.so.0 > #14 0xb7e22c10 in ScanLib::allFiles () from /usr/lib/libdigikam.so.0 > #15 0xb7e22914 in ScanLib::allFiles () from /usr/lib/libdigikam.so.0 > #16 0xb7e22914 in ScanLib::allFiles () from /usr/lib/libdigikam.so.0 > #17 0xb7e22914 in ScanLib::allFiles () from /usr/lib/libdigikam.so.0 > #18 0xb7e22914 in ScanLib::allFiles () from /usr/lib/libdigikam.so.0 > #19 0xb7e23704 in ScanLib::findMissingItems () from > /usr/lib/libdigikam.so.0 #20 0xb7e24329 in ScanLib::startScan () from > /usr/lib/libdigikam.so.0 #21 0xb7dc0976 in AlbumManager::setLibraryPath () > from /usr/lib/libdigikam.so.0 > #22 0x08049f40 in main () > > > I have *absolutely no clue* what the problem is. digikam isn't compiled with debug information. You have certainly installed a package for your dist. Have you any information on a console (start digikam from a console) > > Any ideas? > > stefan@bebakus:~$ digikam --version > Qt: 3.3.5 > KDE: 3.4.2 > digiKam: 0.8.0 > > stefan@bebakus:~$ uname -a > Linux bebakus 2.6.14-1-686 #1 Fri Oct 28 16:55:18 JST 2005 i686 GNU/Linux bebakus is your linux dist name ? -- Gilles Caulier _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Gilles Caulier schrieb:
> digikam isn't compiled with debug information. You have certainly installed a > package for your dist. Have you any information on a console (start digikam >>from a console) it's the debian package: >>stefan@bebakus:~$ digikam --version >>Qt: 3.3.5 >>KDE: 3.4.2 >>digiKam: 0.8.0 >>stefan@bebakus:~$ uname -a >>Linux bebakus 2.6.14-1-686 #1 Fri Oct 28 16:55:18 JST 2005 i686 GNU/Linux > > bebakus is your linux dist name ? no, that's the name of my computer. The dist ist debian. -- Stefan Walter | Graz, Austria http://www.steptrev.org "Batze spaare, Drämmli fahre!" _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Tuesday 06 December 2005 18:30, Stefan Walter wrote:
r> Gilles Caulier schrieb: > > digikam isn't compiled with debug information. You have certainly installed a > > package for your dist. Have you any information on a console (start digikam > >>from a console) > > it's the debian package: > > >>stefan@bebakus:~$ digikam --version > >>Qt: 3.3.5 > >>KDE: 3.4.2 > >>digiKam: 0.8.0 You are using unstable, right? You are sure biten by the transitions going currently on in Debian. 0.8 was working fine some time ago in debian/sid. You can fix it by rebuilding from source. As root mkdir bld; cd bld; apt-get build-dep digikam apt-get -b source digikam deb -i digikam*.deb Ditto for digikamimageplugins and kipi-plugins. Or wait until the transition calm down. Digikam will soon be scheduled for rebuild. Achim > > >>stefan@bebakus:~$ uname -a > >>Linux bebakus 2.6.14-1-686 #1 Fri Oct 28 16:55:18 JST 2005 i686 GNU/Linux > > > > bebakus is your linux dist name ? > > no, that's the name of my computer. The dist ist debian. > > -- > Stefan Walter | Graz, Austria > http://www.steptrev.org > > "Batze spaare, Drämmli fahre!" > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > > -- To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it. -- [hidden email] _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |