Version: (using KDE 3.5.10) OS: Linux Installed from: SuSE RPMs after opening digikam 0.10.0 I wnated to do some settings. Clicking on the menu item "settings" digikam crashes with the following statements: Anwendung: digiKam (digikam), Signal SIGSEGV [?1034h[Thread debugging using libthread_db enabled] [New Thread 0x7f9ee746b950 (LWP 7266)] [New Thread 0x7f9ee8483950 (LWP 7259)] [New Thread 0x7f9ee8c84950 (LWP 7258)] [New Thread 0x7f9eea0ff950 (LWP 7257)] [New Thread 0x7f9eea900950 (LWP 7256)] [New Thread 0x7f9eeb974950 (LWP 7250)] [New Thread 0x7f9ef4a9e950 (LWP 7249)] [New Thread 0x7f9ef429d950 (LWP 7248)] [New Thread 0x7f9ef8be6950 (LWP 7200)] [KCrash handler] #5 0x00007f9f004a86bc in ?? () from /lib64/libc.so.6 #6 0x00007f9f004aa891 in malloc () from /lib64/libc.so.6 #7 0x00007f9f004c2643 in ?? () from /lib64/libc.so.6 #8 0x00007f9f004b987f in wcsrtombs () from /lib64/libc.so.6 #9 0x00007f9f004679a1 in wcstombs () from /lib64/libc.so.6 #10 0x00007f9f050391e4 in ?? () from /usr/lib64/liblcms.so.1 #11 0x00007f9f05039bd6 in cmsTakeProductDesc () from /usr/lib64/liblcms.so.1 #12 0x00000000004844ef in Digikam::SetupICC::parseProfilesfromDir ( this=0x61cb8c0, files=<value optimized out>) at /usr/src/debug/digikam-0.10.0-rc1/utilities/setup/setupicc.cpp:618 #13 0x0000000000486668 in Digikam::SetupICC::fillCombos (this=0x61cb8c0, path=@0x7fff13690690, report=false) at /usr/src/debug/digikam-0.10.0-rc1/utilities/setup/setupicc.cpp:525 #14 0x0000000000487201 in Digikam::SetupICC::readSettings (this=0x61cb8c0, restore=<value optimized out>) at /usr/src/debug/digikam-0.10.0-rc1/utilities/setup/setupicc.cpp:476 #15 0x0000000000487895 in Digikam::SetupICC::slotToggledWidgets ( this=0x61cb8c0, t=true) at /usr/src/debug/digikam-0.10.0-rc1/utilities/setup/setupicc.cpp:708 #16 0x00000000004879af in Digikam::SetupICC::qt_metacall (this=0x61cb8c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff13690870) at /usr/src/debug/digikam-0.10.0-rc1/build/digikam/setupicc.moc:78 #17 0x00007f9f0b1a5454 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #18 0x00007f9f06a095a2 in QAbstractButton::toggled(bool) () from /usr/lib64/libQtGui.so.4 #19 0x00007f9f0678f916 in QAbstractButton::setChecked(bool) () from /usr/lib64/libQtGui.so.4 #20 0x0000000000486ec3 in Digikam::SetupICC::readSettings (this=0x61cb8c0, restore=<value optimized out>) at /usr/src/debug/digikam-0.10.0-rc1/utilities/setup/setupicc.cpp:463 #21 0x000000000048d12a in SetupICC (this=0x61cb8c0, parent=<value optimized out>, dialog=<value optimized out>) at /usr/src/debug/digikam-0.10.0-rc1/utilities/setup/setupicc.cpp:397 #22 0x000000000049d211 in Setup (this=0x7fff13691b90, parent=<value optimized out>, name=<value optimized out>, page=Digikam::Setup::LastPageUsed) at /usr/src/debug/digikam-0.10.0-rc1/utilities/setup/setup.cpp:214 #23 0x00000000005ec031 in Digikam::DigikamApp::setup (this=0xb47390, iccSetupPage=<value optimized out>) at /usr/src/debug/digikam-0.10.0-rc1/digikam/digikamapp.cpp:1963 #24 0x000000000060125d in Digikam::DigikamApp::qt_metacall (this=0xb47390, _c=QMetaObject::InvokeMetaMethod, _id=49, _a=0x7fff13691d30) at /usr/src/debug/digikam-0.10.0-rc1/build/digikam/digikamapp.moc:198 #25 0x00007f9f0b1a5454 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #26 0x00007f9f0647e527 in QAction::triggered(bool) () from /usr/lib64/libQtGui.so.4 #27 0x00007f9f0647ecf0 in QAction::activate(QAction::ActionEvent) () from /usr/lib64/libQtGui.so.4 #28 0x00007f9f0681631d in ?? () from /usr/lib64/libQtGui.so.4 #29 0x00007f9f0a6f7781 in KMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libkdeui.so.5 #30 0x00007f9f064d67a9 in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #31 0x00007f9f06818afb in QMenu::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #32 0x00007f9f064841bd in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #33 0x00007f9f0648c7fa in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #34 0x00007f9f0a642ccb in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #35 0x00007f9f0b191091 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #36 0x00007f9f0648bb98 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&) () from /usr/lib64/libQtGui.so.4 #37 0x00007f9f064f0214 in ?? () from /usr/lib64/libQtGui.so.4 #38 0x00007f9f064eea77 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4 #39 0x00007f9f06515214 in ?? () from /usr/lib64/libQtGui.so.4 #40 0x00007f9effd990db in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #41 0x00007f9effd9c8ad in ?? () from /usr/lib64/libglib-2.0.so.0 #42 0x00007f9effd9ca6b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #43 0x00007f9f0b1b94ef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #44 0x00007f9f065149bf in ?? () from /usr/lib64/libQtGui.so.4 #45 0x00007f9f0b18f9a2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #46 0x00007f9f0b18fb2d in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #47 0x00007f9f0b191ffd in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #48 0x000000000065f071 in main (argc=5, argv=0x7fff13694268) at /usr/src/debug/digikam-0.10.0-rc1/digikam/main.cpp:188
The crash appears in libcms not digiKam. Sound like you have an exotic icc color profil on your computer. Which digiKam version you use ? Marcel, if remember, you hav fixed something like that in KDE4. Right ? Gilles Caulier
I'm using digikam-0.10.0-rc1 in KDE 3.5.10 with the KDE4 runtime module (KDE 4.1.3) . A strange phenomenon appeared: I waited almost a minute or so after starting digikam and then I could use the settings. Following ICC profiles are set: workspace and monitor are set to 'AdobeRGB' and printer is set to 'Europe ISO Coated FOGRA27' Bernhard Breitenauer
Sound like a problem similar than this entry: https://bugs.kde.org/show_bug.cgi?id=152528 ...fixed by Marcel n current implementation from svn (not 0.10.0-rc2) Gilles Caulier
Bernhard, what is the status of this report? Still reproducible? Can you give us an update here? Andi
Bernhard, What's news about this entry. It still valid ? Gilles Caulier
Sorry for my late answer. I did a new intsallation of all required packages, including kde4-digikam. Now its functioning fine. Thanks for Your efforts. With regards Bernhard Breitenauer