Application: kate (17.12.2) Qt Version: 5.10.1 Frameworks Version: 5.43.0 Operating System: Linux 4.15.5-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: I am not entirely certain how to reproduce it, but kate crashed immediately after I copied a file into a folder I previously edited a file with the same name and deleted it and told kate to ignore the deletion. -- Backtrace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7feebf6e62c0 (LWP 3402))] Thread 2 (Thread 0x7feea0e1b700 (LWP 3405)): #0 0x00007feeb9f3297b in poll () at /usr/lib/libc.so.6 #1 0x00007feeb39ffff3 in () at /usr/lib/libglib-2.0.so.0 #2 0x00007feeb3a0010e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x00007feeba87e314 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #4 0x00007feeba8203db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #5 0x00007feeba62f7ae in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x00007feebaca1416 in () at /usr/lib/libQt5DBus.so.5 #7 0x00007feeba634b4d in () at /usr/lib/libQt5Core.so.5 #8 0x00007feeb5a0f08c in start_thread () at /usr/lib/libpthread.so.0 #9 0x00007feeb9f3ce7f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7feebf6e62c0 (LWP 3402)): [KCrash Handler] #5 0x00007feebb18c002 in () at /usr/lib/libKF5CoreAddons.so.5 #6 0x00007feeba8526c6 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #7 0x00007feeba85efa9 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #8 0x00007feeba85f384 in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #9 0x00007feebbd09fec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #10 0x00007feebbd119c6 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #11 0x00007feeba821da0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x00007feeba87ef8e in () at /usr/lib/libQt5Core.so.5 #13 0x00007feeb39ffe38 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #14 0x00007feeb3a00081 in () at /usr/lib/libglib-2.0.so.0 #15 0x00007feeb3a0010e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #16 0x00007feeba87e2f1 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #17 0x00007feead163482 in () at /usr/lib/libQt5XcbQpa.so.5 #18 0x00007feeba8203db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #19 0x00007feeba8297d8 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #20 0x000055a42c0574b9 in () #21 0x00007feeb9e67f4a in __libc_start_main () at /usr/lib/libc.so.6 #22 0x000055a42c0584ea in _start () Reported using DrKonqi
Hi, sorry for the crash, but we need some way to reproduce it. (the backtrace doesn't really help to find it, as it is)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Sorry, but it never happened again and it was a very specific situation in the first place. So I am not sure what more information I could provide.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!