Kdevelop will crash every time when quit by clicking on the close button of the window. Reproducible: Always Steps to Reproduce: 1. Open kdevelop 2. Close kdevelop by the close button on the title bar Actual Results: A window popup declaring a crash of kdevelop Expected Results: Close normally Version 5.0.2 Using: KDE Frameworks 5.27.0 Qt 5.7.0 (built against 5.7.0) The xcb windowing system The following are obtained from the popup window after crash. Executable: kdevelop PID: 12084 Signal: Segmentation fault (11) Time: 2016/10/18 09:58:49 Application: kdevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fac336c0800 (LWP 12084))] Thread 2 (Thread 0x7fac0bfff700 (LWP 12086)): [KCrash Handler] #6 0x00007fac30dcf9cf in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () at /usr/lib/libQt5Core.so.5 #7 0x00007fac32902530 in () at /usr/lib/libQt5DBus.so.5 #8 0x00007fac32902784 in () at /usr/lib/libQt5DBus.so.5 #9 0x00007fac32902ab9 in () at /usr/lib/libQt5DBus.so.5 #10 0x00007fac328eef2e in () at /usr/lib/libQt5DBus.so.5 #11 0x00007fac30bc5d78 in () at /usr/lib/libQt5Core.so.5 #12 0x00007fac29da9454 in start_thread () at /usr/lib/libpthread.so.0 #13 0x00007fac304db7df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fac336c0800 (LWP 12084)): #0 0x00007fac29daf10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x00007fac30bc6c2b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x00007fac30bc591e in QThread::wait(unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x00007fac328eecc6 in () at /usr/lib/libQt5DBus.so.5 #4 0x00007fac328eed59 in () at /usr/lib/libQt5DBus.so.5 #5 0x00007fac30428990 in __run_exit_handlers () at /usr/lib/libc.so.6 #6 0x00007fac304289ea in () at /usr/lib/libc.so.6 #7 0x00007fac30413298 in __libc_start_main () at /usr/lib/libc.so.6 #8 0x000000000040c0ea in _start ()
This bug also happens for kdevelop version 5.0.1
Could you install debug symbols for Qt5DBus? Then reproduce the issue and send us the updated backtrace?
In current version, Version 5.0.80, I no longer encounter this bug. Now I change the status to fixed.