https://bugs.kde.org/show_bug.cgi?id=371899
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from [email protected] --- The crash backtrace is not clear : Thread 2 (Thread 0x7efc51688700 (LWP 27432)): [KCrash Handler] #6 0x00007efc73bae0c7 in raise () at /lib64/libc.so.6 #7 0x00007efc73baf478 in abort () at /lib64/libc.so.6 #8 0x00007efc73beb784 in () at /lib64/libc.so.6 #9 0x00007efc73bf1026 in malloc_printerr () at /lib64/libc.so.6 #10 0x00007efc73bf35d5 in _int_malloc () at /lib64/libc.so.6 #11 0x00007efc73bf495c in malloc () at /lib64/libc.so.6 #12 0x00007efc62dd94c0 in () at /usr/lib64/tls/libnvidia-tls.so.367.44 #13 0x00007efc7456d86f in QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags<QArrayData::AllocationOption>) () at /usr/lib64/libQt5Core.so.5 #14 0x00007efc745efb23 in QString::QString(int, Qt::Initialization) () at /usr/lib64/libQt5Core.so.5 #15 0x00007efc7477929d in () at /usr/lib64/libQt5Core.so.5 #16 0x00007efc745f63ce in QString::fromUtf8_helper(char const*, int) () at /usr/lib64/libQt5Core.so.5 #17 0x00007efc705aefc1 in () at /usr/lib64/libQt5DBus.so.5 #18 0x00007efc705a78ce in () at /usr/lib64/libQt5DBus.so.5 #19 0x00007efc6494c6a6 in dbus_connection_dispatch () at /lib64/libdbus-1.so.3 #20 0x00007efc705a74f1 in () at /usr/lib64/libQt5DBus.so.5 #21 0x00007efc705a77e9 in () at /usr/lib64/libQt5DBus.so.5 #22 0x00007efc7474bcfc in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #23 0x00007efc747c316e in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5 #24 0x00007efc747587f9 in QSocketNotifier::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #25 0x00007efc747235f1 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #26 0x00007efc74772b3e in () at /usr/lib64/libQt5Core.so.5 #27 0x00007efc69c0fc84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #28 0x00007efc69c0fed8 in () at /usr/lib64/libglib-2.0.so.0 #29 0x00007efc69c0ff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #30 0x00007efc74771f4b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #31 0x00007efc7472189b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #32 0x00007efc7456802a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #33 0x00007efc70596465 in () at /usr/lib64/libQt5DBus.so.5 #34 0x00007efc7456c859 in () at /usr/lib64/libQt5Core.so.5 #35 0x00007efc7036a0a4 in start_thread () at /lib64/libpthread.so.0 #36 0x00007efc73c5e02d in clone () at /lib64/libc.so.6 ... where it crash do not show any digiKam code. I see Akonadi working in background in this backtrace (indirect trace). Why ? I suspect something wrong on your system... Try to reproduce the crash with a better backtrace. Another test : try to use my Linux 64 bits AppImage bundle of next 5.3.0 to see if it reproducible. https://drive.google.com/open?id=0BzeiVr-byqt5SUZRMGtWa3VCUDg Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
