Bug 283355

Summary: DigiKam crashed while tagging an image with shortcut keys
Product: [Applications] digikam Reporter: somemail
Component: Usability-KeyboardAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: caulier.gilles
Priority: NOR    
Version: 2.1.1   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 5.1.0
Sentry Crash Report:

Description somemail 2011-10-04 22:08:38 UTC 
Application: digikam (2.1.1)
KDE Platform Version: 4.7.1 (4.7.1)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-11-generic i686
Distribution: Ubuntu 11.04

-- Information about the crash:
- What I was doing when the application crashed:
Tagging an image, using shortcut keys.  Specifically the MOD key (windows key) and Alt key + a letter (don't remember which letter, maybe 'i').  This has happened a few times to me, always the instant I press the last key in the shortcut combination.  When I reload the application, I can tag the image without any issues.

- Custom settings of the application:
Running a precompiled version of DigiKam under Ubuntu and GTK (I think - I'm definitely not running KDE).

The crash can be reproduced some of the time.

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

Thread 17 (Thread 0xb56f1b70 (LWP 3187)):
#0  0x0074e416 in __kernel_vsyscall ()
#1  0x0667ef76 in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0x0306484b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x030541af in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x0305492b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x042cf304 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6  0x0307d2df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0x008abe99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0x0668d73e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 16 (Thread 0xb3af4b70 (LWP 3189)):
#0  0x0074e416 in __kernel_vsyscall ()
#1  0x008b048c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0x0669b3fd in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0x039e4467 in wait (this=0x91f2924, mutex=0x91f2920, time=4294967295) at thread/qwaitcondition_unix.cpp:88
#4  QWaitCondition::wait (this=0x91f2924, mutex=0x91f2920, time=4294967295) at thread/qwaitcondition_unix.cpp:160
#5  0x081e92e9 in Digikam::ScanController::run (this=0x91f26e8) at /build/buildd/digikam2-2.1.1/core/digikam/database/scancontroller.cpp:647
#6  0x039e3da2 in QThreadPrivate::start (arg=0x91f26e8) at thread/qthread_unix.cpp:320
#7  0x008abe99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0x0668d73e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 15 (Thread 0xb32f3b70 (LWP 3190)):
#0  0x0074e416 in __kernel_vsyscall ()
#1  0x0669b753 in ?? () from /lib/i386-linux-gnu/libc.so.6
#2  0x0662eb94 in ?? () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 14 (Thread 0xb2af2b70 (LWP 3192)):
#0  0x0074e416 in __kernel_vsyscall ()
#1  0x008b048c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0
#2  0x0669b3fd in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0x039e4467 in wait (this=0x935dc68, mutex=0x935dc64, time=4294967295) at thread/qwaitcondition_unix.cpp:88
#4  QWaitCondition::wait (this=0x935dc68, mutex=0x935dc64, time=4294967295) at thread/qwaitcondition_unix.cpp:160
#5  0x02c7183a in Digikam::ParkingThread::run (this=0x935dc58) at /build/buildd/digikam2-2.1.1/core/libs/threads/threadmanager.cpp:119
#6  0x039e3da2 in QThreadPrivate::start (arg=0x935dc58) at thread/qthread_unix.cpp:320
#7  0x008abe99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0x0668d73e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 13 (Thread 0xab5beb70 (LWP 3217)):
#0  0x0074e416 in __kernel_vsyscall ()
#1  0x0669b753 in ?? () from /lib/i386-linux-gnu/libc.so.6
#2  0x0662eb94 in ?? () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 12 (Thread 0xad24cb70 (LWP 3218)):
#0  0x0074e416 in __kernel_vsyscall ()
#1  0x0669b753 in ?? () from /lib/i386-linux-gnu/libc.so.6
#2  0x066484f6 in ?? () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 11 (Thread 0xabe1fb70 (LWP 3219)):
#0  0x0074e416 in __kernel_vsyscall ()
#1  0x0669b753 in ?? () from /lib/i386-linux-gnu/libc.so.6
#2  0x0662eb94 in ?? () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 10 (Thread 0xac620b70 (LWP 3220)):
#0  0x0074e416 in __kernel_vsyscall ()
#1  0x0669b753 in ?? () from /lib/i386-linux-gnu/libc.so.6
#2  0x0662eb94 in ?? () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 9 (Thread 0xa903bb70 (LWP 3221)):
#0  0x0074e416 in __kernel_vsyscall ()
#1  0x0669b753 in ?? () from /lib/i386-linux-gnu/libc.so.6
#2  0x0662eb94 in ?? () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 8 (Thread 0xa810cb70 (LWP 3222)):
#0  0x00a838de in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#1  0x00a83991 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#2  0x00a82225 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#3  0x008abe99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#4  0x0668d73e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 7 (Thread 0xa790bb70 (LWP 3223)):
#0  0x00a838de in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#1  0x00a83991 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#2  0x00a82225 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#3  0x008abe99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#4  0x0668d73e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 6 (Thread 0xa6a92b70 (LWP 3224)):
#0  0x00a838de in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#1  0x00a83991 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#2  0x00a82225 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#3  0x008abe99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#4  0x0668d73e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 5 (Thread 0xa6291b70 (LWP 3225)):
#0  0x00a838de in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#1  0x00a83991 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#2  0x00a82225 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#3  0x008abe99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#4  0x0668d73e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 4 (Thread 0xa5a90b70 (LWP 3226)):
#0  0x00a838de in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#1  0x00a83991 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#2  0x00a82225 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#3  0x008abe99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#4  0x0668d73e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 3 (Thread 0xa3016b70 (LWP 3227)):
#0  0x0074e416 in __kernel_vsyscall ()
#1  0x0669b753 in ?? () from /lib/i386-linux-gnu/libc.so.6
#2  0x0662eb94 in ?? () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0xa2815b70 (LWP 3228)):
#0  0x00a838de in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#1  0x00a83991 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#2  0x00a82225 in ?? () from /usr/lib/i386-linux-gnu/libgomp.so.1
#3  0x008abe99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#4  0x0668d73e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb595b8c0 (LWP 3185)):
[KCrash Handler]
#7  0x0074e416 in __kernel_vsyscall ()
#8  0x065e7e71 in raise () from /lib/i386-linux-gnu/libc.so.6
#9  0x065eb34e in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0x0661e577 in ?? () from /lib/i386-linux-gnu/libc.so.6
#11 0x06628961 in ?? () from /lib/i386-linux-gnu/libc.so.6
#12 0x0662b4ba in ?? () from /lib/i386-linux-gnu/libc.so.6
#13 0x0662cf53 in malloc () from /lib/i386-linux-gnu/libc.so.6
#14 0x025c6679 in operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#15 0x01cf30ea in QBrush::detach (this=0xaa5d048, newStyle=Qt::SolidPattern) at painting/qbrush.cpp:610
#16 0x01cf40bc in QBrush::setStyle (this=0xaa5d048, style=Qt::SolidPattern) at painting/qbrush.cpp:666
#17 0x01d29a16 in QPainter::fillRect (this=0xbfede858, r=..., brush=...) at painting/qpainter.cpp:6981
#18 0x01c1710e in fillRegion (this=0x9645cf8, painter=0xbfede858, rgn=..., flags=0) at kernel/qwidget.cpp:2337
#19 QWidgetPrivate::paintBackground (this=0x9645cf8, painter=0xbfede858, rgn=..., flags=0) at kernel/qwidget.cpp:2372
#20 0x01c1d39f in QWidgetPrivate::drawWidget (this=0x9645cf8, pdev=0x9347a0c, rgn=..., offset=..., flags=68, sharedPainter=0x0, backingStore=0x9232290) at kernel/qwidget.cpp:5470
#21 0x01dfb329 in QWidgetBackingStore::sync (this=0x9232290) at painting/qbackingstore.cpp:1325
#22 0x01c12843 in QWidgetPrivate::syncBackingStore (this=0x9229e00) at kernel/qwidget.cpp:1842
#23 0x01c207e5 in QWidget::event (this=0x92579d0, event=0xa021cf8) at kernel/qwidget.cpp:8552
#24 0x02031527 in QMainWindow::event (this=0x92579d0, event=0xa021cf8) at widgets/qmainwindow.cpp:1480
#25 0x01997aec in KMainWindow::event (this=0x92579d0, ev=0xa021cf8) at ../../kdeui/widgets/kmainwindow.cpp:1100
#26 0x019ddebf in KXmlGuiWindow::event (this=0x92579d0, ev=0xa021cf8) at ../../kdeui/xmlgui/kxmlguiwindow.cpp:126
#27 0x01bc7d24 in QApplicationPrivate::notify_helper (this=0x904f3a0, receiver=0x92579d0, e=0xa021cf8) at kernel/qapplication.cpp:4462
#28 0x01bcc97b in QApplication::notify (this=0xbfedf54c, receiver=0x92579d0, e=0xa021cf8) at kernel/qapplication.cpp:4427
#29 0x018c2c9a in KApplication::notify (this=0xbfedf54c, receiver=0x92579d0, event=0xa021cf8) at ../../kdeui/kernel/kapplication.cpp:311
#30 0x03ad80bb in QCoreApplication::notifyInternal (this=0xbfedf54c, receiver=0x92579d0, event=0xa021cf8) at kernel/qcoreapplication.cpp:731
#31 0x03adbc79 in sendEvent (receiver=0x0, event_type=0, data=0x8ff3f88) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#32 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8ff3f88) at kernel/qcoreapplication.cpp:1372
#33 0x03adbe0d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1265
#34 0x03b053c4 in sendPostedEvents (s=0x90520d0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#35 postEventSourceDispatch (s=0x90520d0) at kernel/qeventdispatcher_glib.cpp:277
#36 0x03053aa8 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#37 0x03054270 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#38 0x03054524 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#39 0x03b0553c in QEventDispatcherGlib::processEvents (this=0x8ff3ae0, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#40 0x01c7e1e5 in QGuiEventDispatcherGlib::processEvents (this=0x8ff3ae0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#41 0x03ad7289 in QEventLoop::processEvents (this=0xbfedf414, flags=...) at kernel/qeventloop.cpp:149
#42 0x03ad7522 in QEventLoop::exec (this=0xbfedf414, flags=...) at kernel/qeventloop.cpp:201
#43 0x03adbecc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#44 0x01bc58e7 in QApplication::exec () at kernel/qapplication.cpp:3736
#45 0x082bbc93 in main (argc=) at /build/buildd/digikam2-2.1.1/core/digikam/main/main.cpp:232

Reported using DrKonqi
Comment 1 caulier.gilles 2011-10-05 04:10:43 UTC 
In the trace, there is nothing from digiKam, only Qt. Sound like a broken depency on your computer. Please run digiKam through GDB and try to get a better backtrace. 

Look here for details : http://www.digikam.org/drupal/contrib

Gilles Caulier
Comment 2 caulier.gilles 2011-11-03 12:42:37 UTC 
digiKam 2.2.0 is out since few weeks. Crash still valid with this version ?

Gilles Caulier
Comment 3 caulier.gilles 2015-06-27 13:47:26 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 4 caulier.gilles 2015-08-22 06:40:45 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 5 caulier.gilles 2016-07-09 16:05:03 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