segmentation fault ./digikam

Gilles Caulier caulier.gilles at gmail.com
Mon Jul 17 20:40:07 BST 2023


Le lun. 17 juil. 2023 à 17:55, Benoit <benoitlst at ouvaton.org> a écrit :
>
> Le vendredi 14 juillet 2023 à 23:11 +0200, Maik Qualmann a écrit :
> > The gdb "list" command is wrong, use "bt" for the backtrace.
> >
>
> Hello
>
> (gdb) bt
> #0  0x00007ffff510c848 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
> #1  0x00007ffff4f52250 in QString::toUtf8_helper(QString const&) () from
> /lib/x86_64-linux-gnu/libQt5Core.so.5
> #2  0x00007ffff6a6df3d in
> Digikam::DPluginLoader::Private::appendPlugin(QObject*, QPluginLoader*) () from
> /div/digikam/digikam-build14-07-2023/bin/libdigikamcore.so.8.1.0
> #3  0x00007ffff6a6eacf in Digikam::DPluginLoader::Private::loadPlugins() ()
> from /div/digikam/digikam-build14-07-2023/bin/libdigikamcore.so.8.1.0
> #4  0x00007ffff780324c in Digikam::DigikamApp::DigikamApp() () from
> /div/digikam/digikam-build14-07-2023/bin/libdigikamgui.so.8.1.0
> #5  0x0000555555559e37 in main ()
>
>
> I've compiled without MEDIAPLAYER without ffmpeg, isn't that the reason?

Not at all. You have probably older digiKam plugins installed that the
application tries to load at start up. due to not compatible binary
version it crash

You must clean up your digiKam installation on your system.

Gillles Caulier


More information about the Digikam-users mailing list