Bug 303545 - Digikam crash when importing photos from a camera
Summary: Digikam crash when importing photos from a camera
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Import-Gphoto2 (show other bugs)
Version: 2.8.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-15 10:36 UTC by Ricardo
Modified: 2017-08-16 06:12 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.13.0


Attachments
New crash information added by DrKonqi (7.93 KB, text/plain)
2012-07-18 09:24 UTC, Carl Troein
Details
New crash information added by DrKonqi (6.20 KB, text/plain)
2012-07-30 19:46 UTC, marc
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ricardo 2012-07-15 10:36:01 UTC
Application: digikam (2.8.0)
KDE Platform Version: 4.8.4 (4.8.4) "release 513"
Qt Version: 4.8.2
Operating System: Linux 3.1.10-1.16-desktop x86_64
Distribution: "openSUSE 12.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

I clicked on the "Import with digikam" from the "available devices" plasmoid
The camara was a Canon Ixus 970 IS

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Aborted
[Current thread is 1 (Thread 0x7f34fbdeb7e0 (LWP 12415))]

Thread 6 (Thread 0x7f34dea51700 (LWP 12417)):
#0  0x00007f34f31f3e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f34f6eafb2b in wait (time=18446744073709551615, this=0xcf1b40) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0xcf1a38, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00000000005dfbd0 in Digikam::ScanController::run (this=0xcf17d0) at /usr/src/debug/digikam-software-compilation/core/digikam/database/scancontroller.cpp:698
#4  0x00007f34f6eaf61b in QThreadPrivate::start (arg=0xcf17d0) at thread/qthread_unix.cpp:307
#5  0x00007f34f31eff05 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f34f54a810d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f34de250700 (LWP 12418)):
#0  0x00007f34f549eff3 in poll () from /lib64/libc.so.6
#1  0x00007f34f0425a98 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f34f0425f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f34f6fdce36 in QEventDispatcherGlib::processEvents (this=0x7f34d00008c0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f34f6fac842 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f34f6faca97 in QEventLoop::exec (this=0x7f34de24fd70, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f34f6eac5f7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f34f6f8c62f in QInotifyFileSystemWatcherEngine::run (this=0xcf49a0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f34f6eaf61b in QThreadPrivate::start (arg=0xcf49a0) at thread/qthread_unix.cpp:307
#9  0x00007f34f31eff05 in start_thread () from /lib64/libpthread.so.0
#10 0x00007f34f54a810d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f34dda4f700 (LWP 12420)):
#0  0x00007f34f31f3e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f34f6eafb2b in wait (time=18446744073709551615, this=0xe1ac00) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0xe36238, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00007f34f965cb61 in Digikam::ParkingThread::run (this=0xe36220) at /usr/src/debug/digikam-software-compilation/core/libs/threads/threadmanager.cpp:119
#4  0x00007f34f6eaf61b in QThreadPrivate::start (arg=0xe36220) at thread/qthread_unix.cpp:307
#5  0x00007f34f31eff05 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f34f54a810d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f34c94f9700 (LWP 12424)):
#0  0x00007f34f549eff3 in poll () from /lib64/libc.so.6
#1  0x00007f34f0425a98 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f34f0425f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f34f6fdce36 in QEventDispatcherGlib::processEvents (this=0x7f34c4002670, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f34f6fac842 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f34f6faca97 in QEventLoop::exec (this=0x7f34c94f8d70, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f34f6eac5f7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f34f6f8c62f in QInotifyFileSystemWatcherEngine::run (this=0x33229d0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f34f6eaf61b in QThreadPrivate::start (arg=0x33229d0) at thread/qthread_unix.cpp:307
#9  0x00007f34f31eff05 in start_thread () from /lib64/libpthread.so.0
#10 0x00007f34f54a810d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f34ca989700 (LWP 12425)):
#0  0x00007f34f549eff3 in poll () from /lib64/libc.so.6
#1  0x00007f34f0425a98 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f34f0425f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f34f6fdce36 in QEventDispatcherGlib::processEvents (this=0x7f34bc0008c0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f34f6fac842 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f34f6faca97 in QEventLoop::exec (this=0x7f34ca988d70, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f34f6eac5f7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f34f6f8c62f in QInotifyFileSystemWatcherEngine::run (this=0x3350880) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f34f6eaf61b in QThreadPrivate::start (arg=0x3350880) at thread/qthread_unix.cpp:307
#9  0x00007f34f31eff05 in start_thread () from /lib64/libpthread.so.0
#10 0x00007f34f54a810d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f34fbdeb7e0 (LWP 12415)):
[KCrash Handler]
#6  0x00007f34f5401d95 in raise () from /lib64/libc.so.6
#7  0x00007f34f54032ab in abort () from /lib64/libc.so.6
#8  0x00007f34f53fa8fe in __assert_fail_base () from /lib64/libc.so.6
#9  0x00007f34f53fa9a2 in __assert_fail () from /lib64/libc.so.6
#10 0x00007f34f31ed9b3 in __pthread_mutex_lock_full () from /lib64/libpthread.so.0
#11 0x00007f34e40d5ccb in libusb_unref_device (dev=0x40e94a0) at core.c:820
#12 0x00007f34e40d5de5 in libusb_free_device_list (list=0x36495a0, unref_devices=<optimized out>) at core.c:649
#13 0x00007f3489befb45 in gp_port_usb_exit (port=0x31040b0) at libusb1.c:275
#14 0x00007f34f8cd8616 in gp_port_exit (port=0x31040b0) at gphoto2-port.c:124
#15 0x00007f34f8cd8791 in gp_port_free (port=0x31040b0) at gphoto2-port.c:319
#16 0x000000000077a223 in Digikam::GPCamera::findConnectedUsbCamera (vendorId=1193, productId=12659, model=..., port=...) at /usr/src/debug/digikam-software-compilation/core/utilities/cameragui/devices/gpcamera.cpp:1844
#17 0x0000000000591080 in Digikam::DigikamApp::openSolidCamera (this=0xd8cd80, udi=..., cameraLabel=...) at /usr/src/debug/digikam-software-compilation/core/digikam/main/digikamapp.cpp:1824
#18 0x00000000005926cb in Digikam::DigikamApp::slotOpenSolidDevice (this=0xd8cd80, udi=...) at /usr/src/debug/digikam-software-compilation/core/digikam/main/digikamapp.cpp:1764
#19 0x0000000000595e71 in Digikam::DigikamApp::qt_static_metacall (_o=0xd8cd80, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/digikam-software-compilation/build/core/digikam/digikamapp.moc:189
#20 0x00007f34f6fc6e06 in QObject::event (this=0xd8cd80, e=<optimized out>) at kernel/qobject.cpp:1204
#21 0x00007f34f610207b in QWidget::event (this=0xd8cd80, event=0x46d32f0) at kernel/qwidget.cpp:8830
#22 0x00007f34f64d7c3b in QMainWindow::event (this=0xd8cd80, event=0x46d32f0) at widgets/qmainwindow.cpp:1478
#23 0x00007f34f7b2f4a8 in KXmlGuiWindow::event (this=0xd8cd80, ev=0x46d32f0) at /usr/src/debug/kdelibs-4.8.4/kdeui/xmlgui/kxmlguiwindow.cpp:126
#24 0x00007f34f60b1fe4 in notify_helper (e=0x46d32f0, receiver=0xd8cd80, this=0xba9670) at kernel/qapplication.cpp:4551
#25 QApplicationPrivate::notify_helper (this=0xba9670, receiver=0xd8cd80, e=0x46d32f0) at kernel/qapplication.cpp:4523
#26 0x00007f34f60b6db3 in QApplication::notify (this=0x7fff9b1f83e0, receiver=0xd8cd80, e=0x46d32f0) at kernel/qapplication.cpp:4412
#27 0x00007f34f7a33746 in KApplication::notify (this=0x7fff9b1f83e0, receiver=0xd8cd80, event=0x46d32f0) at /usr/src/debug/kdelibs-4.8.4/kdeui/kernel/kapplication.cpp:311
#28 0x00007f34f6fadd0c in QCoreApplication::notifyInternal (this=0x7fff9b1f83e0, receiver=0xd8cd80, event=0x46d32f0) at kernel/qcoreapplication.cpp:915
#29 0x00007f34f6fb15ba in sendEvent (event=0x46d32f0, receiver=0xd8cd80) at kernel/qcoreapplication.h:231
#30 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xb48f60) at kernel/qcoreapplication.cpp:1539
#31 0x00007f34f6fdc9a3 in sendPostedEvents () at kernel/qcoreapplication.h:236
#32 postEventSourceDispatch (s=0xbabcf0) at kernel/qeventdispatcher_glib.cpp:279
#33 0x00007f34f042558d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#34 0x00007f34f0425d88 in ?? () from /usr/lib64/libglib-2.0.so.0
#35 0x00007f34f0425f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#36 0x00007f34f6fdcdcf in QEventDispatcherGlib::processEvents (this=0xb48860, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#37 0x00007f34f615569e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#38 0x00007f34f6fac842 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#39 0x00007f34f6faca97 in QEventLoop::exec (this=0x7fff9b1f8260, flags=...) at kernel/qeventloop.cpp:204
#40 0x00007f34f6fb18b5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#41 0x00000000004977fb in main (argc=3, argv=<optimized out>) at /usr/src/debug/digikam-software-compilation/core/digikam/main/main.cpp:232

Reported using DrKonqi
Comment 1 Carl Troein 2012-07-18 09:24:46 UTC
Created attachment 72605 [details]
New crash information added by DrKonqi

digikam (2.6.0) on KDE Platform 4.8.4 (4.8.4) "release 2" using Qt 4.8.1

- What I was doing when the application crashed:

Started digikam and attempted to import photos from IXUS 230HS camera. Alternatively accepted to import with digikam from the menu that pops up when the camera is attached. In either case digikam immediately crashed, rendering the program utterly useless for its purpose.

-- Backtrace (Reduced):
#10 0x00007fe966fc5cc5 in gp_port_usb_exit (port=0x2aad2b0) at libusb1.c:275
#11 0x00007fe9b85a4756 in gp_port_exit (port=0x2aad2b0) at gphoto2-port.c:124
#12 0x00007fe9b85a48d1 in gp_port_free (port=0x2aad2b0) at gphoto2-port.c:319
#13 0x000000000075a250 in Digikam::GPCamera::findConnectedUsbCamera (vendorId=1193, productId=12855, model=..., port=...) at /usr/src/debug/digikam-2.6.0/core/utilities/cameragui/devices/gpcamera.cpp:1844
#14 0x0000000000586260 in Digikam::DigikamApp::openSolidCamera (this=this@entry=0x1180dd0, udi=..., cameraLabel=...) at /usr/src/debug/digikam-2.6.0/core/digikam/main/digikamapp.cpp:1824
Comment 2 caulier.gilles 2012-07-22 15:07:35 UTC
It crash in Gphoto Driver ? Which libgphoto version you use ? Go to Help/Components Info dialog for details...

Gilles Caulier
Comment 3 Ricardo 2012-07-23 22:22:11 UTC
digiKam version 2.8.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.8.4 (4.8.4) "release 513"
LibKExiv2: 2.1.0
LibKGeoMap: 2.0.0
LibKdcraw: 2.0.1
LibLCMS: 119
LibLensFun: 0.2.6-0 - internal library
LibLqr: internal library
LibPGF: 6.12.27 - internal library
LibPNG: 1.4.8
LibQt: 4.8.2
LibRaw: 0.14.4
LibTIFF: LIBTIFF, Version 3.9.5 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc.
Marble Widget: 0.13.4 (stable release)
Parallelized PGF codec: No
Parallelized demosaicing: Yes
Database backend: QSQLITE
LibGphoto2: 2.4.14
LibKface: 2.0.0
LibKipi: 1.3.0
LibOpenCV: 2.4.0
Libface: 0.2
Comment 4 caulier.gilles 2012-07-24 07:27:01 UTC
It sound like a binary  incompatibility broken between libusb and libgphoto2. Please check your packages...

Gilles Caulier
Comment 5 Ricardo 2012-07-24 09:08:27 UTC
Ok, thx. I can live with it until the next opensuse release..
Comment 6 marc 2012-07-30 19:46:27 UTC
Created attachment 72834 [details]
New crash information added by DrKonqi

digikam (2.6.0) on KDE Platform 4.8.4 (4.8.4) "release 2" using Qt 4.8.1

- What I was doing when the application crashed:

I was trying to upload photos from my nikon D90 camera via PTP. Digikam always crashes.

I work on opensuse 12.2 RC1.

-- Backtrace (Reduced):
#7  0x00007f31e059c213 in libusb_unref_device (dev=0xf0) at core.c:859
#8  0x00007f31e059c2b5 in libusb_free_device_list (list=0x550bb30, unref_devices=<optimized out>) at core.c:676
#9  0x00007f31b0b2bcc5 in gp_port_usb_exit (port=0x5509a50) at libusb1.c:278
#10 0x00007f31f55d6756 in gp_port_exit (port=0x5509a50) at gphoto2-port.c:124
#11 0x00007f31f55d68d1 in gp_port_free (port=0x5509a50) at gphoto2-port.c:319
Comment 7 caulier.gilles 2012-07-30 19:56:09 UTC
It crash in libusb, used by libgphoto2. It's not a crash from digiKam. Sound like a packaging problem between libusb and libgphoto2...

Gilles Caulier
Comment 8 marc 2012-07-31 09:54:15 UTC
Thanks, I'll transmit to the opensuse bugzilla.
https://bugzilla.novell.com/show_bug.cgi?id=771743
Marc
Comment 9 caulier.gilles 2015-06-27 13:42:41 UTC
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles caulier
Comment 10 caulier.gilles 2015-08-21 07:04:31 UTC
digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.
Comment 11 marc 2015-08-21 08:27:52 UTC
(In reply to Gilles Caulier from comment #10)
> digiKam 4.12.0 is out :
> 
> https://www.digikam.org/node/741
> 
> We need a fresh feedback using this release please...
> Thanks in advance.

Hi Gilles,

I made a fresh install of Digikam 4.12.0 on OpenSuse 13.2 x64 repos (built by simotek), which only requiered two or three update of packages for dependencies, but no problem in the end.

I could launch Digikam (pretty fast to launch) and I'm currently uploading photos from my camera (Nikon D90). No crash !

Thanks for this very good software !
Marc