Bug 379786

Summary: kontact crashed by using ctrl+q
Product: [Frameworks and Libraries] frameworks-knotifications Reporter: nick.haflinger
Component: generalAssignee: Martin Klapetek <mklapetek>
Status: RESOLVED DUPLICATE    
Severity: crash CC: barnabas02, kdelibs-bugs
Priority: NOR Keywords: drkonqi
Version: 5.18.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description nick.haflinger 2017-05-13 17:32:46 UTC
Application: kontact (5.1.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-77-generic x86_64
Distribution: Ubuntu 16.04.2 LTS

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

I booted the system, started kontact, checked the mails, got offline, finished with ctrl+q and kontact crashed

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f46671cb940 (LWP 1713))]

Thread 4 (Thread 0x7f46137fe700 (LWP 1718)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f467e3e7aa3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x00007f467e708541 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x00007f467a49b6ba in start_thread (arg=0x7f46137fe700) at pthread_create.c:333
#4  0x00007f468046182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f4613fff700 (LWP 1717)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f467e3e6a74 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x00007f467e708541 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x00007f467a49b6ba in start_thread (arg=0x7f4613fff700) at pthread_create.c:333
#4  0x00007f468046182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f465e0ea700 (LWP 1715)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f467e6d888b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x00007f467e6d88c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x00007f467a49b6ba in start_thread (arg=0x7f465e0ea700) at pthread_create.c:333
#4  0x00007f468046182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f46671cb940 (LWP 1713)):
[KCrash Handler]
#6  0x00000000021c4730 in ?? ()
#7  0x00007f465f8f09c6 in qDeleteAll<QList<Phonon::MediaObject*>::const_iterator> (end=..., begin=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:317
#8  qDeleteAll<QList<Phonon::MediaObject*> > (c=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qalgorithms.h:325
#9  NotifyByAudio::~NotifyByAudio (this=0x1ef1700, __in_chrg=<optimized out>) at ../../src/notifybyaudio.cpp:46
#10 0x00007f465f8f0a59 in NotifyByAudio::~NotifyByAudio (this=0x1ef1700, __in_chrg=<optimized out>) at ../../src/notifybyaudio.cpp:48
#11 0x00007f4680f6f28b in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007f4680f78b00 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007f465f8d4889 in KNotificationManagerSingleton::~KNotificationManagerSingleton (this=<optimized out>, __in_chrg=<optimized out>) at ../../src/knotificationmanager.cpp:58
#14 (anonymous namespace)::Q_QGS_s_self::Holder::~Holder (this=<optimized out>, __in_chrg=<optimized out>) at ../../src/knotificationmanager.cpp:64
#15 0x00007f4680394ff8 in __run_exit_handlers (status=0, listp=0x7f468071e5f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#16 0x00007f4680395045 in __GI_exit (status=<optimized out>) at exit.c:104
#17 0x00007f468037b837 in __libc_start_main (main=0x403b50 <main>, argc=1, argv=0x7ffd94459fc8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd94459fb8) at ../csu/libc-start.c:325
#18 0x0000000000404fe9 in _start ()

Reported using DrKonqi
Comment 1 Christoph Feck 2017-05-16 01:14:13 UTC
*** Bug 379824 has been marked as a duplicate of this bug. ***
Comment 2 Christoph Feck 2017-05-29 23:12:54 UTC
Bug 380114 has a better backtrace with newer versions.

*** This bug has been marked as a duplicate of bug 380114 ***