Bug 223348 - Digikam crash during album view browsing AVIs with PgUp/PgDown
Summary: Digikam crash during album view browsing AVIs with PgUp/PgDown
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Preview-Video (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-18 23:52 UTC by René Krell
Modified: 2018-08-25 20:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.0.0

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description René Krell 2010-01-18 23:52:20 UTC 
Version:           1.0.0 (using 4.3.90 (KDE 4.3.90 (KDE 4.4 RC1)) "release 212", KDE:KDE4:Factory:Desktop / openSUSE_11.2)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.31.8-0.1-desktop

I have a mixed albums with JPEGs and AVIs, ending with AVIs. Navigating at the end back and forward lets Digikam crash withou a backtrace. The console output ends with this (repeated more times during changing between AVIs):

digikam(7884)/KEXIV2 KExiv2Iface::KExiv2Priv::printExiv2ExceptionError: Cannot load metadata using Exiv2   (Error # 11 :  /home/album/Fotky/BÄýšov/P1160382.AVI: The file contains data of an unknown image type
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
minscanline 1
Not a JPEG file: starts with 0xff 0xc4
Fatal Error: Accessed global static 'QStringList *kaccmp_sns()' after destruction. Defined at /usr/src/packages/BUILD/kdelibs-4.3.90/kdeui/shortcuts/kacceleratormanager.cpp:141
KCrash: Application 'digikam' crashing...
sock_file=/home/rkrell/.kde4/socket-linux/kdeinit4__0
Unable to start Dr. Konqi
Comment 1 caulier.gilles 2010-01-19 08:50:00 UTC 
We need a gdb backtrace to investiguate...

Gilles Caulier
Comment 2 René Krell 2010-01-19 22:40:07 UTC 
Here is one, there are still missing some debug symbols, but hopefully it helps:

...
minscanline 1                                                                                                  
minscanline 1                                                                                                  
minscanline 1                                                                                                  
minscanline 1                                                                                                  
[Thread 0x7fffcece8910 (LWP 10232) exited]                                                                     
Not a JPEG file: starts with 0xff 0xc4                                                                         
Fatal Error: Accessed global static 'QStringList *kaccmp_sns()' after destruction. Defined at /usr/src/packages/BUILD/kdelibs-4.3.90/kdeui/shortcuts/kacceleratormanager.cpp:141                                              

Program received signal SIGABRT, Aborted.
0x00007ffff19724e5 in raise () from /lib64/libc.so.6
(gdb) backtrace                                     
#0  0x00007ffff19724e5 in raise () from /lib64/libc.so.6
#1  0x00007ffff19739b0 in abort () from /lib64/libc.so.6
#2  0x00007ffff2486514 in qt_message_output (msgType=QtFatalMsg, buf=<value optimized out>)
    at global/qglobal.cpp:2250
#3  0x00007ffff24866f2 in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=
    QtFatalMsg, msg=
    0x7ffff41dd9e8 "Fatal Error: Accessed global static '%s *%s()' after destruction. Defined at %s:%d", ap=
    0x7fffffffba80) at global/qglobal.cpp:2296
#4  0x00007ffff24868a5 in qFatal (msg=0x277b <Address 0x277b out of bounds>) at global/qglobal.cpp:2479
#5  0x00007ffff4035ff5 in ?? () from /usr/lib64/libkdeui.so.5
#6  0x00007ffff403614c in ?? () from /usr/lib64/libkdeui.so.5
#7  0x00007ffff4042103 in ?? () from /usr/lib64/libkdeui.so.5
#8  0x00007ffff40e01d9 in ?? () from /usr/lib64/libkdeui.so.5
#9  0x00007ffff40e03f9 in ?? () from /usr/lib64/libkdeui.so.5
#10 0x00007ffff40e0aa6 in ?? () from /usr/lib64/libkdeui.so.5
#11 0x00007ffff40e0628 in ?? () from /usr/lib64/libkdeui.so.5
#12 0x00007ffff40e14ba in ?? () from /usr/lib64/libkdeui.so.5
#13 0x00007ffff40e15cb in KAcceleratorManager::manage(QWidget*, bool) () from /usr/lib64/libkdeui.so.5
#14 0x00007ffff40e4156 in ?? () from /usr/lib64/libkdeui.so.5
#15 0x00007ffff40e45ae in ?? () from /usr/lib64/libkdeui.so.5
#16 0x00007ffff40e4628 in ?? () from /usr/lib64/libkdeui.so.5
#17 0x00007ffff259543f in QMetaObject::activate (sender=0xc3c770, m=<value optimized out>,
    local_signal_index=<value optimized out>, argv=0xffffffffffffffff) at kernel/qobject.cpp:3267
#18 0x00007ffff2592093 in QObject::event (this=0xc3c770, e=0x7fffffffcac0) at kernel/qobject.cpp:1204
#19 0x00007ffff315286c in QApplicationPrivate::notify_helper (this=0xad04d0, receiver=0xc3c770, e=
    0x7fffffffcac0) at kernel/qapplication.cpp:4298
#20 0x00007ffff3158e4b in QApplication::notify (this=0x7fffffffcee0, receiver=0xc3c770, e=0x7fffffffcac0)
    at kernel/qapplication.cpp:4181
#21 0x00007ffff4007806 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#22 0x00007ffff258265c in QCoreApplication::notifyInternal (this=0x7fffffffcee0, receiver=0xc3c770, event=
    0x7fffffffcac0) at kernel/qcoreapplication.cpp:704
#23 0x00007ffff25af305 in sendEvent (event=<value optimized out>, receiver=<value optimized out>)
    at kernel/qcoreapplication.h:215
#24 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>)
    at kernel/qeventdispatcher_unix.cpp:617
#25 0x00007ffff25abe98 in timerSourceDispatch (source=<value optimized out>)
    at kernel/qeventdispatcher_glib.cpp:184
#26 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#27 0x00007fffebe26dde in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#28 0x00007fffebe2a7a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#29 0x00007fffebe2a8d0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#30 0x00007ffff25abb63 in QEventDispatcherGlib::processEvents (this=0xa95e60, flags=<value optimized out>)
    at kernel/qeventdispatcher_glib.cpp:412
#31 0x00007ffff320086e in QGuiEventDispatcherGlib::processEvents (this=0x277b, flags=<value optimized out>)
    at kernel/qguieventdispatcher_glib.cpp:204
#32 0x00007ffff2580f72 in QEventLoop::processEvents (this=<value optimized out>, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
)
    at kernel/qeventloop.cpp:149
#33 0x00007ffff258134c in QEventLoop::exec (this=0x7fffffffce10, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
) at kernel/qeventloop.cpp:201
#34 0x00007ffff258509b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#35 0x000000000076576b in main (argc=<value optimized out>, argv=<value optimized out>)
    at /usr/src/debug/digikam-1.0.0/digikam/main.cpp:195
Comment 3 René Krell 2010-01-19 22:48:11 UTC 
Well, with the libkde4 debug symbols installed it looks better:

#0  0x00007ffff19724e5 in raise () from /lib64/libc.so.6
#1  0x00007ffff19739b0 in abort () from /lib64/libc.so.6
#2  0x00007ffff2486514 in qt_message_output (msgType=QtFatalMsg, buf=<value optimized out>)
    at global/qglobal.cpp:2250
#3  0x00007ffff24866f2 in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=
    QtFatalMsg, msg=
    0x7ffff41dd9e8 "Fatal Error: Accessed global static '%s *%s()' after destruction. Defined at %s:%d", ap=
    0x7fffffffba80) at global/qglobal.cpp:2296
#4  0x00007ffff24868a5 in qFatal (msg=0x2b4a <Address 0x2b4a out of bounds>) at global/qglobal.cpp:2479
#5  0x00007ffff4035ff5 in operator-> (this=<value optimized out>)
    at /usr/src/debug/kdelibs-4.3.90/kdeui/shortcuts/kacceleratormanager.cpp:141
#6  KAcceleratorManagerPrivate::standardName (this=<value optimized out>)
    at /usr/src/debug/kdelibs-4.3.90/kdeui/shortcuts/kacceleratormanager.cpp:146
#7  0x00007ffff403614c in KAccelString::calculateWeights (this=0x7fffffffbd80,
    initialWeight=<value optimized out>)
    at /usr/src/debug/kdelibs-4.3.90/kdeui/shortcuts/kacceleratormanager.cpp:620
#8  0x00007ffff4042103 in KAccelString::KAccelString (this=0x7fffffffbd80, input=<value optimized out>,
    initialWeight=250) at /usr/src/debug/kdelibs-4.3.90/kdeui/shortcuts/kacceleratormanager.cpp:543
#9  0x00007ffff40e01d9 in KAcceleratorManagerPrivate::manageMenuBar (mbar=0x38fdfb0,
    item=<value optimized out>) at /usr/src/debug/kdelibs-4.3.90/kdeui/shortcuts/kacceleratormanager.cpp:478
#10 0x00007ffff40e03f9 in KAcceleratorManagerPrivate::manageWidget (w=0x38fdfb0, item=0x59d7d10)
    at /usr/src/debug/kdelibs-4.3.90/kdeui/shortcuts/kacceleratormanager.cpp:331
#11 0x00007ffff40e0aa6 in KAcceleratorManagerPrivate::traverseChildren (widget=0xc84aa0, item=0x59d7d10)
    at /usr/src/debug/kdelibs-4.3.90/kdeui/shortcuts/kacceleratormanager.cpp:283
#12 0x00007ffff40e0628 in KAcceleratorManagerPrivate::manageWidget (w=0xc84aa0, item=0x59d7d10)
    at /usr/src/debug/kdelibs-4.3.90/kdeui/shortcuts/kacceleratormanager.cpp:401
#13 0x00007ffff40e14ba in KAcceleratorManagerPrivate::manage (widget=0xc84aa0)
    at /usr/src/debug/kdelibs-4.3.90/kdeui/shortcuts/kacceleratormanager.cpp:189
#14 0x00007ffff40e15cb in KAcceleratorManager::manage (widget=0xc84aa0, programmers_mode=false)
    at /usr/src/debug/kdelibs-4.3.90/kdeui/shortcuts/kacceleratormanager.cpp:505
#15 0x00007ffff40e4156 in KCheckAccelerators::checkAccelerators (this=0xc30650, automatic=true)
    at /usr/src/debug/kdelibs-4.3.90/kdeui/shortcuts/kcheckaccelerators.cpp:243
#16 0x00007ffff40e45ae in KCheckAccelerators::autoCheckSlot (this=0xc30650)                                   
    at /usr/src/debug/kdelibs-4.3.90/kdeui/shortcuts/kcheckaccelerators.cpp:197                               
#17 0x00007ffff40e4628 in KCheckAccelerators::qt_metacall (this=0xc30650, _c=InvokeMetaMethod,
    _id=<value optimized out>, _a=0x7fffffffc330)
    at /usr/src/debug/kdelibs-4.3.90/build/kdeui/kcheckaccelerators.moc:74
#18 0x00007ffff259543f in QMetaObject::activate (sender=0xc30670, m=<value optimized out>,
    local_signal_index=<value optimized out>, argv=0xffffffffffffffff) at kernel/qobject.cpp:3267
#19 0x00007ffff2592093 in QObject::event (this=0xc30670, e=0x7fffffffcac0) at kernel/qobject.cpp:1204
#20 0x00007ffff315286c in QApplicationPrivate::notify_helper (this=0xad04d0, receiver=0xc30670, e=
    0x7fffffffcac0) at kernel/qapplication.cpp:4298
#21 0x00007ffff3158e4b in QApplication::notify (this=0x7fffffffcee0, receiver=0xc30670, e=0x7fffffffcac0)
    at kernel/qapplication.cpp:4181
#22 0x00007ffff4007806 in KApplication::notify (this=0x7fffffffcee0, receiver=0xc30670, event=0x7fffffffcac0)
    at /usr/src/debug/kdelibs-4.3.90/kdeui/kernel/kapplication.cpp:302
#23 0x00007ffff258265c in QCoreApplication::notifyInternal (this=0x7fffffffcee0, receiver=0xc30670, event=
    0x7fffffffcac0) at kernel/qcoreapplication.cpp:704
#24 0x00007ffff25af305 in sendEvent (event=<value optimized out>, receiver=<value optimized out>)
    at kernel/qcoreapplication.h:215
#25 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>)
    at kernel/qeventdispatcher_unix.cpp:617
#26 0x00007ffff25abe98 in timerSourceDispatch (source=<value optimized out>)
    at kernel/qeventdispatcher_glib.cpp:184
#27 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#28 0x00007fffebe26dde in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#29 0x00007fffebe2a7a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#30 0x00007fffebe2a8d0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#31 0x00007ffff25abb63 in QEventDispatcherGlib::processEvents (this=0xa95e60, flags=<value optimized out>)
    at kernel/qeventdispatcher_glib.cpp:412
#32 0x00007ffff320086e in QGuiEventDispatcherGlib::processEvents (this=0x2b4a, flags=<value optimized out>)
    at kernel/qguieventdispatcher_glib.cpp:204
#33 0x00007ffff2580f72 in QEventLoop::processEvents (this=<value optimized out>, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
)
    at kernel/qeventloop.cpp:149
#34 0x00007ffff258134c in QEventLoop::exec (this=0x7fffffffce10, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
) at kernel/qeventloop.cpp:201
#35 0x00007ffff258509b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#36 0x000000000076576b in main (argc=<value optimized out>, argv=<value optimized out>)
    at /usr/src/debug/digikam-1.0.0/digikam/main.cpp:195
Comment 4 René Krell 2010-01-19 22:51:37 UTC 
Using:
libqt4-4.6.0+4.6.20100119 (aka almost Qt 4.6.1)
libkde4-4.3.90 (aka KDE 4.4 RC1)
Comment 5 caulier.gilles 2010-01-20 10:14:28 UTC 
The crash appears in kdelibs (not reproducible here).

Gilles Caulier
Comment 6 Christoph Feck 2010-01-25 23:11:27 UTC 
Related to bug 220347.
Comment 7 Evalinda Parkin 2010-02-12 20:48:17 UTC 
Regarding video thumbnails, I also notice many errors like this:

digikam(8483)/KEXIV2 KExiv2Iface::KExiv2Priv::printExiv2ExceptionError: Cannot load metadata using Exiv2   (Error # 11 :  /media/WD/tmp.digi/Clips/Action_HQ_00030.00.avi: The file contains data of an unknown image type

digikam(8483)/KEXIV2 KExiv2Iface::KExiv2Priv::printExiv2ExceptionError: Cannot load metadata using Exiv2   (Error # 11 :  /media/WD/tmp.digi/Clips/TeasStrSci.wmv: The file contains data of an unknown image type

I wondering why exiv2 is called, isn´t it only for images?

[Digikam 1.1 KDE 4.4.0 Arch 32bit]
Comment 8 René Krell 2010-02-12 22:26:52 UTC 
(In reply to comment #7)
> Regarding video thumbnails, I also notice many errors like this:
> 
> digikam(8483)/KEXIV2 KExiv2Iface::KExiv2Priv::printExiv2ExceptionError:
> Cannot load metadata using Exiv2 ...

Yes, but this won't be probably the reason for the crash.
It seems to be the same issue with kacceleratormanager as reported in https://bugs.kde.org/show_bug.cgi?id=220347
Comment 9 Christoph Feck 2013-09-12 21:43:38 UTC 
This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)
Comment 10 René Krell 2013-09-13 08:49:48 UTC 
This does not happen any longer, Digikam 3.4.0 on KDE 4.11.1 seems to be stable to me.
Comment 11 caulier.gilles 2018-08-25 20:35:32 UTC 
Not reproducible since digiKam use QtAV + ffmpeg to handle video files.