Digikam crashes right on startup after the console messages as follows: (... lots of kipi.plugins loading ...) kipi.library: Loaded plugin "Smug" kipi.plugins: Reading data from kipirc file.. Could not resolve property : XMLID_8_ Could not resolve property : XMLID_12_ Could not resolve property : XMLID_13_ Could not resolve property : XMLID_14_ Could not resolve property : XMLID_8_ Could not resolve property : XMLID_12_ Could not resolve property : XMLID_13_ Could not resolve property : XMLID_14_ Could not resolve property : XMLID_8_ Could not resolve property : XMLID_12_ Could not resolve property : XMLID_13_ Could not resolve property : XMLID_14_ digikam.geoiface: ---- Speicherzugriffsfehler (Speicherabzug geschrieben) This happens exactly when in digikamrc, the following section is present: [Digikam Right Sidebar] Removing this section allows Digikam to start again. After closing it, the section changes as follows: [Digikam Right Sidebar] -ActiveTab=3 +ActiveTab=0 DigikamProperties Expanded=true FileProperties Expanded=true ItemProperties Expanded=true -Minimized=false +Minimized=true PhotographProperties Expanded=true -RestoreSize=-1 +RestoreSize=209 VideoProperties Expanded=true and subsequent starts are successful again. This file was written by Digikam upon exit, I did not modify it by myself. Partial backtrace: Thread 1 (Thread 0x7f3822ac7b80 (LWP 7551)): #0 0x00007f384f7d81d1 in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x00007f384a64c397 in ?? () from /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23 #2 0x00007f384a64cd30 in ?? () from /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23 #3 0x00007f384f805ea1 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 StacktraceTop: QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23 ?? () from /usr/lib/x86_64-linux-gnu/libmarblewidget-qt5.so.23 QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 Reproducible: Always
Sound like a Marble Widget problem when sidebar is set to show maps view at startup. Remember that Marble has plenty of plugins. The problem can be located in a 3rd party component Also, this will be interesting to see if stand alone marble application has same problem on your computer... Note : please specify which maps view is expected to see : GoogleMaps, OSM, or local ?
IIRC it was Marble with OSM. I don't remember ... is there any way to track it (eg. by activating more console debug output)? Which Marble standalone app should I try out? I still have the old config so I can try more debugging ...
I can confirm what Jens wrote, exactly the same behavior on my machine. I have Marble with OSM enabled. HP
Marble is also a stand alone application to study world maps. digiKam only use a shared widget from this application. Install marble application on your computer and run it with OSM map. If it crash too, the problem is definitively in Marble code (that i suspect in fact)... Gilles Caulier
Marble with OSM map works perfectly.
I also experience crash on startup with same last message: kipi.library: UI file : "/usr/share/kxmlgui5/kipi/kipiplugin_rajceui.rc" kipi.library: Loaded plugin "Rajce" kipi.plugins: Plugin_YandexFotki plugin loaded kipi.library: UI file : "/usr/share/kxmlgui5/kipi/kipiplugin_yandexfotkiui.rc" kipi.library: Loaded plugin "YandexFotki" kipi.plugins: Reading data from kipirc file.. digikam.geoiface: ---- Speicherzugriffsfehler (Speicherabzug geschrieben) @Jens: Which file is it where I can make thd modificaton to start again? Where is it? This happens exactly when in digikamrc, the following section is present: [Digikam Right Sidebar]
It's in digikamrc, either in $HOME/.kde/config or in .config/digikam (I think).
Thanks Jens, must have made a typo yesterday searching for digikamrc in home directory. There are two digikamrc one in .config and one in .kde/share/config. Reverting the first one to an older version helps - digikam is starting through again. I first changed the one in .kde/share/config with no success - crashes at some point. As a side note nautilus only finds the file in .config not and not in ./kde/share/config ... Thanks, I have a running system again. Georg
Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Version 7.1.0 resolved - Thanks