Bug 305054

Summary: Crash DigiKam when selecting newly imported albums
Product: [Applications] digikam Reporter: Markus Brosche <m.bro>
Component: Import-AlbumsAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: caulier.gilles, sven.langkamp
Priority: NOR    
Version: 2.5.0   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In: 5.1.0
Sentry Crash Report:

Description Markus Brosche 2012-08-12 23:17:58 UTC 
Application: digikam (2.5.0)
KDE Platform Version: 4.8.4 (4.8.4) (Compiled from sources)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-29-generic x86_64
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
Nach Auswahl des neu importierten Albums (von SD-Karte) stürzt DigiKam immer ab.

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0d3c3dda00 (LWP 7811))]

Thread 6 (Thread 0x7f0d18a79700 (LWP 7814)):
#0  0x00007f0d358570bd in read () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007f0d2ee018cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f0d2edc6ba4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f0d2edc6fd6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f0d2edc749a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f0d18a7e98b in ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
#6  0x00007f0d2ede89e5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007f0d31179e9a in start_thread (arg=0x7f0d18a79700) at pthread_create.c:308
#8  0x00007f0d358644bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#9  0x0000000000000000 in ?? ()

Thread 5 (Thread 0x7f0d13fff700 (LWP 7815)):
#0  0x00007f0d2ee025d1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f0d2edc61f8 in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f0d2edc6f04 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f0d2edc749a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f0d24b9f406 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x00007f0d2ede89e5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f0d31179e9a in start_thread (arg=0x7f0d13fff700) at pthread_create.c:308
#7  0x00007f0d358644bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#8  0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f0d0b7e8700 (LWP 7819)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f0d366384db in wait (time=18446744073709551615, this=0xfb0130) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0xfb0028, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00000000005ca1d0 in Digikam::ScanController::run (this=0xfafdc0) at /build/buildd/digikam-2.5.0/core/digikam/database/scancontroller.cpp:647
#4  0x00007f0d36637fcb in QThreadPrivate::start (arg=0xfafdc0) at thread/qthread_unix.cpp:298
#5  0x00007f0d31179e9a in start_thread (arg=0x7f0d0b7e8700) at pthread_create.c:308
#6  0x00007f0d358644bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f0d0afe7700 (LWP 7820)):
#0  0x00007f0d35858b03 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f0d2edc7036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f0d2edc7164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f0d36766426 in QEventDispatcherGlib::processEvents (this=0x7f0cf80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f0d36735c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f0d36735ed7 in QEventLoop::exec (this=0x7f0d0afe6b50, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f0d36634fa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f0d367159ff in QInotifyFileSystemWatcherEngine::run (this=0xfb25b0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f0d36637fcb in QThreadPrivate::start (arg=0xfb25b0) at thread/qthread_unix.cpp:298
#9  0x00007f0d31179e9a in start_thread (arg=0x7f0d0afe7700) at pthread_create.c:308
#10 0x00007f0d358644bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f0d0a7e6700 (LWP 7822)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f0d366384db in wait (time=18446744073709551615, this=0x1297580) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x12972e8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00007f0d39a3fff1 in Digikam::ParkingThread::run (this=0x12972d0) at /build/buildd/digikam-2.5.0/core/libs/threads/threadmanager.cpp:119
#4  0x00007f0d36637fcb in QThreadPrivate::start (arg=0x12972d0) at thread/qthread_unix.cpp:298
#5  0x00007f0d31179e9a in start_thread (arg=0x7f0d0a7e6700) at pthread_create.c:308
#6  0x00007f0d358644bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f0d3c3dda00 (LWP 7811)):
[KCrash Handler]
#6  0x00007f0d0996b32d in QAccessibleTable2Cell::state (this=0x1400190, child=<optimized out>) at itemviews.cpp:733
#7  0x00007f0d09bbd971 in AtSpiAdaptor::accessibleInterface(QAccessibleInterface*, int, QString const&, QDBusMessage const&, QDBusConnection const&) () from /usr/lib/x86_64-linux-gnu/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#8  0x00007f0d09bbf62b in AtSpiAdaptor::handleMessage(QDBusMessage const&, QDBusConnection const&) () from /usr/lib/x86_64-linux-gnu/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so
#9  0x00007f0d36363985 in QDBusConnectionPrivate::activateObject (this=0xfde600, node=..., msg=..., pathStartPos=27) at qdbusintegrator.cpp:1384
#10 0x00007f0d36363f2b in QDBusActivateObjectEvent::placeMetaCall (this=0x2424cb0) at qdbusintegrator.cpp:1537
#11 0x00007f0d36750446 in QObject::event (this=0xfc5bb0, e=<optimized out>) at kernel/qobject.cpp:1195
#12 0x00007f0d37131894 in notify_helper (e=0x2424cb0, receiver=0xfc5bb0, this=0xcb2020) at kernel/qapplication.cpp:4559
#13 QApplicationPrivate::notify_helper (this=0xcb2020, receiver=0xfc5bb0, e=0x2424cb0) at kernel/qapplication.cpp:4531
#14 0x00007f0d37136713 in QApplication::notify (this=0x7fff7eb5b0b0, receiver=0xfc5bb0, e=0x2424cb0) at kernel/qapplication.cpp:4420
#15 0x00007f0d37e6b9e6 in KApplication::notify (this=0x7fff7eb5b0b0, receiver=0xfc5bb0, event=0x2424cb0) at ../../kdeui/kernel/kapplication.cpp:311
#16 0x00007f0d36736e9c in QCoreApplication::notifyInternal (this=0x7fff7eb5b0b0, receiver=0xfc5bb0, event=0x2424cb0) at kernel/qcoreapplication.cpp:876
#17 0x00007f0d3673ac6a in sendEvent (event=0x2424cb0, receiver=0xfc5bb0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#18 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0xc4e2a0) at kernel/qcoreapplication.cpp:1500
#19 0x00007f0d36765f93 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#20 postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:279
#21 0x00007f0d2edc6d53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f0d2edc70a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f0d2edc7164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f0d367663bf in QEventDispatcherGlib::processEvents (this=0xc4fb80, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#25 0x00007f0d371d9d5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#26 0x00007f0d36735c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#27 0x00007f0d36735ed7 in QEventLoop::exec (this=0x7fff7eb5af30, flags=...) at kernel/qeventloop.cpp:204
#28 0x00007f0d3673af67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#29 0x000000000048bc5d in main (argc=5, argv=<optimized out>) at /build/buildd/digikam-2.5.0/core/digikam/main/main.cpp:232

Reported using DrKonqi
Comment 1 caulier.gilles 2012-08-13 07:36:22 UTC 
It crash in DBUs API, not digiKam.

Please check your system, and try to use a most recent digiKam release (2.8.0 is just arrived)

Also, please use English words here. We don't understand German...

Thanks in advance

Gilles Caulier
Comment 2 Markus Brosche 2012-08-13 12:35:05 UTC 
Hello,
thanks for the fast reaktion.

I m not very good in Ubuntu-System-Check. I only klick on the updates ;)

I m going on trying.....

Ubuntu is great Linux!!!

Bye
Markus

Am 13.08.2012 09:36, schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=305054
>
> Gilles Caulier <caulier.gilles@gmail.com> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>               Status|UNCONFIRMED                 |RESOLVED
>                   CC|                            |caulier.gilles@gmail.com
>           Resolution|---                         |WAITINGFORINFO
>
> --- Comment #1 from Gilles Caulier <caulier.gilles@gmail.com> ---
> It crash in DBUs API, not digiKam.
>
> Please check your system, and try to use a most recent digiKam release (2.8.0
> is just arrived)
>
> Also, please use English words here. We don't understand German...
>
> Thanks in advance
>
> Gilles Caulier
>
Comment 3 Sven Langkamp 2013-02-16 19:53:29 UTC 
You can work around this bug by uninstalling qt-at-spi. I have reported it to launchpad here: https://bugs.launchpad.net/ubuntu/+source/qt-at-spi/+bug/1127461
Comment 4 caulier.gilles 2015-06-27 13:47:43 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 5 caulier.gilles 2015-08-22 06:39:10 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 6 caulier.gilles 2016-07-09 14:19:20 UTC 
This problem is not reproducible with last 5.0.0.
I close this file now. Don't hesitate to re-open it if necessary.
Gilles Caulier