Bug 172680 - Digikam crashes when I try to download the photos from my camera
Summary: Digikam crashes when I try to download the photos from my camera
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Import-Gphoto2 (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-12 21:30 UTC by Milko Krachounov
Modified: 2017-08-16 06:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 0.10.0
Sentry Crash Report:


Attachments
Crash backtrace (6.33 KB, text/plain)
2008-10-12 21:31 UTC, Milko Krachounov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Milko Krachounov 2008-10-12 21:30:13 UTC
Version:            (using KDE 4.1.2)
Compiler:          gcc 4.3.1 
OS:                Linux
Installed from:    Gentoo Packages

I'm experiencing a crash when I try to download the photos from my camera when using the following two configurations:
- digiKam 0.10.0 beta 2 on Qt 4.4.2/KDE 4.1.2
- digiKam 0.10.0 beta 4 on Qt 4.4.2/KDE 4.1.2/libkdcraw from kdegraphics 4.1.69

Everything is compiled with gcc 4.3.1 and is running on a x86_64 machine.  

The crash occurs at the moment I try to open the camera (e.g. I click on it in the main menu). After this, the camera is inaccessible from other applications until I reconnect it, or turn it on and off. A subsequent try to open it from digiKam without doing so, doesn't result in a crash, just it waits indefinitely for the camera, until I close the window. 

The camera is Nikon D200 running in PTP mode.

I will attach a backtrace shortly.
Comment 1 Milko Krachounov 2008-10-12 21:31:04 UTC
Created attachment 27836 [details]
Crash backtrace
Comment 2 engage 2008-11-04 00:52:47 UTC
Digikam crashes when attempting to d/l my images also. KDE 3.5, Mandriva 2009.0, digikam-0.10.0-1.beta3.2mdv2009.0. Debug output:

Application: digiKam (digikam), signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb4ac76d0 (LWP 17574)]
[New Thread 0xb3248b90 (LWP 17597)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xffffe424 in __kernel_vsyscall ()
#7  0xb593ed90 in raise () from /lib/i686/libc.so.6
#8  0xb59407f8 in abort () from /lib/i686/libc.so.6
#9  0xb6839445 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb6839535 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb68395e5 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb7eb3d9e in Digikam::DatabaseAccess::assertNoLock ()
   from /usr/lib/libdigikamdatabase.so.1
#13 0xb7eafef2 in Digikam::CollectionManager::updateLocations ()
   from /usr/lib/libdigikamdatabase.so.1
#14 0xb7eb25d9 in Digikam::CollectionManager::refresh ()
   from /usr/lib/libdigikamdatabase.so.1
#15 0xb7eb525e in Digikam::DatabaseAccess::checkReadyForUse ()
   from /usr/lib/libdigikamdatabase.so.1
#16 0x082aad18 in Digikam::ScanController::run ()
#17 0xb684189f in ?? () from /usr/lib/libQtCore.so.4
#18 0xb5903315 in start_thread () from /lib/i686/libpthread.so.0
#19 0xb59eddde in clone () from /lib/i686/libc.so.6

Thread 1 (Thread 0xb4ac76d0 (LWP 17574)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb5906b95 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/i686/libpthread.so.0
#2  0xb59fb21d in pthread_cond_wait () from /lib/i686/libc.so.6
#3  0xb68429ab in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb6841a51 in QThread::wait () from /usr/lib/libQtCore.so.4
#5  0x082aaa4f in Digikam::ScanController::shutDown ()
#6  0x082abfbf in Digikam::ScanController::~ScanController ()
#7  0x082ac107 in ?? ()
#8  0xb5941e69 in exit () from /lib/i686/libc.so.6
#9  0xb6050e68 in ?? () from /usr/lib/libQtGui.so.4
#10 0xb6ebb0e9 in KApplication::xioErrhandler () from /usr/lib/libkdeui.so.5
#11 0xb6ebb124 in ?? () from /usr/lib/libkdeui.so.5
#12 0xb5654026 in _XIOError () from /usr/lib/libX11.so.6
#13 0xb565cc8b in ?? () from /usr/lib/libX11.so.6
#14 0x092b25c8 in ?? ()
#15 0x00000000 in ?? ()
Comment 3 caulier.gilles 2008-11-04 09:11:18 UTC
Marcel,

Look like there is a lock with database when a new file is insserted in album collections...

Gilles Caulier
Comment 4 Marcel Wiesweg 2008-11-17 22:39:16 UTC
We must pay attention, this can be misleading:
The thread backtrace which sends the abort is clearly because of a locked db that should not be locked,
but looking at the main thread backtrace, you see that it is attempting shutdown out of the middle of operation because of an XIO Error caught by KApplication.
I found this message regarding the topic:

http://lists.kde.org/?l=kde-devel&m=121673396224505&w=2

where it is suggested to run the application with the --sync option to possibly get more information.
Comment 5 Marcel Wiesweg 2008-11-28 19:41:16 UTC
We recently fixed a crash in the gphoto code which could be the cause of this. Can you please retest with current svn or beta6?
Comment 6 Milko Krachounov 2008-11-28 20:22:51 UTC
The crash doesn't happen with me anymore with beta6, so I'm almost certain that at least my crash got fixed, so now I can download photos without any problem. Thanks. :)