Bug 293492 - digikam crash on import from canon powershot a2200
Summary: digikam crash on import from canon powershot a2200
Status: RESOLVED UPSTREAM
Alias: None
Product: digikam
Classification: Applications
Component: Import-Gphoto2 (show other bugs)
Version: 2.5.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-06 23:41 UTC by graham
Modified: 2022-01-24 20:49 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.6.0


Attachments
New crash information added by DrKonqi (7.11 KB, text/plain)
2012-02-07 00:01 UTC, graham
Details
New crash information added by DrKonqi (6.74 KB, text/plain)
2013-09-17 16:38 UTC, alainthiaville59
Details
New crash information added by DrKonqi (5.26 KB, text/plain)
2013-10-02 15:56 UTC, alainthiaville59
Details
New crash information added by DrKonqi (12.86 KB, text/plain)
2013-12-02 11:16 UTC, Simone Sapienza
Details

Note You need to log in before you can comment on or make changes to this bug.
Description graham 2012-02-06 23:41:02 UTC
Application: digikam (2.5.0)
KDE Platform Version: 4.6.5 (4.6.5)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-13-generic i686
Distribution: Ubuntu 11.04

-- Information about the crash:
- What I was doing when the application crashed:
Plugged in canon powershot a2200 via USB and attempted to import photos

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

Thread 10 (Thread 0xb3c22b70 (LWP 3183)):
#0  0x008d07af in __pthread_mutex_unlock_usercnt () from /lib/i386-linux-gnu/libpthread.so.0
#1  0x0221f656 in pthread_mutex_unlock () from /lib/i386-linux-gnu/libc.so.6
#2  0x0283a0b4 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x0283a92b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x04679304 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#5  0x028632df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6  0x0386470c in ?? () from /usr/lib/nvidia-current/libGL.so.1
#7  0x00000000 in ?? ()

Thread 9 (Thread 0xb0bcbb70 (LWP 3186)):
#0  0x00dbb416 in __kernel_vsyscall ()
#1  0x008d148c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0x0221f3fd in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0x01f10467 in wait (this=0xa77b3dc, mutex=0xa77b3d8, time=4294967295) at thread/qwaitcondition_unix.cpp:88
#4  QWaitCondition::wait (this=0xa77b3dc, mutex=0xa77b3d8, time=4294967295) at thread/qwaitcondition_unix.cpp:160
#5  0x081eeec9 in Digikam::ScanController::run (this=0xa771ec8) at /build/buildd/digikam-2.5.0/core/digikam/database/scancontroller.cpp:647
#6  0x01f0fda2 in QThreadPrivate::start (arg=0xa771ec8) at thread/qthread_unix.cpp:320
#7  0x0386470c in ?? () from /usr/lib/nvidia-current/libGL.so.1
#8  0x00000000 in ?? ()

Thread 8 (Thread 0xb03cab70 (LWP 3187)):
#0  0x08e79d41 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1
#1  0x01f65dd8 in do_gettime () at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0x020324f2 in updateCurrentTime (this=0xb330dd3c, tm=...) at kernel/qeventdispatcher_unix.cpp:339
#4  QTimerInfoList::timerWait (this=0xb330dd3c, tm=...) at kernel/qeventdispatcher_unix.cpp:442
#5  0x02030d32 in timerSourcePrepareHelper (src=<value optimized out>, timeout=0xb03c9e6c) at kernel/qeventdispatcher_glib.cpp:136
#6  0x02030dcd in timerSourcePrepare (source=0xb330dd08, timeout=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#7  0x02838fd4 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0x02839e63 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0x0283a524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0x02031577 in QEventDispatcherGlib::processEvents (this=0xa72a3a0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#11 0x02003289 in QEventLoop::processEvents (this=0xb03ca020, flags=...) at kernel/qeventloop.cpp:149
#12 0x02003522 in QEventLoop::exec (this=0xb03ca020, flags=...) at kernel/qeventloop.cpp:201
#13 0x01f0d2a0 in QThread::exec (this=0xa73c560) at thread/qthread.cpp:492
#14 0x01fe4fdb in QInotifyFileSystemWatcherEngine::run (this=0xa73c560) at io/qfilesystemwatcher_inotify.cpp:248
#15 0x01f0fda2 in QThreadPrivate::start (arg=0xa73c560) at thread/qthread_unix.cpp:320
#16 0x0386470c in ?? () from /usr/lib/nvidia-current/libGL.so.1
#17 0x00000000 in ?? ()

Thread 7 (Thread 0xafbc9b70 (LWP 3191)):
#0  0x00dbb416 in __kernel_vsyscall ()
#1  0x008d148c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0x0221f3fd in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0x01f10467 in wait (this=0xaa937b0, mutex=0xaa937ac, time=4294967295) at thread/qwaitcondition_unix.cpp:88
#4  QWaitCondition::wait (this=0xaa937b0, mutex=0xaa937ac, time=4294967295) at thread/qwaitcondition_unix.cpp:160
#5  0x018e526a in Digikam::ParkingThread::run (this=0xaa937a0) at /build/buildd/digikam-2.5.0/core/libs/threads/threadmanager.cpp:119
#6  0x01f0fda2 in QThreadPrivate::start (arg=0xaa937a0) at thread/qthread_unix.cpp:320
#7  0x0386470c in ?? () from /usr/lib/nvidia-current/libGL.so.1
#8  0x00000000 in ?? ()

Thread 6 (Thread 0xa664cb70 (LWP 3206)):
#0  0x00dbb416 in __kernel_vsyscall ()
#1  0x008d1834 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0x0221f454 in pthread_cond_timedwait () from /lib/i386-linux-gnu/libc.so.6
#3  0x040f5963 in ?? () from /usr/lib/libxine.so.1
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 5 (Thread 0xa523fb70 (LWP 3208)):
#0  0x00dbb416 in __kernel_vsyscall ()
#1  0x02202f76 in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0x02c6bfe0 in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1
#3  0x02c6c5b5 in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1
#4  0x02c6ce25 in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1
#5  0x02c6d9dd in xcb_wait_for_reply () from /usr/lib/i386-linux-gnu/libxcb.so.1
#6  0x02c71e3b in xcb_intern_atom_reply () from /usr/lib/i386-linux-gnu/libxcb.so.1
#7  0x045ae5c8 in ?? () from /usr/lib/xine/plugins/1.29/xineplug_vo_out_xcbxv.so
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 4 (Thread 0xa4a3eb70 (LWP 3209)):
#0  0x00dbb416 in __kernel_vsyscall ()
#1  0x02202f76 in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0x00e814a2 in ?? () from /usr/lib/libpulse.so.0
#3  0x00e703a9 in pa_mainloop_poll () from /usr/lib/libpulse.so.0
#4  0x00e70b84 in pa_mainloop_iterate () from /usr/lib/libpulse.so.0
#5  0x00e70c64 in pa_mainloop_run () from /usr/lib/libpulse.so.0
#6  0x00e81443 in ?? () from /usr/lib/libpulse.so.0
#7  0x07ddfa75 in ?? () from /usr/lib/libpulsecommon-0.9.22.so
#8  0x0386470c in ?? () from /usr/lib/nvidia-current/libGL.so.1
#9  0x00000000 in ?? ()

Thread 3 (Thread 0x9feffb70 (LWP 3210)):
#0  0x00dbb416 in __kernel_vsyscall ()
#1  0x008d148c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0x0221f3fd in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0x04108870 in ?? () from /usr/lib/libxine.so.1
#4  0x00000001 in ?? ()

Thread 2 (Thread 0x97affb70 (LWP 4459)):
[KCrash Handler]
#7  0x08382ff3 in Digikam::GPCamera::getItemInfoInternal (this=0xc15c500, folder=..., itemName=..., info=..., useMetadata=true) at /build/buildd/digikam-2.5.0/core/utilities/cameragui/devices/gpcamera.cpp:840
#8  0x0838a535 in Digikam::GPCamera::getItemsInfoList (this=0xc15c500, folder=..., useMetadata=true, items=...) at /build/buildd/digikam-2.5.0/core/utilities/cameragui/devices/gpcamera.cpp:793
#9  0x083abc00 in Digikam::CameraController::executeCommand (this=0xc11e8e0, cmd=0xb743fe0) at /build/buildd/digikam-2.5.0/core/utilities/cameragui/controller/cameracontroller.cpp:489
#10 0x083b59eb in Digikam::CameraController::run (this=0xc11e8e0) at /build/buildd/digikam-2.5.0/core/utilities/cameragui/controller/cameracontroller.cpp:396
#11 0x01f0fda2 in QThreadPrivate::start (arg=0xc11e8e0) at thread/qthread_unix.cpp:320
#12 0x0386470c in ?? () from /usr/lib/nvidia-current/libGL.so.1
#13 0x00000000 in ?? ()

Thread 1 (Thread 0xb3e858d0 (LWP 3181)):
#0  0x00dbb416 in __kernel_vsyscall ()
#1  0x008d1834 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0x0221f454 in pthread_cond_timedwait () from /lib/i386-linux-gnu/libc.so.6
#3  0x01f0fafe in thread_sleep (ti=<value optimized out>) at thread/qthread_unix.cpp:470
#4  0x01f0fc53 in QThread::msleep (msecs=200) at thread/qthread_unix.cpp:496
#5  0x0909ee24 in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#6  0x0909ef92 in ?? () from /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so
#7  0x00caac3d in ?? () from /usr/lib/libphonon.so.4
#8  0x00caada2 in ?? () from /usr/lib/libphonon.so.4
#9  0x00ca90f5 in ?? () from /usr/lib/libphonon.so.4
#10 0x00ca563b in ?? () from /usr/lib/libphonon.so.4
#11 0x02170a6f in ?? () from /lib/i386-linux-gnu/libc.so.6
#12 0x02170acf in exit () from /lib/i386-linux-gnu/libc.so.6
#13 0x031e3a90 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#14 0x01ce507a in KApplication::xioErrhandler (this=0xbfcb11bc, dpy=0xa590430) at ../../kdeui/kernel/kapplication.cpp:419
#15 0x01ce50b6 in kde_xio_errhandler (dpy=0xa590430) at ../../kdeui/kernel/kapplication.cpp:126
#16 0x022dc166 in _XIOError () from /usr/lib/i386-linux-gnu/libX11.so.6
#17 0x022d981f in _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6
#18 0x022ca4eb in XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6
#19 0x04c69fc5 in x11EventSourceCheck (s=0xa5807a8) at kernel/qguieventdispatcher_glib.cpp:85
#20 0x0283971d in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0
#21 0x0283a03a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#22 0x0283a524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#23 0x0203153c in QEventDispatcherGlib::processEvents (this=0xa51fd70, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#24 0x04c6a1e5 in QGuiEventDispatcherGlib::processEvents (this=0xa51fd70, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#25 0x02003289 in QEventLoop::processEvents (this=0xbfcb1084, flags=...) at kernel/qeventloop.cpp:149
#26 0x02003522 in QEventLoop::exec (this=0xbfcb1084, flags=...) at kernel/qeventloop.cpp:201
#27 0x02007ecc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#28 0x04bb18e7 in QApplication::exec () at kernel/qapplication.cpp:3736
#29 0x082c3183 in main (argc=) at /build/buildd/digikam-2.5.0/core/digikam/main/main.cpp:232

Reported using DrKonqi
Comment 1 graham 2012-02-07 00:01:39 UTC
Created attachment 68581 [details]
New crash information added by DrKonqi

digikam (2.5.0) on KDE Platform 4.6.5 (4.6.5) using Qt 4.7.2

- What I was doing when the application crashed: same as before - plugged in Canon powershot a2200 and tried to import. Have tried both manually attaching camera and autodetecting. Same result each time - application just dies.

-- Backtrace (Reduced):
#7  0x08382ff3 in Digikam::GPCamera::getItemInfoInternal (this=0x9f9f7b0, folder=..., itemName=..., info=..., useMetadata=true) at /build/buildd/digikam-2.5.0/core/utilities/cameragui/devices/gpcamera.cpp:840
#8  0x0838a535 in Digikam::GPCamera::getItemsInfoList (this=0x9f9f7b0, folder=..., useMetadata=true, items=...) at /build/buildd/digikam-2.5.0/core/utilities/cameragui/devices/gpcamera.cpp:793
#9  0x083abc00 in Digikam::CameraController::executeCommand (this=0xb62ef80, cmd=0xb548db0) at /build/buildd/digikam-2.5.0/core/utilities/cameragui/controller/cameracontroller.cpp:489
#10 0x083b59eb in Digikam::CameraController::run (this=0xb62ef80) at /build/buildd/digikam-2.5.0/core/utilities/cameragui/controller/cameracontroller.cpp:396
#11 0x06c8cda2 in QThreadPrivate::start (arg=0xb62ef80) at thread/qthread_unix.cpp:320
Comment 2 caulier.gilles 2012-02-07 06:22:41 UTC
It sound like a GPhoto2 driver problem used with Canon camera. It still crashing using a memory card reader instead ?

Which Gphoto2 version you use ?

Gilles Caulier
Comment 3 graham 2012-02-10 10:38:04 UTC
Sorry for the delay in replying.

Here is the data from 'Component information'

digiKam version 2.5.0
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibClapack: internal library
LibExiv2: 0.22
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.6.5 (4.6.5)
LibKExiv2: 2.1.0
LibKGeoMap: 2.0.0
LibKdcraw: 2.0.1
LibLCMS: 118
LibPGF: 6.11.42 - internal library
LibPNG: 1.2.44
LibQt: 4.7.2
LibRaw: 0.14.5
LibTIFF: LIBTIFF, Version 3.9.4 Copyright (c) 1988-1996 Sam Leffler
Copyright (c) 1991-1996 Silicon Graphics, Inc.
Marble Widget: 0.11.5 (Stable Release)
Parallelised demosaicing: Yes
Database backend: QSQLITE
LibGphoto2: 2.4.11
LibKface: 2.0.0
LibKipi: 1.3.0
LibOpenCV: 2.3.1
Libface: 0.2

Hope this helps.

The application crashes with the Powershot whether I use autodetect or
manually using 'USB PTP Class camera'.
No problem importing from a card reader however.

I can import successfully from my autodetected CASIO EX-P600.


On 7 February 2012 06:22, Gilles Caulier <caulier.gilles@gmail.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=293492
>
>
> Gilles Caulier <caulier.gilles@gmail.com> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                 CC|                            |caulier.gilles@gmail.com
>          Component|general                     |Import
>
>
>
>
> --- Comment #2 from Gilles Caulier <caulier gilles gmail com>  2012-02-07
> 06:22:41 ---
> It sound like a GPhoto2 driver problem used with Canon camera. It still
> crashing using a memory card reader instead ?
>
> Which Gphoto2 version you use ?
>
> Gilles Caulier
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> You reported the bug.
>
Comment 4 caulier.gilles 2012-02-10 10:43:27 UTC
yes. It's definitivly a Gphoto2 driver problem. Please report it to Gphoto2 bugzilla.

Thanks...

Gilles Caulier
Comment 5 graham 2012-02-10 10:56:27 UTC
OK will do.

Do you have a link?
A quick Google reveals Redhat and Suse Gphoto bugzillas but is there a
generic one I should use? I can keep searching but a link from you would be
quicker.

Sorry not done this stuff before.

Thanks

On 10 February 2012 10:43, Gilles Caulier <caulier.gilles@gmail.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=293492
>
>
> Gilles Caulier <caulier.gilles@gmail.com> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |RESOLVED
>         Resolution|                            |UPSTREAM
>
>
>
>
> --- Comment #4 from Gilles Caulier <caulier gilles gmail com>  2012-02-10
> 10:43:27 ---
> yes. It's definitivly a Gphoto2 driver problem. Please report it to Gphoto2
> bugzilla.
>
> Thanks...
>
> Gilles Caulier
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> You reported the bug.
>
Comment 6 caulier.gilles 2012-02-10 11:06:14 UTC
http://gphoto.sourceforge.net/feedback/

Gilles Caulier
Comment 7 caulier.gilles 2012-02-29 21:04:58 UTC
*** Bug 295062 has been marked as a duplicate of this bug. ***
Comment 8 marten@thizas.se 2012-03-01 00:10:12 UTC
it seams that not all canon cameras efects by this bug my canon powershot A480 works fine to download pics from
Comment 9 caulier.gilles 2012-03-11 17:10:03 UTC
*** Bug 295778 has been marked as a duplicate of this bug. ***
Comment 10 caulier.gilles 2012-03-11 18:16:14 UTC
*** Bug 295751 has been marked as a duplicate of this bug. ***
Comment 11 caulier.gilles 2012-10-06 15:26:34 UTC
*** Bug 307972 has been marked as a duplicate of this bug. ***
Comment 12 caulier.gilles 2013-03-03 10:38:01 UTC
*** Bug 316063 has been marked as a duplicate of this bug. ***
Comment 13 alainthiaville59 2013-09-17 16:38:32 UTC
Created attachment 82373 [details]
New crash information added by DrKonqi

digikam (3.3.0) on KDE Platform 4.10.5 using Qt 4.8.5

- Custom settings of the application:
my camera is a Canon EOS 7D. Each time i connect my camera digikam crashes.
the command is "digikam --detect-camera" 
the problem IS NOT  in (lib)gphoto2 but in digikam because: 
  a) i can upload all photos or thumbnails with the command  "ghoto2 -T --auto-detect".
  b) I can upload photos with shotwell (another app wich uses libgphoto2
  c) if i start digikam from  an another user account (with no digikam database), all thumbnails are showed and i
can upload the photos

  Hereafter the last console line in debug-mode :

digikam(19679)/digikam (core) Digikam::DigikamApp::checkSolidCamera: fillSolidMenus: Found Camera  "Canon Inc. Canon Digital Camera"  protocols  ("ptp")  drivers  ("gphoto")
digikam(19679)/digikam (core) Digikam::GPCamera::getFreeSpace: Storage description:  "CF"
digikam(19679)/digikam (core) Digikam::GPCamera::getFreeSpace: Storage base-dir:  "/store_00010001"
digikam(19679)/digikam (core) Digikam::GPCamera::getFreeSpace: Storage access: R/W
digikam(19679)/digikam (core) Digikam::GPCamera::getFreeSpace: Storage type: removable RAM
digikam(19679)/digikam (core) Digikam::GPCamera::getFreeSpace: Storage capacity:  3914048
digikam(19679)/digikam (core) Digikam::GPCamera::getFreeSpace: Storage free-space:  1774304
digikam(19679)/digikam (core) Digikam::GPCamera::getMetadata: Size of Exif metadata from camera =  28216
digikam(19679)/digikam (core) Digikam::GPCamera::getMetadata: Exif header found at position  4
digikam(19679)/KEXIV2 KExiv2Iface::KExiv2::Private::printExiv2MessageHandler: Exiv2 ( 2 ) :  Directory Thumbnail, entry 0x0201: Data area exceeds data buffer, ignoring it.
digikam(19679)/KEXIV2 KExiv2Iface::KExiv2::getImageDateTime: DateTime => Exif.Photo.DateTimeOriginal =>  QDateTime("mar. mars 26 10:03:05 2013")
digikam(19679)/digikam (core) Digikam::DMetadata::mSecTimeStamp: msec timestamp:  150
digikam(19679)/KEXIV2 KExiv2Iface::KExiv2::getImageDateTime: DateTime => Exif.Photo.DateTimeOriginal =>  QDateTime("mar. mars 26 10:03:05 2013")
KCrash: Application 'digikam' crashing...
KCrash: Attempting to start /usr/libexec/kde4/drkonqi from kdeinit
sock_file=/home/Bernadette/.kde/socket-alix/kdeinit4__1
digikam: Fatal IO error: client killed

-- Backtrace (Reduced):
#6  0x00000000007c7fe3 in Digikam::GPCamera::getItemInfoInternal (this=this@entry=0x633a4b0, folder=..., itemName=..., info=..., useMetadata=useMetadata@entry=true) at /usr/src/debug/digikam-3.3.0/core/utilities/importui/backend/gpcamera.cpp:849
#7  0x00000000007c8542 in Digikam::GPCamera::getItemsInfoList (this=0x633a4b0, folder=..., useMetadata=true, items=...) at /usr/src/debug/digikam-3.3.0/core/utilities/importui/backend/gpcamera.cpp:802
#8  0x00000000007b9d9c in Digikam::CameraController::executeCommand (this=this@entry=0x2256200, cmd=cmd@entry=0x4f78920) at /usr/src/debug/digikam-3.3.0/core/utilities/importui/backend/cameracontroller.cpp:505
#9  0x00000000007bc446 in Digikam::CameraController::run (this=0x2256200) at /usr/src/debug/digikam-3.3.0/core/utilities/importui/backend/cameracontroller.cpp:402
#10 0x0000003ad147ad0f in QThreadPrivate::start (arg=0x2256200) at thread/qthread_unix.cpp:338
Comment 14 alainthiaville59 2013-10-02 15:56:09 UTC
Created attachment 82611 [details]
New crash information added by DrKonqi

digikam (3.4.0) on KDE Platform 4.11.1 using Qt 4.8.5

- What I was doing when the application crashed:

my camera is a Canon EOS 7D. Each time i connect my camera digikam crashes.
the command is "digikam --detect-camera" 
the problem IS NOT in (lib)gphoto2 but in digikam because: 
a) i can upload all photos or thumbnails with the command "ghoto2 -T --auto-detect".
b) I can upload photos with shotwell (another app wich uses libgphoto2
c) if i start digikam from an another user account (with no digikam database), all thumbnails are showed and i
can upload the photos

-- Backtrace (Reduced):
#6  0x00000000007c9f13 in Digikam::GPCamera::getItemInfoInternal (this=this@entry=0x50ce790, folder=..., itemName=..., info=..., useMetadata=useMetadata@entry=true) at /usr/src/debug/digikam-3.4.0/core/utilities/importui/backend/gpcamera.cpp:849
#7  0x00000000007ca472 in Digikam::GPCamera::getItemsInfoList (this=0x50ce790, folder=..., useMetadata=true, items=...) at /usr/src/debug/digikam-3.4.0/core/utilities/importui/backend/gpcamera.cpp:802
#8  0x00000000007bbccc in Digikam::CameraController::executeCommand (this=this@entry=0x497c850, cmd=cmd@entry=0x5371170) at /usr/src/debug/digikam-3.4.0/core/utilities/importui/backend/cameracontroller.cpp:505
#9  0x00000000007be376 in Digikam::CameraController::run (this=0x497c850) at /usr/src/debug/digikam-3.4.0/core/utilities/importui/backend/cameracontroller.cpp:402
#10 0x00007fffeda9cd0f in QThreadPrivate::start (arg=0x497c850) at thread/qthread_unix.cpp:338
Comment 15 Simone Sapienza 2013-12-02 11:16:20 UTC
Created attachment 83875 [details]
New crash information added by DrKonqi

digikam (2.5.0) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.1

- What I was doing when the application crashed: Importing images from digital camera via usb

-- Backtrace (Reduced):
#6  0x00000000007582b8 in Digikam::GPCamera::getItemInfoInternal (this=0x57acc80, folder=..., itemName=..., info=..., useMetadata=true) at /build/buildd/digikam-2.5.0/core/utilities/cameragui/devices/gpcamera.cpp:840
#7  0x000000000075f915 in Digikam::GPCamera::getItemsInfoList (this=0x57acc80, folder=..., useMetadata=true, items=...) at /build/buildd/digikam-2.5.0/core/utilities/cameragui/devices/gpcamera.cpp:793
#8  0x0000000000783c00 in Digikam::CameraController::executeCommand (this=0x566a020, cmd=0x4d07340) at /build/buildd/digikam-2.5.0/core/utilities/cameragui/controller/cameracontroller.cpp:489
#9  0x00000000007872a6 in Digikam::CameraController::run (this=0x566a020) at /build/buildd/digikam-2.5.0/core/utilities/cameragui/controller/cameracontroller.cpp:396
#10 0x00007f27bd6fefcb in QThreadPrivate::start (arg=0x566a020) at thread/qthread_unix.cpp:298