Bug 253091

Summary: digiKam will not launch
Product: [Applications] digikam Reporter: glen tyler <gtyler142>
Component: Plugin-DImg-RAWAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: caulier.gilles, giuseppe.vinci, jaqian, paulac.bur
Priority: NOR    
Version: 1.4.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In: 7.0.0
Sentry Crash Report:

Description glen tyler 2010-10-03 07:40:44 UTC 
Application: digikam (1.4.0)
KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 3"
Qt Version: 4.6.3
Operating System: Linux 2.6.34.7-0.3-default i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
digkam starts but then closes when clicked on

The crash can be reproduced every time.

 -- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
[Current thread is 1 (Thread 0xb2104740 (LWP 5378))]

Thread 2 (Thread 0xb0aafb70 (LWP 5379)):
[KCrash Handler]
#6  ref (this=0xb0aaef50, filePath=..., loadFlagsInt=1, observer=0x0, rawDecodingSettings=...) at /usr/include/QtCore/qatomic_i386.h:120
#7  QString (this=0xb0aaef50, filePath=..., loadFlagsInt=1, observer=0x0, rawDecodingSettings=...) at /usr/include/QtCore/qstring.h:715
#8  RawDecodingSettings (this=0xb0aaef50, filePath=..., loadFlagsInt=1, observer=0x0, rawDecodingSettings=...) at /usr/include/libkdcraw/rawdecodingsettings.h:46
#9  DRawDecoding (this=0xb0aaef50, filePath=..., loadFlagsInt=1, observer=0x0, rawDecodingSettings=...) at /usr/src/debug/digikam-1.4.0/libs/dimg/drawdecoding.h:49
#10 Digikam::DImg::load (this=0xb0aaef50, filePath=..., loadFlagsInt=1, observer=0x0, rawDecodingSettings=...) at /usr/src/debug/digikam-1.4.0/libs/dimg/dimg.cpp:434
#11 0xb680f8d8 in Digikam::DImg::loadImageInfo (this=0xb0aaef50, filePath=..., loadMetadata=false, loadICCData=false, loadUniqueHash=false) at /usr/src/debug/digikam-1.4.0/libs/dimg/dimg.cpp:331
#12 0xb66755be in Digikam::ImageScanner::loadFromDisk (this=0xb0aaef40) at /usr/src/debug/digikam-1.4.0/libs/database/imagescanner.cpp:593
#13 0xb667b0b2 in Digikam::ImageScanner::newFile (this=0xb0aaef40, albumId=2) at /usr/src/debug/digikam-1.4.0/libs/database/imagescanner.cpp:99
#14 0xb6627163 in Digikam::CollectionScanner::scanNewFile (this=0xb0aaf2c0, info=..., albumId=2) at /usr/src/debug/digikam-1.4.0/libs/database/collectionscanner.cpp:768
#15 0xb6628a64 in Digikam::CollectionScanner::scanAlbum (this=0xb0aaf2c0, location=..., album=...) at /usr/src/debug/digikam-1.4.0/libs/database/collectionscanner.cpp:673
#16 0xb66286d9 in Digikam::CollectionScanner::scanAlbum (this=0xb0aaf2c0, location=..., album=...) at /usr/src/debug/digikam-1.4.0/libs/database/collectionscanner.cpp:691
#17 0xb66293ce in Digikam::CollectionScanner::scanAlbumRoot (this=0xb0aaf2c0, location=...) at /usr/src/debug/digikam-1.4.0/libs/database/collectionscanner.cpp:485
#18 0xb6629689 in Digikam::CollectionScanner::completeScan (this=0xb0aaf2c0) at /usr/src/debug/digikam-1.4.0/libs/database/collectionscanner.cpp:254
#19 0x082f9527 in Digikam::ScanController::run (this=0x852c648) at /usr/src/debug/digikam-1.4.0/digikam/scancontroller.cpp:540
#20 0xb4dca04f in ?? () from /usr/lib/libQtCore.so.4
#21 0xb4622b25 in start_thread () from /lib/libpthread.so.0
#22 0xb4b1e46e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb2104740 (LWP 5378)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb4627125 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb4b2c24c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6
#3  0xb4dca710 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#4  0xb4dc96e1 in QThread::wait(unsigned long) () from /usr/lib/libQtCore.so.4
#5  0x082f7199 in Digikam::ScanController::shutDown (this=0x852c648) at /usr/src/debug/digikam-1.4.0/digikam/scancontroller.cpp:290
#6  0x082fa6ee in Digikam::ScanController::~ScanController (this=0x852c648, __in_chrg=<value optimized out>) at /usr/src/debug/digikam-1.4.0/digikam/scancontroller.cpp:273
#7  0x082fa907 in ~ScanControllerCreator () at /usr/src/debug/digikam-1.4.0/digikam/scancontroller.cpp:221
#8  destroy () at /usr/src/debug/digikam-1.4.0/digikam/scancontroller.cpp:222
#9  0xb4a797cf in __run_exit_handlers () from /lib/libc.so.6
#10 0xb4a7982d in exit () from /lib/libc.so.6
#11 0xb53ec7e8 in ?? () from /usr/lib/libQtGui.so.4
#12 0xb5ddc2a9 in KApplication::xioErrhandler(_XDisplay*) () from /usr/lib/libkdeui.so.5
#13 0xb5ddc2e4 in ?? () from /usr/lib/libkdeui.so.5
#14 0xb47a9504 in _XIOError () from /usr/lib/libX11.so.6
#15 0xb47b02b8 in ?? () from /usr/lib/libX11.so.6
#16 0xb47b070c in _XEventsQueued () from /usr/lib/libX11.so.6
#17 0xb47992e8 in XEventsQueued () from /usr/lib/libX11.so.6
#18 0xb5427fd5 in ?? () from /usr/lib/libQtGui.so.4
#19 0xb2ebf7d0 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#20 0xb2ec0108 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0xb2ec060e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0xb4eefd4b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#23 0xb542819a in ?? () from /usr/lib/libQtGui.so.4
#24 0xb4ec311d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#25 0xb4ec3319 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#26 0x082f751f in Digikam::ScanController::completeCollectionScan (this=0x852c648, splash=0x857ca18) at /usr/src/debug/digikam-1.4.0/digikam/scancontroller.cpp:377
#27 0x082ab8aa in Digikam::DigikamApp::DigikamApp (this=0x85ac0b0, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /usr/src/debug/digikam-1.4.0/digikam/digikamapp.cpp:197
#28 0x0836ae7a in main (argc=) at /usr/src/debug/digikam-1.4.0/digikam/main.cpp:172

Possible duplicates by query: bug 250477, bug 246065, bug 244188, bug 244142, bug 243011.

Reported using DrKonqi
Comment 1 caulier.gilles 2010-10-03 10:25:37 UTC 
This is a crash due to a binary uncompatibility of libkdcraw on your system. Please update this library. It sound like a package problem.

Gilles Caulier
Comment 2 Martin Klapetek 2010-10-03 21:11:00 UTC 
I see the binary incompatibility issues quite a lot. Can we detect ABI version of the currently loaded library and if incompatible, inform the user about it (and also exit digiKam nicely)?
Comment 3 Marcel Wiesweg 2010-10-04 15:28:46 UTC 
Interesting idea for the header-only changes that do not cause failure of runtime linking. We'd need a macro (compile time version) and a runtime method (runtime version) and compare the two. Are there other projects forced to do this? It would be a bit sad, it's not our job.

I still think it's the packagers responsibility to correctly specify the dependencies.
Comment 4 Martin Klapetek 2010-10-04 18:59:21 UTC 
The only other project I know of, which is checking for ABI, is AMD's Catalyst driver installer. It checks for current X.Org ABI and if it is not compatible, it will let you know and the installation is then canceled.
Comment 5 caulier.gilles 2010-10-29 06:02:34 UTC 
*** Bug 255538 has been marked as a duplicate of this bug. ***
Comment 6 caulier.gilles 2010-11-11 09:45:20 UTC 
*** Bug 256571 has been marked as a duplicate of this bug. ***
Comment 7 caulier.gilles 2010-11-25 20:21:57 UTC 
*** Bug 257905 has been marked as a duplicate of this bug. ***
Comment 8 Giuseppe Vinci 2010-11-25 22:25:43 UTC 
Gilles Caulier wrote:
"This is a crash due to a binary uncompatibility of libkdcraw on your system.
Please update this library. It sound like a package problem."

It would help every user with this problem, to know which version of libkdcraw digikam needs. On my system is the libkdcraw8 4.4.4-2.1.1-x86_64. I experienced crashes also with the version 4.4.4-500.1-x86_64.

Maybe can it be posted on this bug ...
Comment 9 caulier.gilles 2019-12-23 17:26:26 UTC 
Not reproducible with digiKam 7.0.0-beta1.
Comment 10 Giuseppe Vinci 2019-12-23 18:26:28 UTC 
This bug is already no more reproducible since long time on my environment.
I actually use the version 6.1.0; but why testing on beta versions?
I think, most of kde users does not work with betas. Or there are now only beta testers among kde users? ;-)

Have a nice time!
Comment 11 caulier.gilles 2019-12-23 18:36:44 UTC 
For regression test, as this file has not been fully closed in the past.