Steps to reproduce: 1. Start Kate with long file. 2. Click on various minimap regions or drag current minimap view. Reproducibility: often. Contents of ~/.local/share/sddm/wayland-session.log file: kf5idletime_kwayland: This plugin does not support polling idle time QObject::connect: invalid null parameter Using Wayland-EGL Using the 'wl-shell' shell integration Creating the cache for: "applications:org.kde.kate.desktop" Already in database? true First update : QDateTime(2017-08-22 11:51:50.000 EEST Qt::TimeSpec(LocalTime)) Last update : QDateTime(2017-08-22 15:13:17.000 EEST Qt::TimeSpec(LocalTime)) After the adjustment Current score : 25 First update : QDateTime(2017-08-22 11:51:50.000 EEST Qt::TimeSpec(LocalTime)) Last update : QDateTime(2017-08-22 15:13:17.000 EEST Qt::TimeSpec(LocalTime)) Interval length is 0 New score : 26 ResourceScoreUpdated: "5a75bcc8-f88e-463f-8b82-c2702211560c" "org.kde.libtaskmanager" "applications:org.kde.kate.desktop" KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kate path = /usr/bin pid = 1847 KCrash: Arguments: /usr/bin/kate -b
We fixed a few issues in the last months regarding crashs, like that the preview of text might crash on wayland. Please try current master if possible, at least we can't reproduce that crash at the moment. We would need more info what to do or some backtrace.
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!
A backtrace after crash: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1ea019a800 (LWP 2095))] Thread 2 (Thread 0x7f1e85fe3700 (LWP 2128)): #0 0x00007f1e9468fd79 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007f1e946499a3 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f1e9464a36b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f1e9464a54c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f1e9b420a9b in QEventDispatcherGlib::processEvents (this=0x7f1e80000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x00007f1e9b3c4dea in QEventLoop::exec (this=this@entry=0x7f1e85fe2d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x00007f1e9b1efb8a in QThread::exec (this=<optimized out>) at thread/qthread.cpp:525 #7 0x00007f1e9b868e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x00007f1e9b1faaab in QThreadPrivate::start (arg=0x7f1e9bae0d60) at thread/qthread_unix.cpp:367 #9 0x00007f1e965cd6db in start_thread (arg=0x7f1e85fe3700) at pthread_create.c:463 #10 0x00007f1e9aaf288f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f1ea019a800 (LWP 2095)): [KCrash Handler] #6 0x000055aa204bc730 in ?? () #7 0x00007f1e9b3cfdc9 in QMetaObject::cast (this=0x7f1e9cf7df80 <QWidgetWindow::staticMetaObject>, obj=obj@entry=0x55aa20078fa0) at kernel/qmetaobject.cpp:366 #8 0x00007f1e9b3cfe05 in QMetaObject::cast (this=<optimized out>, obj=obj@entry=0x55aa20078fa0) at kernel/qmetaobject.cpp:355 #9 0x00007f1e9c8b6579 in qobject_cast<QWidgetWindow*> (object=0x55aa20078fa0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:504 #10 QApplicationPrivate::notifyActiveWindowChange (this=<optimized out>, previous=<optimized out>) at kernel/qapplication.cpp:2186 #11 0x00007f1e9c0b6ce5 in QGuiApplicationPrivate::processActivatedEvent (e=<optimized out>) at kernel/qguiapplication.cpp:2309 #12 0x00007f1e9c0b6f4d in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0x55aa2032b940) at kernel/qguiapplication.cpp:1838 #13 0x00007f1e9c08ff0b in QWindowSystemInterface::sendWindowSystemEvents (flags=...) at kernel/qwindowsysteminterface.cpp:1032 #14 0x00007f1e8ab7957b in QPAEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #15 0x00007f1e9b3c4dea in QEventLoop::exec (this=this@entry=0x7ffe4e624690, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #16 0x00007f1e9b3cdfa0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1336 #17 0x000055aa1ec77a61 in main (argc=<optimized out>, argv=<optimized out>) at ./kate/main.cpp:639
Sorry, can not reproduce this :/ The backtrace is not that helpful, if somebody can reproduce this with some recent version, please reopen. Given this seemed to happen on Wayland there should have been a lot of progress in the last two years inside the stack.