Re: Debugging digikam
Gilles Caulier <[email protected]> Thu, 19 Jan 2023 09:09:25 +0100
| Newsgroups | gmane.comp.kde.digikam.devel |
|---|---|
| Message-ID | <CAHFG6sF1HMEw=N6sDWOB6BG5+giWe_63cGzKSNn8sw18NF1xZA@mail.gmail.com> |
Please capture the whole command line debug trace from a console when you start digiKam. Just to see if the message is more informative at this place against the GUI. Gilles Caulier Le mer. 18 janv. 2023 à 15:37, Martin Marmsoler <[email protected]> a écrit : > > > > The error message I get is: Could not open the configuration file <b></b>. This file is installed with the digikam application and is absolutely required to run digikam. Please check your installation. > > BR, > Martin > > Am Mi., 18. Jan. 2023 um 15:24 Uhr schrieb Martin Marmsoler <[email protected]>: >> >> Hi Maik, >> >> thanks for the response. I uninstalled digikam for now to not have those plugins installed. Now it fails during initialization of the database in main.cpp: >> >> AlbumManager::instance()->setDatabase(params, !commandLineDBPath.isNull(), firstAlbumPath) >> returns false because of "ScanController::AbortImmediately" >> >> Lokale Variablen >> aboutData @0x7fffffffe1b8 KAboutData >> app @0x7fffffffe210 QApplication >> argc 1 int >> argv <ein Element> char ** >> commandLineDBPath "" QString >> config @0x7fffffffe1d0 KSharedConfig::Ptr >> digikam 0x0 Digikam::DigikamApp* >> firstAlbumPath "" QString >> group @0x7fffffffe220 KConfigGroup >> iconTheme "" QString >> mainConfig @0x7fffffffe230 KConfigGroup >> params @0x7fffffffe280 Digikam::DbEngineParameters >> connectOptions "" QString >> databaseNameCore "/home/$USER/Dokumente/Festplatte/database/digikam4.db" QString >> databaseNameFace "/home/$USER/Dokumente/Festplatte/database/recognition.db" QString >> databaseNameSimilarity "/home/$USER/Dokumente/Festplatte/database/similarity.db" QString >> databaseNameThumbnails "/home/$USER/Dokumente/Festplatte/database/thumbnails-digikam.db" QString >> databaseType "QSQLITE" QString >> hostName "" QString >> internalServer false bool >> internalServerDBPath "" QString >> internalServerMysqlAdminCmd "" QString >> internalServerMysqlInitCmd "" QString >> internalServerMysqlServCmd "" QString >> password "" QString >> port -1 int >> userName "" QString >> walMode false bool >> parser @0x7fffffffe1c0 QCommandLineParser >> ret -1076182377 int >> system @0x7fffffffe200 Digikam::SystemSettings >> version "8.0.0-beta1" QString >> Inspector >> Ausdrücke >> Rückgabewert >> Tooltip >> >> Best regards, >> Martin >> >> Am Mo., 16. Jan. 2023 um 19:51 Uhr schrieb Maik Qualmann <[email protected]>: >>> >>> You still have "old" plugins in the directory. A possible path is "/usr/lib64/ >>> qt5/plugins/digikam/". Check the files in the folders based on the date, which >>> plugins were not last updated and delete them. Due to the API change (help doc >>> added), loading the "old" plugins crashes. >>> >>> Maik >>> >>> Am Montag, 16. Januar 2023, 17:28:35 CET schrieb Martin Marmsoler: >>> > Hello, >>> > >>> > I am trying currently to debug digikam. So far building worked fine and >>> > also debugging works. >>> > (For setup I used bootstrap.local) >>> > But when the application opens, it fails with a segmentation fault: >>> > >>> > 3 QString::toUtf8() const & qstring.h 684 >>> > 0x7ffff5e630a2 >>> > 4 KConfigGroup::readEntry<bool> kconfiggroup.h 260 >>> > 0x7ffff5e6331f >>> > 5 Digikam::DPluginLoader::Private::appendPlugin dpluginloader_p.cpp 161 >>> > 0x7ffff61f2b8c >>> > 6 Digikam::DPluginLoader::Private::loadPlugins dpluginloader_p.cpp 223 >>> > 0x7ffff61f34cb >>> > 7 Digikam::DPluginLoader::init dpluginloader.cpp 62 >>> > 0x7ffff61ef768 >>> > 8 Digikam::DigikamApp::DigikamApp digikamapp.cpp 137 >>> > 0x7ffff775a811 >>> > 9 main main.cpp 402 >>> > 0x55555555a712 >>> > >>> > >>> > commit id: d3e3a6c2e986bd35e47654824d62345374f67c5e (master 15.01.2023) >>> > >>> > Do you have an idea why it crashes? >>> > >>> > BR, >>> > Martin >>> >>> >>> >>>