Application: kdeinit5 (16.08.2) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.90-18.32-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I opened a new Konsole. I used a shortcut key and suspect two instances were starting up in close succession. The crash can be reproduced sometimes. -- Backtrace: Application: Konsole (kdeinit5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2747e0e780 (LWP 460))] Thread 3 (Thread 0x7f272acfd700 (LWP 462)): #0 0x00007f2742a0e7b9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x00007f27429ccb51 in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #2 0x00007f27429cd27f in () at /usr/lib64/libglib-2.0.so.0 #3 0x00007f27429cd42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x00007f27464e233b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x00007f274648ffeb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #6 0x00007f27462caf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x00007f273cc83295 in () at /usr/lib64/libQt5DBus.so.5 #8 0x00007f27462cf9e9 in () at /usr/lib64/libQt5Core.so.5 #9 0x00007f2743692744 in start_thread () at /lib64/libpthread.so.0 #10 0x00007f2745f66aad in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f2731679700 (LWP 461)): #0 0x00007f2745f5e20d in poll () at /lib64/libc.so.6 #1 0x00007f27472873e2 in () at /usr/lib64/libxcb.so.1 #2 0x00007f2747288fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x00007f2734205839 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x00007f27462cf9e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x00007f2743692744 in start_thread () at /lib64/libpthread.so.0 #6 0x00007f2745f66aad in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f2747e0e780 (LWP 460)): [KCrash Handler] #6 0x00007f2745eb18d7 in raise () at /lib64/libc.so.6 #7 0x00007f2745eb2caa in abort () at /lib64/libc.so.6 #8 0x00007f2745eef1b4 in () at /lib64/libc.so.6 #9 0x00007f2745ef4706 in malloc_printerr () at /lib64/libc.so.6 #10 0x00007f2745ef4aa2 in malloc_consolidate () at /lib64/libc.so.6 #11 0x00007f2745ef53fb in _int_free () at /lib64/libc.so.6 #12 0x00007f2746493dc3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #13 0x00007f27464e2c93 in () at /usr/lib64/libQt5Core.so.5 #14 0x00007f27429cd134 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #15 0x00007f27429cd388 in () at /usr/lib64/libglib-2.0.so.0 #16 0x00007f27429cd42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #17 0x00007f27464e231c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #18 0x00007f274648ffeb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #19 0x00007f2746497ed6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #20 0x00007f273547cc87 in kdemain () at /usr/lib64/libkdeinit5_konsole.so #21 0x0000000000408720 in () #22 0x0000000000409a1e in () #23 0x000000000040a101 in () #24 0x00000000004051bc in () #25 0x00007f2745e9d6e5 in __libc_start_main () at /lib64/libc.so.6 #26 0x0000000000405f79 in _start () Reported using DrKonqi
Can you explain this better? Thanks - What I was doing when the application crashed: I opened a new Konsole. I used a shortcut key and suspect two instances were starting up in close succession.
The application crashed when opening using shortcut keys. There was already a Konsole open and I was trying to open another one. I think it is possible that I ended up hitting the shortcut twice in quick succession by mistake and that could have triggered the crash. I hope that helps.
Konsole 16.08 is 2 years old at this point. Your Qt and Frameworks versions are also very old. Unfortunately we are not able to offer support for software that is so old. Please see https://community.kde.org/Get_Involved/Bug_Reporting#Step_2:_Make_sure_it_hasn.27t_already_been_fixed