[Bug 454113] Re: digikam crashes when click on download selected

Bug Watch Updater 454113 at bugs.launchpad.net
Wed Jun 27 19:47:40 UTC 2012


Launchpad has imported 153 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=210462.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2009-10-13T19:49:37+00:00 mrgil wrote:

Application that crashed: digikam
Version of the application: 1.0.0-beta5
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.31-3.slh.1-sidux-686 i686

What I was doing when the application crashed:
When I connect my Canon PowerShot SD1000 to Digikam, the previews show up fine, but when I select New items and Download selected, Digikam 1.0.0-beta5 crashes.

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

Thread 20 (Thread 0xb197eb90 (LWP 7908)):
#0  0xb7794424 in __kernel_vsyscall ()
#1  0xb4788f65 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb4ba985d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb4da55c2 in QWaitConditionPrivate::wait (this=0x954cb10, mutex=0x954cb0c, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0x954cb10, mutex=0x954cb0c, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#5  0x08306001 in Digikam::ScanController::run (this=0x953e098) at /build/buildd-digikam_1.0.0~beta5-1-i386-gHJtOv/digikam-1.0.0~beta5/digikam/scancontroller.cpp:499
#6  0xb4da45e2 in QThreadPrivate::start (arg=0x953e098) at thread/qthread_unix.cpp:188
#7  0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#8  0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 19 (Thread 0xb0cffb90 (LWP 7911)):
#0  0xb3370fec in clock_gettime () from /lib/i686/cmov/librt.so.1
#1  0xb4ec1e9b in QTimerInfoList::getTime (this=0x967a604, t=...) at kernel/qeventdispatcher_unix.cpp:339
#2  0xb4ec2061 in QTimerInfoList::updateCurrentTime (this=0x967a604) at kernel/qeventdispatcher_unix.cpp:297
#3  0xb4ec221a in QTimerInfoList::timerWait (this=0x967a604, tm=...) at kernel/qeventdispatcher_unix.cpp:420
#4  0xb4ec0220 in timerSourcePrepareHelper (src=0xb0cff0d8, timeout=0xb0cff1c8) at kernel/qeventdispatcher_glib.cpp:136
#5  0xb4ec02a5 in timerSourcePrepare (source=0x0, timeout=0xb3374ff4) at kernel/qeventdispatcher_glib.cpp:169
#6  0xb3402f40 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#7  0xb3403304 in ?? () from /lib/libglib-2.0.so.0
#8  0xb34037a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#9  0xb4ec005f in QEventDispatcherGlib::processEvents (this=0x9678d70, flags=...) at kernel/qeventdispatcher_glib.cpp:409
#10 0xb4e9383a in QEventLoop::processEvents (this=0xb0cff330, flags=...) at kernel/qeventloop.cpp:149
#11 0xb4e93c82 in QEventLoop::exec (this=0xb0cff330, flags=...) at kernel/qeventloop.cpp:201
#12 0xb4da1309 in QThread::exec (this=0x96689d8) at thread/qthread.cpp:487
#13 0xb675414d in Digikam::ImageFilterModelWorker::Thread::run() () from /usr/lib/libdigikamdatabase.so.1
#14 0xb4da45e2 in QThreadPrivate::start (arg=0x96689d8) at thread/qthread_unix.cpp:188
#15 0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#16 0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 18 (Thread 0xb00ffb90 (LWP 7912)):
#0  0xb4787ec1 in __pthread_mutex_unlock_usercnt () from /lib/i686/cmov/libpthread.so.0
#1  0xb4ba9a66 in pthread_mutex_unlock () from /lib/i686/cmov/libc.so.6
#2  0xb34030e7 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#3  0xb3403304 in ?? () from /lib/libglib-2.0.so.0
#4  0xb34037a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0xb4ec005f in QEventDispatcherGlib::processEvents (this=0x967cbe8, flags=...) at kernel/qeventdispatcher_glib.cpp:409
#6  0xb4e9383a in QEventLoop::processEvents (this=0xb00ff330, flags=...) at kernel/qeventloop.cpp:149
#7  0xb4e93c82 in QEventLoop::exec (this=0xb00ff330, flags=...) at kernel/qeventloop.cpp:201
#8  0xb4da1309 in QThread::exec (this=0x96890b8) at thread/qthread.cpp:487
#9  0xb675414d in Digikam::ImageFilterModelWorker::Thread::run() () from /usr/lib/libdigikamdatabase.so.1
#10 0xb4da45e2 in QThreadPrivate::start (arg=0x96890b8) at thread/qthread_unix.cpp:188
#11 0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#12 0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 17 (Thread 0xaf8feb90 (LWP 7913)):
#0  0xb7794424 in __kernel_vsyscall ()
#1  0xb4788f65 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb4ba985d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb4da55c2 in QWaitConditionPrivate::wait (this=0x9697a70, mutex=0x9697a6c, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0x9697a70, mutex=0x9697a6c, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#5  0xb695d02a in Digikam::LoadSaveThread::run (this=0x9697a60) at /build/buildd-digikam_1.0.0~beta5-1-i386-gHJtOv/digikam-1.0.0~beta5/libs/threadimageio/loadsavethread.cpp:136
#6  0xb4da45e2 in QThreadPrivate::start (arg=0x9697a60) at thread/qthread_unix.cpp:188
#7  0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#8  0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 16 (Thread 0xaf0fdb90 (LWP 7914)):
#0  0xb3370fec in clock_gettime () from /lib/i686/cmov/librt.so.1
#1  0xb4ec1e9b in QTimerInfoList::getTime (this=0x96929d4, t=...) at kernel/qeventdispatcher_unix.cpp:339
#2  0xb4ec2061 in QTimerInfoList::updateCurrentTime (this=0x96929d4) at kernel/qeventdispatcher_unix.cpp:297
#3  0xb4ec221a in QTimerInfoList::timerWait (this=0x96929d4, tm=...) at kernel/qeventdispatcher_unix.cpp:420
#4  0xb4ec0220 in timerSourcePrepareHelper (src=0xaf0fd0e8, timeout=0xaf0fd1d8) at kernel/qeventdispatcher_glib.cpp:136
#5  0xb4ec02a5 in timerSourcePrepare (source=0x0, timeout=0xb3374ff4) at kernel/qeventdispatcher_glib.cpp:169
#6  0xb3402f40 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#7  0xb3403304 in ?? () from /lib/libglib-2.0.so.0
#8  0xb34037a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#9  0xb4ec005f in QEventDispatcherGlib::processEvents (this=0x9772b48, flags=...) at kernel/qeventdispatcher_glib.cpp:409
#10 0xb4e9383a in QEventLoop::processEvents (this=0xaf0fd340, flags=...) at kernel/qeventloop.cpp:149
#11 0xb4e93c82 in QEventLoop::exec (this=0xaf0fd340, flags=...) at kernel/qeventloop.cpp:201
#12 0xb4da1309 in QThread::exec (this=0x96810f8) at thread/qthread.cpp:487
#13 0xb4da45e2 in QThreadPrivate::start (arg=0x96810f8) at thread/qthread_unix.cpp:188
#14 0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#15 0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 15 (Thread 0xae8fcb90 (LWP 7915)):
#0  0xb3370fec in clock_gettime () from /lib/i686/cmov/librt.so.1
#1  0xb4ec1e9b in QTimerInfoList::getTime (this=0x969b0c4, t=...) at kernel/qeventdispatcher_unix.cpp:339
#2  0xb4ec2061 in QTimerInfoList::updateCurrentTime (this=0x969b0c4) at kernel/qeventdispatcher_unix.cpp:297
#3  0xb4ec221a in QTimerInfoList::timerWait (this=0x969b0c4, tm=...) at kernel/qeventdispatcher_unix.cpp:420
#4  0xb4ec0220 in timerSourcePrepareHelper (src=0xae8fc0e8, timeout=0xae8fc1d8) at kernel/qeventdispatcher_glib.cpp:136
#5  0xb4ec02a5 in timerSourcePrepare (source=0x0, timeout=0xb3374ff4) at kernel/qeventdispatcher_glib.cpp:169
#6  0xb3402f40 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#7  0xb3403304 in ?? () from /lib/libglib-2.0.so.0
#8  0xb34037a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#9  0xb4ec005f in QEventDispatcherGlib::processEvents (this=0x967dff8, flags=...) at kernel/qeventdispatcher_glib.cpp:409
#10 0xb4e9383a in QEventLoop::processEvents (this=0xae8fc340, flags=...) at kernel/qeventloop.cpp:149
#11 0xb4e93c82 in QEventLoop::exec (this=0xae8fc340, flags=...) at kernel/qeventloop.cpp:201
#12 0xb4da1309 in QThread::exec (this=0x969f7c0) at thread/qthread.cpp:487
#13 0xb4da45e2 in QThreadPrivate::start (arg=0x969f7c0) at thread/qthread_unix.cpp:188
#14 0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#15 0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 14 (Thread 0xae0fbb90 (LWP 7916)):
#0  0xb7794424 in __kernel_vsyscall ()
#1  0xb4788f65 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb4ba985d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb4da55c2 in QWaitConditionPrivate::wait (this=0x969af90, mutex=0x969af8c, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0x969af90, mutex=0x969af8c, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#5  0xb695d02a in Digikam::LoadSaveThread::run (this=0x969af80) at /build/buildd-digikam_1.0.0~beta5-1-i386-gHJtOv/digikam-1.0.0~beta5/libs/threadimageio/loadsavethread.cpp:136
#6  0xb4da45e2 in QThreadPrivate::start (arg=0x969af80) at thread/qthread_unix.cpp:188
#7  0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#8  0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 13 (Thread 0xab76cb90 (LWP 7917)):
#0  0xb7794424 in __kernel_vsyscall ()
#1  0xb4789292 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb4ba98b4 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6
#3  0xb043e903 in ?? () from /usr/lib/libxine.so.1

Thread 12 (Thread 0xaa9ffb90 (LWP 7918)):
#0  0xb7794424 in __kernel_vsyscall ()
#1  0xb4b92fe1 in select () from /lib/i686/cmov/libc.so.6
#2  0xb046834a in xine_usec_sleep () from /usr/lib/libxine.so.1
#3  0x00000000 in ?? ()

Thread 11 (Thread 0xaa1feb90 (LWP 7919)):
#0  0xb4ba9a57 in pthread_mutex_unlock () from /lib/i686/cmov/libc.so.6
#1  0xb3402c69 in g_main_context_check () from /lib/libglib-2.0.so.0
#2  0xb3403555 in ?? () from /lib/libglib-2.0.so.0
#3  0xb34037a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#4  0xb4ec005f in QEventDispatcherGlib::processEvents (this=0x962c2b8, flags=...) at kernel/qeventdispatcher_glib.cpp:409
#5  0xb4e9383a in QEventLoop::processEvents (this=0xaa1fe2f0, flags=...) at kernel/qeventloop.cpp:149
#6  0xb4e93c82 in QEventLoop::exec (this=0xaa1fe2f0, flags=...) at kernel/qeventloop.cpp:201
#7  0xb4da1309 in QThread::exec (this=0x98a96f0) at thread/qthread.cpp:487
#8  0xac4152ba in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#9  0xb4da45e2 in QThreadPrivate::start (arg=0x98a96f0) at thread/qthread_unix.cpp:188
#10 0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#11 0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 10 (Thread 0xa99f4b90 (LWP 7921)):
#0  0xb7794424 in __kernel_vsyscall ()
#1  0xb4788f65 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb4ba985d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb044fa56 in ?? () from /usr/lib/libxine.so.1
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 9 (Thread 0xa915db90 (LWP 7932)):
#0  0xb4ba9a57 in pthread_mutex_unlock () from /lib/i686/cmov/libc.so.6
#1  0xb340191c in g_main_context_acquire () from /lib/libglib-2.0.so.0
#2  0xb340322c in ?? () from /lib/libglib-2.0.so.0
#3  0xb34037a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#4  0xb4ec005f in QEventDispatcherGlib::processEvents (this=0x9ecea28, flags=...) at kernel/qeventdispatcher_glib.cpp:409
#5  0xb4e9383a in QEventLoop::processEvents (this=0xa915d2e0, flags=...) at kernel/qeventloop.cpp:149
#6  0xb4e93c82 in QEventLoop::exec (this=0xa915d2e0, flags=...) at kernel/qeventloop.cpp:201
#7  0xb4da1309 in QThread::exec (this=0x9493978) at thread/qthread.cpp:487
#8  0xa91ddf1c in ?? () from /usr/lib/kde4/plugins/marble/GpsdPositionProviderPlugin.so
#9  0xb4da45e2 in QThreadPrivate::start (arg=0x9493978) at thread/qthread_unix.cpp:188
#10 0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#11 0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 8 (Thread 0xa60ffb90 (LWP 7933)):
#0  0xb7794424 in __kernel_vsyscall ()
#1  0xb4788f65 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb4ba985d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb4da55c2 in QWaitConditionPrivate::wait (this=0x981ec00, mutex=0x981ebfc, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0x981ec00, mutex=0x981ebfc, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#5  0xb695d02a in Digikam::LoadSaveThread::run (this=0x981ebf0) at /build/buildd-digikam_1.0.0~beta5-1-i386-gHJtOv/digikam-1.0.0~beta5/libs/threadimageio/loadsavethread.cpp:136
#6  0xb4da45e2 in QThreadPrivate::start (arg=0x981ebf0) at thread/qthread_unix.cpp:188
#7  0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#8  0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 7 (Thread 0xa6cffb90 (LWP 7940)):
#0  0xb7794424 in __kernel_vsyscall ()
#1  0xb4788f65 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb4ba985d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb4da55c2 in QWaitConditionPrivate::wait (this=0xa4ec050, mutex=0xa4ec04c, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0xa4ec050, mutex=0xa4ec04c, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#5  0xb695d02a in Digikam::LoadSaveThread::run (this=0xa4ec040) at /build/buildd-digikam_1.0.0~beta5-1-i386-gHJtOv/digikam-1.0.0~beta5/libs/threadimageio/loadsavethread.cpp:136
#6  0xb4da45e2 in QThreadPrivate::start (arg=0xa4ec040) at thread/qthread_unix.cpp:188
#7  0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#8  0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 6 (Thread 0xa58feb90 (LWP 7941)):
#0  0xb3370fec in clock_gettime () from /lib/i686/cmov/librt.so.1
#1  0xb4ec1e9b in QTimerInfoList::getTime (this=0xa55985c, t=...) at kernel/qeventdispatcher_unix.cpp:339
#2  0xb4ec2061 in QTimerInfoList::updateCurrentTime (this=0xa55985c) at kernel/qeventdispatcher_unix.cpp:297
#3  0xb4ec221a in QTimerInfoList::timerWait (this=0xa55985c, tm=...) at kernel/qeventdispatcher_unix.cpp:420
#4  0xb4ec0220 in timerSourcePrepareHelper (src=0xa58fe088, timeout=0xa58fe178) at kernel/qeventdispatcher_glib.cpp:136
#5  0xb4ec02a5 in timerSourcePrepare (source=0x0, timeout=0xb3374ff4) at kernel/qeventdispatcher_glib.cpp:169
#6  0xb3402f40 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#7  0xb3403304 in ?? () from /lib/libglib-2.0.so.0
#8  0xb34037a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#9  0xb4ec005f in QEventDispatcherGlib::processEvents (this=0xa5597c0, flags=...) at kernel/qeventdispatcher_glib.cpp:409
#10 0xb4e9383a in QEventLoop::processEvents (this=0xa58fe2e0, flags=...) at kernel/qeventloop.cpp:149
#11 0xb4e93c82 in QEventLoop::exec (this=0xa58fe2e0, flags=...) at kernel/qeventloop.cpp:201
#12 0xb4da1309 in QThread::exec (this=0xa535668) at thread/qthread.cpp:487
#13 0xa91ddf1c in ?? () from /usr/lib/kde4/plugins/marble/GpsdPositionProviderPlugin.so
#14 0xb4da45e2 in QThreadPrivate::start (arg=0xa535668) at thread/qthread_unix.cpp:188
#15 0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#16 0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 5 (Thread 0xa895cb90 (LWP 7942)):
#0  0xb7794424 in __kernel_vsyscall ()
#1  0xb4788f65 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb4ba985d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb4da55c2 in QWaitConditionPrivate::wait (this=0xa56edd8, mutex=0xa56edd4, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0xa56edd8, mutex=0xa56edd4, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#5  0xb695d02a in Digikam::LoadSaveThread::run (this=0xa56edc8) at /build/buildd-digikam_1.0.0~beta5-1-i386-gHJtOv/digikam-1.0.0~beta5/libs/threadimageio/loadsavethread.cpp:136
#6  0xb4da45e2 in QThreadPrivate::start (arg=0xa56edc8) at thread/qthread_unix.cpp:188
#7  0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#8  0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 4 (Thread 0xa38ffb90 (LWP 7962)):
#0  0xb4783230 in __i686.get_pc_thunk.bx () from /lib/i686/cmov/libpthread.so.0
#1  0xb478686e in pthread_mutex_lock () from /lib/i686/cmov/libpthread.so.0
#2  0xb4ba9a26 in pthread_mutex_lock () from /lib/i686/cmov/libc.so.6
#3  0xb3403433 in ?? () from /lib/libglib-2.0.so.0
#4  0xb34037a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0xb4ec005f in QEventDispatcherGlib::processEvents (this=0xb7caa50, flags=...) at kernel/qeventdispatcher_glib.cpp:409
#6  0xb4e9383a in QEventLoop::processEvents (this=0xa38ff2e0, flags=...) at kernel/qeventloop.cpp:149
#7  0xb4e93c82 in QEventLoop::exec (this=0xa38ff2e0, flags=...) at kernel/qeventloop.cpp:201
#8  0xb4da1309 in QThread::exec (this=0xb7d5e60) at thread/qthread.cpp:487
#9  0xa91ddf1c in ?? () from /usr/lib/kde4/plugins/marble/GpsdPositionProviderPlugin.so
#10 0xb4da45e2 in QThreadPrivate::start (arg=0xb7d5e60) at thread/qthread_unix.cpp:188
#11 0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#12 0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 3 (Thread 0xa2affb90 (LWP 7963)):
#0  0xb7794424 in __kernel_vsyscall ()
#1  0xb4788f65 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb4ba985d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb4da55c2 in QWaitConditionPrivate::wait (this=0xb7d5e40, mutex=0xb7d5e3c, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0xb7d5e40, mutex=0xb7d5e3c, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#5  0xb695d02a in Digikam::LoadSaveThread::run (this=0xb7d5e30) at /build/buildd-digikam_1.0.0~beta5-1-i386-gHJtOv/digikam-1.0.0~beta5/libs/threadimageio/loadsavethread.cpp:136
#6  0xb4da45e2 in QThreadPrivate::start (arg=0xb7d5e30) at thread/qthread_unix.cpp:188
#7  0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#8  0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 2 (Thread 0xa22feb90 (LWP 7970)):
#0  0xb7794424 in __kernel_vsyscall ()
#1  0xb4788f65 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb4ba985d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb4da55c2 in QWaitConditionPrivate::wait (this=0xb7e73ac, mutex=0xb7e73a8, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  QWaitCondition::wait (this=0xb7e73ac, mutex=0xb7e73a8, time=4294967295) at thread/qwaitcondition_unix.cpp:159
#5  0x08120de4 in Digikam::CameraController::run (this=0xb7e73b8) at /build/buildd-digikam_1.0.0~beta5-1-i386-gHJtOv/digikam-1.0.0~beta5/utilities/cameragui/cameracontroller.cpp:329
#6  0xb4da45e2 in QThreadPrivate::start (arg=0xb7e73b8) at thread/qthread_unix.cpp:188
#7  0xb47854b5 in start_thread () from /lib/i686/cmov/libpthread.so.0
#8  0xb4b9aa5e in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb2f3a700 (LWP 7905)):
[KCrash Handler]
#6  0xb4d1421c in __dynamic_cast () from /usr/lib/libstdc++.so.6
#7  0x08273ce9 in Digikam::AlbumSelectDialog::selectAlbum (parent=0xb6aa3a8, albumToSelect=0xb5bce70, header=..., newAlbumString=..., allowRootSelection=false)
    at /build/buildd-digikam_1.0.0~beta5-1-i386-gHJtOv/digikam-1.0.0~beta5/digikam/albumselectdialog.cpp:174
#8  0x08148732 in Digikam::CameraUI::slotDownload (this=0xb6aa3a8, onlySelected=true, deleteAfter=false, album=0xb5bce70)
    at /build/buildd-digikam_1.0.0~beta5-1-i386-gHJtOv/digikam-1.0.0~beta5/utilities/cameragui/cameraui.cpp:1498
#9  0x081491a9 in Digikam::CameraUI::slotDownloadSelected (this=0xb6aa3a8) at /build/buildd-digikam_1.0.0~beta5-1-i386-gHJtOv/digikam-1.0.0~beta5/utilities/cameragui/cameraui.cpp:1436
#10 0x0814e34d in Digikam::CameraUI::qt_metacall (this=0xb6aa3a8, _c=QMetaObject::InvokeMetaMethod, _id=33, _a=0xbff92bec)
    at /build/buildd-digikam_1.0.0~beta5-1-i386-gHJtOv/digikam-1.0.0~beta5/obj-i486-linux-gnu/digikam/cameraui.moc:224
#11 0xb4eaa303 in QMetaObject::activate (sender=0xbb2ac88, from_signal_index=5, to_signal_index=6, argv=0xbff92bec) at kernel/qobject.cpp:3112
#12 0xb4eaa720 in QMetaObject::activate (sender=0xbb2ac88, m=0x848bcc8, from_local_signal_index=1, to_local_signal_index=2, argv=0xbff92bec) at kernel/qobject.cpp:3206
#13 0xb5377591 in QAction::triggered (this=0xbb2ac88, _t1=false) at .moc/release-shared/moc_qaction.cpp:236
#14 0xb5378adf in QAction::activate (this=0xbb2ac88, event=QAction::Trigger) at kernel/qaction.cpp:1167
#15 0xb5811012 in QAction::trigger (this=0xb4c15160) at ../../include/QtGui/../../src/gui/kernel/qaction.h:203
#16 QToolButton::nextCheckState (this=0xb4c15160) at widgets/qtoolbutton.cpp:1135
#17 0xb572c543 in QAbstractButtonPrivate::click (this=0xbb42d48) at widgets/qabstractbutton.cpp:525
#18 0xb572c816 in QAbstractButton::mouseReleaseEvent (this=0xbb4bb98, e=0xbff932bc) at widgets/qabstractbutton.cpp:1115
#19 0xb581150c in QToolButton::mouseReleaseEvent (this=0xbb4bb98, e=0xbff932bc) at widgets/qtoolbutton.cpp:709
#20 0xb53d39fb in QWidget::event (this=0xbb4bb98, event=0xbff932bc) at kernel/qwidget.cpp:7554
#21 0xb572a7fe in QAbstractButton::event (this=0xbb4bb98, e=0xbff932bc) at widgets/qabstractbutton.cpp:1077
#22 0xb5813eba in QToolButton::event (this=0xbb4bb98, event=0xbff932bc) at widgets/qtoolbutton.cpp:1151
#23 0xb537da94 in QApplicationPrivate::notify_helper (this=0x9451350, receiver=0xbb4bb98, e=0xbff932bc) at kernel/qapplication.cpp:4065
#24 0xb5386551 in QApplication::notify (this=0xbff94b74, receiver=0xbb4bb98, e=0xbff932bc) at kernel/qapplication.cpp:3767
#25 0xb5f770fd in KApplication::notify (this=0xbff94b74, receiver=0xbb4bb98, event=0xbff932bc) at ../../kdeui/kernel/kapplication.cpp:302
#26 0xb4e951eb in QCoreApplication::notifyInternal (this=0xbff94b74, receiver=0xbb4bb98, event=0xbff932bc) at kernel/qcoreapplication.cpp:610
#27 0xb53855de in QCoreApplication::sendSpontaneousEvent (receiver=0xbb4bb98, event=0xbff932bc, alienWidget=0xbb4bb98, nativeWidget=0xb6aa3a8, buttonDown=0xb5bf4580, lastMouseReceiver=...)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#28 QApplicationPrivate::sendMouseEvent (receiver=0xbb4bb98, event=0xbff932bc, alienWidget=0xbb4bb98, nativeWidget=0xb6aa3a8, buttonDown=0xb5bf4580, lastMouseReceiver=...)
    at kernel/qapplication.cpp:2924
#29 0xb53f4175 in QETWidget::translateMouseEvent (this=0xb6aa3a8, event=0xbff9486c) at kernel/qapplication_x11.cpp:4411
#30 0xb53f3646 in QApplication::x11ProcessEvent (this=0xbff94b74, event=0xbff9486c) at kernel/qapplication_x11.cpp:3430
#31 0xb541dbc2 in x11EventSourceDispatch (s=0x94545b0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#32 0xb33ffe98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#33 0xb3403623 in ?? () from /lib/libglib-2.0.so.0
#34 0xb34037a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#35 0xb4ec0041 in QEventDispatcherGlib::processEvents (this=0x942b5f8, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#36 0xb541d305 in QGuiEventDispatcherGlib::processEvents (this=0x942b5f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#37 0xb4e9383a in QEventLoop::processEvents (this=0xbff94ad0, flags=...) at kernel/qeventloop.cpp:149
#38 0xb4e93c82 in QEventLoop::exec (this=0xbff94ad0, flags=...) at kernel/qeventloop.cpp:201
#39 0xb4e960d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#40 0xb537d917 in QApplication::exec () at kernel/qapplication.cpp:3525
#41 0x0839f3bb in main (argc=3, argv=0xbff94fa4) at /build/buildd-digikam_1.0.0~beta5-1-i386-gHJtOv/digikam-1.0.0~beta5/digikam/main.cpp:186

Reported using DrKonqi

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/0

------------------------------------------------------------------------
On 2009-10-14T02:41:50+00:00 Dario Andres wrote:

>From bug 210496:
What I was doing when the application crashed:
I've been using digikam for a couple of months reading and downloading pics
from a 4GB SDHC card. Now I have this problem, and it happens either trying to
download all the pics and videos (mov, actually I've done that before also) or
trying to download a subset of them.

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/1

------------------------------------------------------------------------
On 2009-10-14T02:41:52+00:00 Dario Andres wrote:

*** Bug 210496 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/2

------------------------------------------------------------------------
On 2009-10-14T11:38:39+00:00 Caulier-gilles-9 wrote:

*** Bug 210522 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/3

------------------------------------------------------------------------
On 2009-10-14T13:42:27+00:00 Andi-clemens wrote:

The bug *might* have been fixed now, we double check every pointer before returning from the selectAlbum() method.
I couldn't confirm the bug before and so I couldn't now, but:

Mr. Gil,
can you try the latest SVN checkout and make sure the issue has been fixed?

Andi

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/4

------------------------------------------------------------------------
On 2009-10-14T17:12:24+00:00 mrgil wrote:

Hi, Andi,

I will check, but it will have to be later today, maybe 12 hours from
now...

Thanks!

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/5

------------------------------------------------------------------------
On 2009-10-14T17:28:40+00:00 Andi-clemens wrote:

*** Bug 210569 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/6

------------------------------------------------------------------------
On 2009-10-14T17:49:18+00:00 Andi-clemens wrote:

*** Bug 210569 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/7

------------------------------------------------------------------------
On 2009-10-15T02:12:13+00:00 mrgil wrote:

I'm trying to build the SVN version of digiKam from instructions here:
http://www.digikam.org/drupal/download/KDE4
and when I get to this step:
cmake -DCMAKE_BUILD_TYPE=debugfull -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` ../../graphics 
there are a lot of libraries not found, but I have the latest versions of all the libraries it's looking for (i.e. libkipi6, libjasper1, libgphoto2-2, libkdcraw7).  Is there a reason the cmake command is looking for different versions of libjasper, libkipi, libgphoto, libkdcraw, etc.?

I would certainly like to build and test the svn digiKam, but so far I
can't.

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/8

------------------------------------------------------------------------
On 2009-10-15T08:21:12+00:00 Caulier-gilles-9 wrote:

Look in README file and install devel headers file from libraries
packages.

Gilles Caulier

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/9

------------------------------------------------------------------------
On 2009-10-15T09:37:01+00:00 mrgil wrote:

Thanks, Gilles, loading the -dev libraries allowed me to complete the
build.

I tested digikam version 1.0.0-beta6 (rev.: 1035415) and my pictures
downloaded perfectly.

Thanks to everyone who helped!

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/10

------------------------------------------------------------------------
On 2009-10-17T19:03:25+00:00 Dario Andres wrote:

*** Bug 210854 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/14

------------------------------------------------------------------------
On 2009-10-17T21:32:45+00:00 Dario Andres wrote:

*** Bug 210906 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/15

------------------------------------------------------------------------
On 2009-10-18T14:08:41+00:00 Andi-clemens wrote:

*** Bug 210963 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/18

------------------------------------------------------------------------
On 2009-10-18T22:45:24+00:00 Andi-clemens wrote:

*** Bug 211017 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/19

------------------------------------------------------------------------
On 2009-10-21T10:32:55+00:00 Andi-clemens wrote:

*** Bug 211308 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/20

------------------------------------------------------------------------
On 2009-10-23T17:26:25+00:00 Andi-clemens wrote:

*** Bug 211561 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/21

------------------------------------------------------------------------
On 2009-10-24T03:19:40+00:00 Dario Andres wrote:

*** Bug 211608 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/22

------------------------------------------------------------------------
On 2009-10-24T17:44:11+00:00 Andi-clemens wrote:

*** Bug 211665 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/23

------------------------------------------------------------------------
On 2009-10-26T19:49:01+00:00 Andi-clemens wrote:

*** Bug 211966 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/24

------------------------------------------------------------------------
On 2009-10-27T01:15:28+00:00 Andi-clemens wrote:

*** Bug 211960 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/25

------------------------------------------------------------------------
On 2009-10-27T19:07:58+00:00 Andi-clemens wrote:

*** Bug 212092 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/26

------------------------------------------------------------------------
On 2009-10-28T01:03:38+00:00 Andi-clemens wrote:

*** Bug 212131 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/27

------------------------------------------------------------------------
On 2009-10-28T10:39:00+00:00 Andi-clemens wrote:

*** Bug 212152 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/28

------------------------------------------------------------------------
On 2009-10-28T11:49:11+00:00 Andi-clemens wrote:

*** Bug 212156 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/29

------------------------------------------------------------------------
On 2009-10-28T16:59:12+00:00 Andi-clemens wrote:

*** Bug 212203 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/30

------------------------------------------------------------------------
On 2009-10-31T11:17:10+00:00 Andi-clemens wrote:

*** Bug 212496 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/33

------------------------------------------------------------------------
On 2009-11-01T10:11:56+00:00 Andi-clemens wrote:

*** Bug 212588 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/34

------------------------------------------------------------------------
On 2009-11-01T10:12:22+00:00 Andi-clemens wrote:

*** Bug 212584 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/35

------------------------------------------------------------------------
On 2009-11-01T21:08:04+00:00 Andi-clemens wrote:

*** Bug 212657 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/36

------------------------------------------------------------------------
On 2009-11-02T18:41:01+00:00 Andi-clemens wrote:

*** Bug 212765 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/37

------------------------------------------------------------------------
On 2009-11-02T18:41:21+00:00 Andi-clemens wrote:

*** Bug 212734 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/38

------------------------------------------------------------------------
On 2009-11-03T14:31:40+00:00 Andi-clemens wrote:

*** Bug 212906 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/40

------------------------------------------------------------------------
On 2009-11-03T20:59:36+00:00 Andi-clemens wrote:

*** Bug 212943 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/41

------------------------------------------------------------------------
On 2009-11-04T10:17:04+00:00 Andi-clemens wrote:

*** Bug 213029 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/42

------------------------------------------------------------------------
On 2009-11-04T13:16:51+00:00 Andi-clemens wrote:

*** Bug 213075 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/43

------------------------------------------------------------------------
On 2009-11-04T22:17:17+00:00 Andi-clemens wrote:

*** Bug 213153 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/44

------------------------------------------------------------------------
On 2009-11-06T02:10:25+00:00 Dario Andres wrote:

*** Bug 213290 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/45

------------------------------------------------------------------------
On 2009-11-06T08:36:53+00:00 Andi-clemens wrote:

*** Bug 213377 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/46

------------------------------------------------------------------------
On 2009-11-07T09:25:38+00:00 Andi-clemens wrote:

*** Bug 213497 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/47

------------------------------------------------------------------------
On 2009-11-07T20:43:09+00:00 Sami Nieminen wrote:

I just experienced the same bug on kubuntu 9.10 while trying to import
pictures from SD card. This is key functionality of digikam and
therefore so many duplicate bug reports. Is the next beta planned to be
released soon with a fix to at least this issue?

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/48

------------------------------------------------------------------------
On 2009-11-08T17:29:22+00:00 Andi-clemens wrote:

*** Bug 213692 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/49

------------------------------------------------------------------------
On 2009-11-09T10:42:05+00:00 Andi-clemens wrote:

Well as you can see, the report has been marked as FIXED, so sure the new beta will have this fix in it.
Also notice that digiKam-1.0.0-beta6 has been released today :-)

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/50

------------------------------------------------------------------------
On 2009-11-09T10:45:44+00:00 Andi-clemens wrote:

*** Bug 212665 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/51

------------------------------------------------------------------------
On 2009-11-09T13:08:08+00:00 Philippe-roubach wrote:

many thanks

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/54

------------------------------------------------------------------------
On 2009-11-10T21:17:57+00:00 Andi-clemens wrote:

*** Bug 214031 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/55

------------------------------------------------------------------------
On 2009-11-11T19:46:32+00:00 Andi-clemens wrote:

*** Bug 214132 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/56

------------------------------------------------------------------------
On 2009-11-11T19:46:59+00:00 Andi-clemens wrote:

*** Bug 214119 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/57

------------------------------------------------------------------------
On 2009-11-11T21:52:04+00:00 Dario Andres wrote:

*** Bug 214144 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/58

------------------------------------------------------------------------
On 2009-11-12T14:06:13+00:00 Andi-clemens wrote:

*** Bug 214261 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/59

------------------------------------------------------------------------
On 2009-11-12T19:17:13+00:00 Andi-clemens wrote:

*** Bug 214293 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/60

------------------------------------------------------------------------
On 2009-11-12T22:25:56+00:00 Andi-clemens wrote:

*** Bug 214310 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/61

------------------------------------------------------------------------
On 2009-11-13T00:55:32+00:00 Luka Renko wrote:

Test packages for Ubuntu Karmic are available in my PPA:
https://launchpad.net/~lure/+archive/ppa

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/64

------------------------------------------------------------------------
On 2009-11-13T09:25:58+00:00 Andi-clemens wrote:

The problem is that if Ubuntu is not updating the package, most users might not be aware of the new beta versions.
Having new versions in an PPA is nice, but will users use it? I doubt it. I still hope Ubuntu will update the digiKam package themselves, they can't just add a beta version and keep it as the official stable digiKam release in their branch.

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/65

------------------------------------------------------------------------
On 2009-11-13T09:46:16+00:00 Luka Renko wrote:

The plan is to get this to standard Karmic backports repository, so it
will be easy to get it for users. PPA is only for testing.

I agree that shipping beta version is bad, but this is also due to release plans for digikam being changed - at the beginning of the cycle it looked like digikam 1.0.0 might be just in time for Karmic (this is why somebody merged beta from debian unstable), but then this has changed. Before Karmic release I could only update to latest beta5, as going back to 0.10.0 was not much better decision either.
I hope we can control the grief with regular updates through backports.

And BTW, even with Beta6, there is report that at least one import crasher is still there:
https://bugs.edge.launchpad.net/ubuntu/+source/digikam/+bug/454113/comments/11

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/66

------------------------------------------------------------------------
On 2009-11-13T09:54:22+00:00 Andi-clemens wrote:

But this crash is not related, at least not to the problem described in here.
We had a bad pointer for the SelectAlbum dialog, but the one you just mentioned is something totally different and might even be unrelated to importing images at all (just a coincidence).
I tested importing so many times now, imported 20.000 images from a harddisk folder (to test threading problems), imported images from my NikonD50 with PTP and from my cardreader, all works fine here.
The link you gave looks more like a general memory problem, I see a lot of malloc problems in there.

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/67

------------------------------------------------------------------------
On 2009-11-13T15:40:57+00:00 Jonah-dorman wrote:

Hey guys,

Should I use the PPA packages, look for an update from backports, look
for an official ubuntu update, do nothing, or stop using the program?

Just throwing it out there, I wasn't importing anything, I was trying to
tag a bunch of pictures.  Not sure that is a duplicate of this bug?

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/71

------------------------------------------------------------------------
On 2009-11-14T13:08:27+00:00 Playinguitar2007 wrote:

Not sure if it is related to the original bug but it does work ok with Picasa.  Looking forward to a fix for this, I like Digikam... 
 
D

--- On Fri, 11/13/09, Andi Clemens <andi.clemens at gmx.net> wrote:


From: Andi Clemens <andi.clemens at gmx.net>
Subject: [Bug 210462] digikam crash select new download
To: playinguitar2007 at yahoo.com
Date: Friday, November 13, 2009, 3:54 AM


https://bugs.kde.org/show_bug.cgi?id=210462



--- Comment #55 from Andi Clemens <andi clemens gmx net>  2009-11-13 09:54:22 ---
But this crash is not related, at least not to the problem described in here.
We had a bad pointer for the SelectAlbum dialog, but the one you just mentioned
is something totally different and might even be unrelated to importing images
at all (just a coincidence).
I tested importing so many times now, imported 20.000 images from a harddisk
folder (to test threading problems), imported images from my NikonD50 with PTP
and from my cardreader, all works fine here.
The link you gave looks more like a general memory problem, I see a lot of
malloc problems in there.

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/73

------------------------------------------------------------------------
On 2009-11-15T23:44:50+00:00 Dario Andres wrote:

*** Bug 214732 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/74

------------------------------------------------------------------------
On 2009-11-16T10:46:06+00:00 Andi-clemens wrote:

*** Bug 214778 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/75

------------------------------------------------------------------------
On 2009-11-16T10:46:35+00:00 Andi-clemens wrote:

*** Bug 214763 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/76

------------------------------------------------------------------------
On 2009-11-16T22:49:50+00:00 Andi-clemens wrote:

*** Bug 214883 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/77

------------------------------------------------------------------------
On 2009-11-17T17:15:36+00:00 Andi-clemens wrote:

*** Bug 214988 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/78

------------------------------------------------------------------------
On 2009-11-17T19:01:38+00:00 Andi-clemens wrote:

*** Bug 214999 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/79

------------------------------------------------------------------------
On 2009-11-17T19:44:36+00:00 Andi-clemens wrote:

*** Bug 215005 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/80

------------------------------------------------------------------------
On 2009-11-18T01:47:51+00:00 Dario Andres wrote:

*** Bug 214874 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/81

------------------------------------------------------------------------
On 2009-11-18T01:47:53+00:00 Dario Andres wrote:

*** Bug 215021 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/82

------------------------------------------------------------------------
On 2009-11-19T22:53:29+00:00 Andi-clemens wrote:

*** Bug 215330 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/83

------------------------------------------------------------------------
On 2009-11-21T10:00:29+00:00 Andi-clemens wrote:

*** Bug 215524 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/84

------------------------------------------------------------------------
On 2009-11-21T10:01:31+00:00 Andi-clemens wrote:

*** Bug 215100 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/85

------------------------------------------------------------------------
On 2009-11-22T02:12:46+00:00 Andi-clemens wrote:

*** Bug 215622 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/86

------------------------------------------------------------------------
On 2009-11-22T15:09:28+00:00 Andi-clemens wrote:

*** Bug 215679 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/87

------------------------------------------------------------------------
On 2009-11-22T16:26:02+00:00 Andi-clemens wrote:

*** Bug 215695 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/88

------------------------------------------------------------------------
On 2009-11-22T16:36:47+00:00 Andi-clemens wrote:

*** Bug 215697 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/89

------------------------------------------------------------------------
On 2009-11-24T13:28:17+00:00 Andi-clemens wrote:

*** Bug 215955 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/90

------------------------------------------------------------------------
On 2009-11-25T02:00:44+00:00 Dario Andres wrote:

*** Bug 215981 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/91

------------------------------------------------------------------------
On 2009-11-25T02:00:45+00:00 Dario Andres wrote:

*** Bug 216024 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/92

------------------------------------------------------------------------
On 2009-11-25T19:44:53+00:00 Dario Andres wrote:

*** Bug 216131 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/93

------------------------------------------------------------------------
On 2009-11-25T21:16:06+00:00 Dario Andres wrote:

*** Bug 216151 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/94

------------------------------------------------------------------------
On 2009-11-26T00:05:34+00:00 Dario Andres wrote:

*** Bug 216172 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/95

------------------------------------------------------------------------
On 2009-11-26T12:46:34+00:00 Andi-clemens wrote:

*** Bug 216206 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/96

------------------------------------------------------------------------
On 2009-11-26T14:59:53+00:00 Andi-clemens wrote:

*** Bug 216257 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/97

------------------------------------------------------------------------
On 2009-11-26T22:06:35+00:00 Andi-clemens wrote:

*** Bug 216311 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/98

------------------------------------------------------------------------
On 2009-11-27T12:47:09+00:00 Andi-clemens wrote:

*** Bug 216373 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/99

------------------------------------------------------------------------
On 2009-11-27T16:23:15+00:00 Andi-clemens wrote:

*** Bug 216389 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/100

------------------------------------------------------------------------
On 2009-11-28T16:52:41+00:00 Andi-clemens wrote:

*** Bug 216523 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/101

------------------------------------------------------------------------
On 2009-11-28T23:31:16+00:00 Andi-clemens wrote:

*** Bug 216571 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/102

------------------------------------------------------------------------
On 2009-11-28T23:39:34+00:00 Andi-clemens wrote:

PLEEEEEEEEEEEEAAAAAAAAAAAAAAASEEEEEEEEEEEEE UBUNTU:
If you decide to add a beta version into your stable release, PLEEEAAAAAAAAASE at least update the packages now. Beta6 has been released nearly three weeks ago.
I'm really annoyed marking this bug 10 times a day as a duplicate...
I guess I will post this in Ubuntu's bugtracker now...

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/103

------------------------------------------------------------------------
On 2009-11-29T13:30:35+00:00 Andi-clemens wrote:

*** Bug 216646 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/104

------------------------------------------------------------------------
On 2009-11-29T19:05:50+00:00 Dario Andres wrote:

*** Bug 216697 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/106

------------------------------------------------------------------------
On 2009-11-29T22:31:16+00:00 Linolizard wrote:

On Saturday 28 November 2009 10:39:44 pm Andi Clemens wrote:
> https://bugs.kde.org/show_bug.cgi?id=210462
> 
> 
> 
> 
> 
> --- Comment #87 from Andi Clemens <andi clemens gmx net>  2009-11-28
>  23:39:34 --- PLEEEEEEEEEEEEAAAAAAAAAAAAAAASEEEEEEEEEEEEE UBUNTU:
> If you decide to add a beta version into your stable release,
>  PLEEEAAAAAAAAASE at least update the packages now. Beta6 has been released
>  nearly three weeks ago.
> I'm really annoyed marking this bug 10 times a day as a duplicate...
> I guess I will post this in Ubuntu's bugtracker now...
> 
 I totaly agree with you......
:)
Lisandro.

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/107

------------------------------------------------------------------------
On 2009-11-30T09:09:54+00:00 Andi-clemens wrote:

*** Bug 216755 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/108

------------------------------------------------------------------------
On 2009-11-30T10:54:36+00:00 Philippe-roubach wrote:

(In reply to comment #87)
> PLEEEEEEEEEEEEAAAAAAAAAAAAAAASEEEEEEEEEEEEE UBUNTU:
> If you decide to add a beta version into your stable release, PLEEEAAAAAAAAASE
> at least update the packages now. Beta6 has been released nearly three weeks
> ago.
> I'm really annoyed marking this bug 10 times a day as a duplicate...
> I guess I will post this in Ubuntu's bugtracker now...

i help you
i ask for Mandriva team to update to 1.0.0b6
they already udpated to kipi-plugins 0.8 but curiously not digikam

see my report

https://qa.mandriva.com/show_bug.cgi?id=56078

thanks for your work

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/109

------------------------------------------------------------------------
On 2009-11-30T11:02:14+00:00 Neoclust-kde wrote:

i will update to RC when available

---
Nicolas Lécureuil
Mandriva KDE Team

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/110

------------------------------------------------------------------------
On 2009-11-30T11:25:16+00:00 Philippe-roubach wrote:

(In reply to comment #93)
> i will update to RC when available
> 
> ---
> Nicolas Lécureuil
> Mandriva KDE Team

ok thanks

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/111

------------------------------------------------------------------------
On 2009-12-02T17:34:09+00:00 Dario Andres wrote:

*** Bug 217085 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/112

------------------------------------------------------------------------
On 2009-12-05T11:52:45+00:00 Andi-clemens wrote:

*** Bug 217421 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/113

------------------------------------------------------------------------
On 2009-12-05T18:44:46+00:00 Dario Andres wrote:

*** Bug 217458 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/114

------------------------------------------------------------------------
On 2009-12-05T23:34:07+00:00 Dario Andres wrote:

*** Bug 217496 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/115

------------------------------------------------------------------------
On 2009-12-06T00:28:31+00:00 FiNeX wrote:

*** Bug 217514 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/116

------------------------------------------------------------------------
On 2009-12-07T13:11:46+00:00 Dario Andres wrote:

*** Bug 217708 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/119

------------------------------------------------------------------------
On 2009-12-08T20:54:57+00:00 Andi-clemens wrote:

*** Bug 217915 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/120

------------------------------------------------------------------------
On 2009-12-10T17:55:08+00:00 Dario Andres wrote:

*** Bug 218137 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/124

------------------------------------------------------------------------
On 2009-12-10T18:57:06+00:00 Kjetil Kjernsmo wrote:

FWIW, there has been a backport of the recent RC to Karmic, so the
Ubuntu users who are bitten by this bug should enable backports, that
is, have this in their /etc/apt/sources.list

deb http://no.archive.ubuntu.com/ubuntu/ karmic-backports main restricted universe multiverse
deb-src http://no.archive.ubuntu.com/ubuntu/ karmic-backports main restricted universe multiverse

I personally think it should be in an karmic-update also, since that is
seen by more people without any action.

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/125

------------------------------------------------------------------------
On 2009-12-10T20:20:29+00:00 Luka Renko wrote:

I plan to ask Ubuntu release team for exception for 1.0.0 final release to get it into karmic-updates. Problem is that they will need to bend the rules a bit to allow to get it through:
https://wiki.ubuntu.com/StableReleaseUpdates

I am sorry that Digikam 1.0.0 release plan was shifted in a way that did
not work for Ubuntu 9.10 and that we did not switch back to 0.10 before
release.

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/126

------------------------------------------------------------------------
On 2009-12-10T21:36:12+00:00 Dario Andres wrote:

*** Bug 218160 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/127

------------------------------------------------------------------------
On 2009-12-13T14:31:15+00:00 Andi-clemens wrote:

*** Bug 218518 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/128

------------------------------------------------------------------------
On 2009-12-14T18:33:06+00:00 Dario Andres wrote:

*** Bug 216940 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/129

------------------------------------------------------------------------
On 2009-12-14T19:52:32+00:00 Dario Andres wrote:

*** Bug 218669 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/130

------------------------------------------------------------------------
On 2009-12-17T17:58:37+00:00 Dario Andres wrote:

*** Bug 219088 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/131

------------------------------------------------------------------------
On 2009-12-20T13:35:25+00:00 Dario Andres wrote:

*** Bug 219416 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/132

------------------------------------------------------------------------
On 2009-12-21T14:29:45+00:00 W-kaftan wrote:

After updating digikam problem solved.

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/133

------------------------------------------------------------------------
On 2009-12-25T14:12:15+00:00 Dario Andres wrote:

*** Bug 220046 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/135

------------------------------------------------------------------------
On 2009-12-25T21:04:28+00:00 Johannes Wienke wrote:

*** Bug 220089 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/136

------------------------------------------------------------------------
On 2009-12-25T22:15:18+00:00 Johannes Wienke wrote:

*** Bug 220099 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/137

------------------------------------------------------------------------
On 2010-01-04T23:24:05+00:00 Dario Andres wrote:

*** Bug 221283 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/139

------------------------------------------------------------------------
On 2010-01-05T12:31:16+00:00 Dario Andres wrote:

*** Bug 221368 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/140

------------------------------------------------------------------------
On 2010-01-08T23:44:04+00:00 Johannes Wienke wrote:

*** Bug 221861 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/141

------------------------------------------------------------------------
On 2010-01-15T00:33:57+00:00 Dario Andres wrote:

*** Bug 222778 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/142

------------------------------------------------------------------------
On 2010-01-17T09:07:51+00:00 Caulier-gilles-9 wrote:

*** Bug 223059 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/143

------------------------------------------------------------------------
On 2010-01-20T00:58:28+00:00 Dario Andres wrote:

*** Bug 223507 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/144

------------------------------------------------------------------------
On 2010-01-20T09:34:19+00:00 Julien wrote:

*** Bug 223535 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/145

------------------------------------------------------------------------
On 2010-01-22T02:23:39+00:00 Dario Andres wrote:

*** Bug 223732 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/146

------------------------------------------------------------------------
On 2010-01-23T07:22:30+00:00 Julien wrote:

*** Bug 223879 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/147

------------------------------------------------------------------------
On 2010-01-24T20:04:09+00:00 Dario Andres wrote:

*** Bug 224066 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/148

------------------------------------------------------------------------
On 2010-01-24T22:14:42+00:00 S-t-kdebugs wrote:

Can somebody familiar with the digikam source code point out a
small/simple/self-contained patch that can be added to the Ubuntu
package that will fix this bug? Or at least, does anyone know which
specific checkin to digikam resolved this?

(Yes, I agree that it's retarded Ubuntu won't upgrade from the beta
version, but if the individual patch for this bug is small enough,
perhaps it can be applied to the beta version and at least you'll stop
getting so many dup reports...)

As an aside, I wonder if the KDE license should be altered to require
packagers not to package beta versions, or to force them to update?

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/149

------------------------------------------------------------------------
On 2010-01-27T13:10:32+00:00 Dario Andres wrote:

It seems that the commits that modified the code mentioned in this bug are:
http://websvn.kde.org/?view=revision&revision=1035079
http://websvn.kde.org/?view=revision&revision=1035122

The last one fixes the cast, so It should be related to the issue.

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/150

------------------------------------------------------------------------
On 2010-01-27T17:16:25+00:00 Dario Andres wrote:

*** Bug 224468 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/151

------------------------------------------------------------------------
On 2010-01-28T07:10:50+00:00 S-t-kdebugs wrote:

Dario, thanks for trying to help me out. Unfortunately, neither of those
changes solve the problem. The place where the crash is happening /is/
right where those changes were made. However, the problem isn't simply
dereferencing a NULL pointer. In particular, this line crashes:

    return (dynamic_cast<PAlbum*>(item->album()));

and gdb says:

(gdb) p item
$1 = (class Digikam::TreeAlbumItem *) 0xc828820
(gdb) p item->album()
$2 = (class Digikam::Album *) 0x30

So, the pointer isn't NULL, which is why the additional NULL checks
didn't help, but the pointer also doesn't look valid. Since the album()
function is trivial (just returning a member variable), I guess there's
some kind of general memory corruption. This is especially true, since
anywhere that m_album is set in treefolderitem.cpp, the code immediately
indirects through it, so the value must have been valid at some time,
then become trashed later.

:-(

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/152

------------------------------------------------------------------------
On 2010-01-28T12:35:24+00:00 Dario Andres wrote:

Then I guess you should wait for the Digikam devs to look at this, or search the commits near the ones I posted. 
Regards

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/153

------------------------------------------------------------------------
On 2010-01-30T10:43:30+00:00 Johannes Wienke wrote:

*** Bug 224852 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/154

------------------------------------------------------------------------
On 2010-01-30T20:31:07+00:00 Johannes Wienke wrote:

*** Bug 224911 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/155

------------------------------------------------------------------------
On 2010-01-31T14:14:27+00:00 Johannes Wienke wrote:

*** Bug 225000 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/156

------------------------------------------------------------------------
On 2010-01-31T16:03:07+00:00 Johannes Wienke wrote:

*** Bug 225015 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/157

------------------------------------------------------------------------
On 2010-01-31T16:54:04+00:00 Dario Andres wrote:

*** Bug 225017 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/158

------------------------------------------------------------------------
On 2010-01-31T23:27:16+00:00 Dario Andres wrote:

*** Bug 225060 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/159

------------------------------------------------------------------------
On 2010-02-01T22:08:00+00:00 Johannes Wienke wrote:

*** Bug 225197 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/160

------------------------------------------------------------------------
On 2010-02-08T16:07:33+00:00 Johannes Wienke wrote:

*** Bug 225919 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/161

------------------------------------------------------------------------
On 2010-02-15T16:13:24+00:00 Dario Andres wrote:

*** Bug 227013 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/162

------------------------------------------------------------------------
On 2010-02-16T01:20:42+00:00 Dario Andres wrote:

*** Bug 227102 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/163

------------------------------------------------------------------------
On 2010-02-27T13:50:25+00:00 Johannes Wienke wrote:

*** Bug 228744 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/165

------------------------------------------------------------------------
On 2010-03-06T12:52:34+00:00 Dario Andres wrote:

*** Bug 229674 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/166

------------------------------------------------------------------------
On 2010-03-12T16:49:39+00:00 Dario Andres wrote:

*** Bug 230464 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/167

------------------------------------------------------------------------
On 2010-03-12T20:28:15+00:00 Dario Andres wrote:

*** Bug 230464 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/168

------------------------------------------------------------------------
On 2010-03-14T23:44:08+00:00 Dario Andres wrote:

*** Bug 230761 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/169

------------------------------------------------------------------------
On 2010-03-15T22:08:14+00:00 Dario Andres wrote:

*** Bug 230837 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/170

------------------------------------------------------------------------
On 2010-03-19T18:03:14+00:00 Dario Andres wrote:

*** Bug 231332 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/171

------------------------------------------------------------------------
On 2010-03-21T00:26:54+00:00 Dario Andres wrote:

*** Bug 231481 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/172

------------------------------------------------------------------------
On 2010-03-22T22:38:31+00:00 Dario Andres wrote:

*** Bug 231798 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/173

------------------------------------------------------------------------
On 2010-03-28T18:39:06+00:00 Dario Andres wrote:

*** Bug 232488 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/174

------------------------------------------------------------------------
On 2010-04-04T14:28:22+00:00 Dario Andres wrote:

*** Bug 233228 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/175

------------------------------------------------------------------------
On 2010-04-11T14:50:12+00:00 Dario Andres wrote:

*** Bug 234043 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/176

------------------------------------------------------------------------
On 2010-06-22T00:05:46+00:00 Caulier-gilles-9 wrote:

*** Bug 242411 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/digikam/+bug/454113/comments/177


** Bug watch added: Mandriva Linux #56078
   http://qa.mandriva.com/show_bug.cgi?id=56078

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to digikam in Ubuntu.
https://bugs.launchpad.net/bugs/454113

Title:
  digikam crashes when click on download selected

To manage notifications about this bug go to:
https://bugs.launchpad.net/digikam/+bug/454113/+subscriptions




More information about the kubuntu-bugs mailing list