Bug 422831

Summary:	Kate randomly crashes when showing autocompletions with python lsp client
Product:	[Applications] kate	Reporter:	Georg Jansing <georg.jansing>
Component:	general	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED FIXED
Severity:	crash	CC:	justin.zobel
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	20.04.1
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Georg Jansing 2020-06-11 16:20:11 UTC

Application: kate (20.04.1)

Qt Version: 5.15.0
Frameworks Version: 5.70.0
Operating System: Linux 5.3.6-2.gd6c109d-default x86_64
Windowing system: Wayland
Distribution: "openSUSE Leap 15.1"

-- Information about the crash:
- What I was doing when the application crashed:
Typing python sourcecode with Python LSP Client enabled.
- Custom settings of the application:
LSP Client enabled, python-language-server module installed with "pip3 install --user"

Note: I'm using openSUSE's KDE & QT Repos (http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_Leap_15.1, http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Leap_15.1, https://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Leap_15.1)

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault

[KCrash Handler]
#4  QWidget::mapToParent (this=this@entry=0x0, pos=...) at kernel/qwidget.cpp:4105
#5  0x00007fbc8acdbe73 in QWidget::mapTo (this=this@entry=0x55da6038ba00, parent=0x55da62132af0, pos=...) at kernel/qwidget.cpp:4061
#6  0x00007fbc8acc0dd7 in QWidgetRepaintManager::flush (this=0x55da628b3650, widget=0x55da6038ba00, region=..., widgetTextures=0x0) at kernel/qwidgetrepaintmanager.cpp:1149
#7  0x00007fbc8acc1cd7 in QWidgetRepaintManager::flush (this=this@entry=0x55da628b3650) at kernel/qwidgetrepaintmanager.cpp:1104
#8  0x00007fbc8acc4ac0 in QWidgetRepaintManager::paintAndFlush (this=this@entry=0x55da628b3650) at kernel/qwidgetrepaintmanager.cpp:1014
#9  0x00007fbc8acc4d57 in QWidgetRepaintManager::sync (this=0x55da628b3650, exposedWidget=0x55da62132af0, exposedRegion=...) at kernel/qwidgetrepaintmanager.cpp:743
#10 0x00007fbc8aceea3f in QWidgetPrivate::syncBackingStore (this=this@entry=0x55da62140810, region=...) at kernel/qwidget.cpp:1766
#11 0x00007fbc8ad1180c in QWidgetWindow::handleExposeEvent (this=this@entry=0x55da62675d60, event=event@entry=0x7ffcf676fae0) at kernel/qwidgetwindow.cpp:1016
#12 0x00007fbc8ad12479 in QWidgetWindow::event (this=0x55da62675d60, event=0x7ffcf676fae0) at kernel/qwidgetwindow.cpp:342
#13 0x00007fbc8acb42fc in QApplicationPrivate::notify_helper (this=this@entry=0x55da5f6ffdd0, receiver=receiver@entry=0x55da62675d60, e=e@entry=0x7ffcf676fae0) at kernel/qapplication.cpp:3671
#14 0x00007fbc8acbb210 in QApplication::notify (this=0x7ffcf6770010, receiver=0x55da62675d60, e=0x7ffcf676fae0) at kernel/qapplication.cpp:3417
#15 0x00007fbc89b1ad73 in QCoreApplication::notifyInternal2 (receiver=0x55da62675d60, event=0x7ffcf676fae0) at kernel/qcoreapplication.cpp:1061
#16 0x00007fbc89b1af5e in QCoreApplication::sendSpontaneousEvent (receiver=receiver@entry=0x55da62675d60, event=event@entry=0x7ffcf676fae0) at kernel/qcoreapplication.cpp:1468
#17 0x00007fbc8a146d47 in QGuiApplicationPrivate::processExposeEvent (e=0x55da62855c90) at kernel/qguiapplication.cpp:3193
#18 0x00007fbc8a146fad in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0x55da62855c90) at kernel/qguiapplication.cpp:2014
#19 0x00007fbc8a11edcb in QWindowSystemInterface::sendWindowSystemEvents (flags=...) at kernel/qwindowsysteminterface.cpp:1175
#20 0x00007fbc7acabd60 in userEventSourceDispatch (source=<optimized out>) at qeventdispatcher_glib.cpp:74
#21 0x00007fbc826dfe87 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#22 0x00007fbc826e0230 in ?? () from /usr/lib64/libglib-2.0.so.0
#23 0x00007fbc826e02bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#24 0x00007fbc89b7d3cc in QEventDispatcherGlib::processEvents (this=0x55da5f745520, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#25 0x00007fbc89b195fa in QEventLoop::exec (this=this@entry=0x7ffcf676fdc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:232
#26 0x00007fbc89b22df7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1369
#27 0x000055da5e5964ca in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kate-20.04.1-lp151.4.4.x86_64/kate/main.cpp:633
[Inferior 1 (process 16174) detached]

Possible duplicates by query: bug 245785, bug 216010, bug 213471, bug 209916, bug 206960.

Reported using DrKonqi

Comment 1 Justin Zobel 2020-11-13 05:37:03 UTC

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.

Comment 2 Bug Janitor Service 2020-11-28 04:33:54 UTC

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
mark the bug 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!

Comment 3 Georg Jansing 2020-12-03 16:56:23 UTC

Sorry for the late reply, I did not have time for some Python work before. Over the last days I did get to some testing, I did not have a crash with the LSP Client reenabled. Seems fixed for me :). Thanks!

I the crashes reappear, I would reopen the bug?

Comment 4 Christoph Feck 2020-12-04 00:23:32 UTC

If you encounter the same issue, set the status of this ticket to REOPENED. If you are unsure, you are also free to report in a separate ticket.