Version: 1.6.0 (using KDE 4.5.4) OS: Linux Every time i try to start digikam, it crashes with "signal: Illegal instruction", as reported by the kcrash application. Reproducible: Always Steps to Reproduce: Just start digikiam Actual Results: crash with signal: illegal instruction I'm not sure, but i think that's is related to the newest opencv version (2.1) against which kipi-plugins are linked. As reported here: http://sacripante.wordpress.com/2010/04/02/opencv-2-0-0a-winxp-on-amd/ starting from version 2.0 opencv libraries are compiled with sse2 instructions, producing a code not executable on platform not supporting these extensions, as the athlon-xp i'm currently using.
Hi Giovanni, thanks for you report! Does KCrash give you any more detailed output, like a backtrace? If so, please also post it here! Michael
Created attachment 55270 [details] here's the kcrash generated backtrace
Well, the backtrace is not so useful because there are no debug-symbols applied, but at least we know the crash is in opencv, supporting your theory. If you want to get digikam to start without having to do a recompile: I think the only plugin that uses OpenCV is the Removed-Red-Eyes plugin. Therefore, you can simply, as root, rename the file: /usr/lib/kde4/kipiplugin_removeredeyes.so mv /usr/lib/kde4/kipiplugin_removeredeyes.so /usr/lib/kde4/kipiplugin_removeredeyes.so.disabled This way, the removedredeyes plugin should not be loaded, hence avoiding the crash for now. Michael
(In reply to comment #3) > > mv /usr/lib/kde4/kipiplugin_removeredeyes.so > /usr/lib/kde4/kipiplugin_removeredeyes.so.disabled > > This way, the removedredeyes plugin should not be loaded, hence avoiding the > crash for now. i've followed your suggestion and now digikam starts and seems usable. Thanks for the quick&dirty fix! G.
Since you get OpenCV from your distribution, you may want to ask them to provide OpenCV packages with optimizations set such that your CPU is supported. Otherwise, there is nothing more we can do about it... Michael
(In reply to comment #5) > Since you get OpenCV from your distribution, you may want to ask them to > provide OpenCV packages with optimizations set such that your CPU is supported. > Otherwise, there is nothing more we can do about it... i've already filed a bug against the package, but i was wondering if a solution was possible for the digikam package, stated the greater possible impact of this problem. But if the only possible solution in the opencv package, i will wait with crossed fingers... Giovanni
kipi-plugins 2.2.0 is out since few weeks. Crash still valid with this version ? Gilles Caulier
Giovanni, This file still valid using kipi-plugins 2.4 ? Gilles Caulier
Official Kipi-plugins 2.6.0 release is out since few days now : http://www.digikam.org/drupal/node/656 Please, check if this entry still valid, or update report accordingly. Thanks in advance. Gilles Caulier
No response, and crash is in opencv code.
Not reproducible with 7.2.0