Version: 1.0.0 (using KDE 4.3.4) Compiler: 4.4.2 OS: Linux Installed from: Ubuntu Packages I'm running a AMD 64 bit system. Digikam segfaults on all plugins except color manipulation plugins with the following message: Program received signal SIGSEGV, Segmentation fault. ... in QTextEngine::itemize () I've used all kinds of debugging (compiled debugfull, strace, gdb) but not more then the above message is coming out of it. I've seen similar bugreports for amarok and kmess (http://kmess.org/board/viewtopic.php?f=4&t=4234). They indicate a problem with oxygenrc. So when I change my Window theme to anything else then Oxygen, the segfault disappears and digiKam works perfect.
You could try this guide to get a better backtrace: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports (take a look at the GDB guide, have you used the "bt full" command on it ?) Ubuntu provides the "digikam-dbg" package (if you use the packaged version) Regards
I compiled the program myself. Here is a better backtrace: ... [Thread 0x7fffb3cc6910 (LWP 7056) exited] digikam(6955)/kdeui (kdelibs): Attempt to use QAction "editorwindow_zoomto" with KXMLGUIFactory! digikam(6955)/digikam (core) Digikam::DImg::load: "/home/gerhard/Pictures/Reisen/Australien/2009/IMG_3564.JPG" : JPEG file identified digikam(6955)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation => 1 digikam(6955)/digikam (core) Digikam::DMetadata::getIccProfile: Exif color-space tag is sRGB. Using default sRGB ICC profile. digikam(6955)/KEXIV2 KExiv2Iface::KExiv2::getImageOrientation: Orientation => Exif.Image.Orientation => 1 Program received signal SIGSEGV, Segmentation fault. 0x00007ffff22aea94 in QTextEngine::itemize (this=0x7596cc0) at text/qtextengine.cpp:1394 1394 text/qtextengine.cpp: No such file or directory. in text/qtextengine.cpp Current language: auto The current source language is "auto; currently c++". (gdb) thread apply all backtrace Thread 37 (Thread 0x7fffc1bdd910 (LWP 7049)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261 #1 0x00007ffff137966b in QWaitConditionPrivate::wait (this=<value optimized out>, mutex=0x3e01498, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87 #2 QWaitCondition::wait (this=<value optimized out>, mutex=0x3e01498, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:159 #3 0x00007ffff4f3bdaa in Digikam::LoadSaveThread::run (this=0x3e01480) at /home/gerhard/OSS/graphics4/digikam/libs/threadimageio/loadsavethread.cpp:131 #4 0x00007ffff13786b5 in QThreadPrivate::start (arg=0x3e01480) at thread/qthread_unix.cpp:244 #5 0x00007ffff10e9a04 in start_thread (arg=<value optimized out>) at pthread_create.c:300 #6 0x00007ffff06a805d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x0000000000000000 in ?? () Thread 36 (Thread 0x7fffc0bdb910 (LWP 7047)): #0 0x00007ffff069bc13 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007fffea6444fc in ?? () from /lib/libglib-2.0.so.0 #2 0x00007fffea644840 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x00007ffff1495053 in QEventDispatcherGlib::processEvents (this=0x438fce0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407 #4 0x00007ffff146a3e2 in QEventLoop::processEvents (this=<value optimized out>, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece. ) at kernel/qeventloop.cpp:149 #5 0x00007ffff146a7bc in QEventLoop::exec (this=0x7fffc0bdae80, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece. ) at kernel/qeventloop.cpp:201 #6 0x00007ffff1375c79 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:487 #7 0x00007fffca8e5c7c in Marble::GpsdThread::run (this=0x3908d70) at /home/gerhard/OSS/marble/src/plugins/positionprovider/gpsd/GpsdThread.cpp:27 #8 0x00007ffff13786b5 in QThreadPrivate::start (arg=0x3908d70) at thread/qthread_unix.cpp:244 #9 0x00007ffff10e9a04 in start_thread (arg=<value optimized out>) at pthread_create.c:300 #10 0x00007ffff06a805d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x0000000000000000 in ?? () Current language: auto The current source language is "auto; currently asm". Thread 35 (Thread 0x7fffbfbd9910 (LWP 7046)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261 #1 0x00007ffff137966b in QWaitConditionPrivate::wait (this=<value optimized out>, mutex=0x3ed6818, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87 #2 QWaitCondition::wait (this=<value optimized out>, mutex=0x3ed6818, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:159 #3 0x00007ffff4f3bdaa in Digikam::LoadSaveThread::run (this=0x3ed6800) at /home/gerhard/OSS/graphics4/digikam/libs/threadimageio/loadsavethread.cpp:131 #4 0x00007ffff13786b5 in QThreadPrivate::start (arg=0x3ed6800) at thread/qthread_unix.cpp:244 #5 0x00007ffff10e9a04 in start_thread (arg=<value optimized out>) at pthread_create.c:300 #6 0x00007ffff06a805d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #7 0x0000000000000000 in ?? () Current language: auto The current source language is "auto; currently c".
digiKam 1.0.0 is out since few days... http://www.digikam.org/drupal/node/491 Please try with this version coming with more than 400 bug-fixes. Thanks in advance Gilles Caulier
*** Bug 220292 has been marked as a duplicate of this bug. ***
For me this sounds like an upstream issue. Should we mark this as such?
yes it is Johannes. Let's go... Gilles
Not reproducible with digiKam 7.3.0 and Exiv2 0.27.4