Bug 187188

Summary: digikam crashes when including a CIFS located album
Product: [Applications] digikam Reporter: Leslie Harlley Watter <leslie>
Component: Database-MediaAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: languitar
Priority: NOR    
Version: 0.9.5   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In: 1.1.0
Attachments: First kcrash file - including the CIFS located album
Second Kcrash - opening digikam just after the first crash

Description Leslie Harlley Watter 2009-03-15 01:29:46 UTC 
Version:           SVN - 13/03/2009 (using Devel)
Compiler:          gcc (Debian 4.3.3-5) 4.3.3 
OS:                Linux
Installed from:    Compiled sources

Digikam crashed when I was including a digikam 0.9.5 album (22Gb) to my Album folders. Note to the album was on a CIFS share.

I could save a trace that follows:

Application: digiKam (digikam), signal SIGSEGV
[Current thread is 0 (LWP 8213)]

Thread 4 (Thread 0xb3353b90 (LWP 8218)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb5561386 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb556119e in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb68d52d8 in ?? () from /usr/lib/libkdeui.so.5
#4  0x00000000 in ?? ()

Thread 3 (Thread 0xaea47b90 (LWP 10442)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb51b8fb5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb55b3f2d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb579c542 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb71e0ae5 in Digikam::LoadSaveThread::run (this=0xbc85e70) at /home/leslie/scm/digikam/graphics/digikam/libs/threadimageio/loadsavethread.cpp:131
#5  0xb579b52e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb51b54e5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb55a510e in clone () from /lib/i686/cmov/libc.so.6

Thread 2 (Thread 0xad5feb90 (LWP 10443)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb51b8fb5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb55b3f2d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb579c542 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb71e0ae5 in Digikam::LoadSaveThread::run (this=0xbeef250) at /home/leslie/scm/digikam/graphics/digikam/libs/threadimageio/loadsavethread.cpp:131
#5  0xb579b52e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb51b54e5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb55a510e in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb48f8700 (LWP 8213)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb51b8fb5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb55b3f2d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb579c542 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb579b6d3 in QThread::wait () from /usr/lib/libQtCore.so.4
#5  0x082d588e in Digikam::ScanController::shutDown (this=0x848f858) at /home/leslie/scm/digikam/graphics/digikam/digikam/scancontroller.cpp:264
#6  0x082d59f6 in ~ScanController (this=0x848f858) at /home/leslie/scm/digikam/graphics/digikam/digikam/scancontroller.cpp:247
#7  0x082d82b1 in ~ScanControllerCreator (this=0x848f858) at /home/leslie/scm/digikam/graphics/digikam/digikam/scancontroller.cpp:188
#8  0x082d5b1e in destroy () at /home/leslie/scm/digikam/graphics/digikam/digikam/scancontroller.cpp:189
#9  0x0824c37b in ~KCleanUpGlobalStatic (this=0x83be268) at /usr/include/kglobal.h:62
#10 0xb54f0b29 in exit () from /lib/i686/cmov/libc.so.6
#11 0xb5da4b8b in ?? () from /usr/lib/libQtGui.so.4
#12 0xb68652fa in KApplication::xioErrhandler () from /usr/lib/libkdeui.so.5
#13 0xb6865336 in ?? () from /usr/lib/libkdeui.so.5
#14 0xbfcd9718 in ?? ()
#15 0x083dea40 in ?? ()
#16 0x000ec76c in ?? ()
#17 0x00000005 in ?? ()
#18 0xb6865319 in ?? () from /usr/lib/libkdeui.so.5
#19 0xb54453ec in ?? () from /usr/lib/libX11.so.6
#20 0xbfcd6e58 in ?? ()
#21 0xb5395922 in _XIOError () from /usr/lib/libX11.so.6
Backtrace stopped: frame did not save the PC
Comment 1 Leslie Harlley Watter 2009-03-15 01:47:19 UTC 
Created attachment 32115 [details]
First kcrash file - including the CIFS located album
Comment 2 Leslie Harlley Watter 2009-03-15 01:49:30 UTC 
Created attachment 32116 [details]
Second Kcrash - opening digikam just after the first crash 

With the CIFS network share mounted digikam crashed.
Without the share mounted, digikam started normally.
Comment 3 caulier.gilles 2009-05-19 15:45:57 UTC 
Leslie,

I recommend to try digiKam 0.10.0. It support better remote files systems.

Gilles Caulier
Comment 4 Leslie Harlley Watter 2009-06-07 04:13:43 UTC 
Hi Gilles,

Sorry for the long delay, but the bug still happened for 0.10 and it happens eventually to SVN (0.11) version. I'm trying to track it down.

cheers,

LEslie
Comment 5 Johannes Wienke 2009-10-31 01:09:46 UTC 
Is this still occurring? If so, can you try to provide a new, complete backtrace?
Comment 6 caulier.gilles 2009-12-25 20:13:44 UTC 
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
Comment 7 Leslie Harlley Watter 2010-01-06 16:49:27 UTC 
Using the last SVN code the bug was fixed. 

Thanks to all and sorry because the long delay.

Cheers,

LEslie