Bug 451808 - Kate crashed on closure of a tab/file
Summary: Kate crashed on closure of a tab/file
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: 20.04.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-03-23 00:11 UTC by Stewart Patch
Modified: 2022-03-23 14:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stewart Patch 2022-03-23 00:11:13 UTC
Application: kate (20.04.2)

Qt Version: 5.12.7
Frameworks Version: 5.76.0
Operating System: Linux 5.3.18-150300.59.54-default x86_64
Windowing system: Wayland
Distribution: "openSUSE Leap 15.3"

-- Information about the crash:
- What I was doing when the application crashed:
Having an open/saved file I opened a second tab/file in the same window then closed the first tab without making any changes to either file. At this point Kate crashed. This has happened more than once.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kate (kate), signal: Aborted
[KCrash Handler]
#4  0x00007f52dd132cdb in raise () from /lib64/libc.so.6
#5  0x00007f52dd134375 in abort () from /lib64/libc.so.6
#6  0x00007f52dd99a87b in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1907
#7  QMessageLogger::fatal (this=this@entry=0x7ffea10e2e00, msg=msg@entry=0x7f52d0ccbbe0 "The Wayland connection broke. Did the Wayland compositor die?") at global/qlogging.cpp:888
#8  0x00007f52d0c654ed in QtWaylandClient::QWaylandDisplay::checkError (this=<optimized out>) at qwaylanddisplay.cpp:179
#9  0x00007f52d0c6553e in QtWaylandClient::QWaylandDisplay::flushRequests (this=0x55e990531fb0) at qwaylanddisplay.cpp:192
#10 0x00007f52ddbc8e75 in QMetaObject::activate (sender=sender@entry=0x55e9905ab870, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3804
#11 0x00007f52ddbc9587 in QMetaObject::activate (sender=sender@entry=0x55e9905ab870, m=m@entry=0x7f52de0472a0 <QAbstractEventDispatcher::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3657
#12 0x00007f52ddb95333 in QAbstractEventDispatcher::awake (this=this@entry=0x55e9905ab870) at .moc/moc_qabstracteventdispatcher.cpp:148
#13 0x00007f52ddbf642e in QEventDispatcherGlib::processEvents (this=0x55e9905ab870, flags=...) at kernel/qeventdispatcher_glib.cpp:429
#14 0x00007f52ddb975ba in QEventLoop::exec (this=this@entry=0x7ffea10e3020, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#15 0x00007f52ddba07c0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1389
#16 0x000055e98f8044fa in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kate-20.04.2-bp153.2.2.1.x86_64/kate/main.cpp:633
[Inferior 1 (process 11914) detached]

Possible duplicates by query: bug 450308, bug 448987, bug 448830, bug 448140, bug 447519.

Reported using DrKonqi
Comment 1 Waqar Ahmed 2022-03-23 14:12:04 UTC
Hi, please try with a newer version of Kate. The version you are using is very old and even the Qt version is quite old. There have been lots of wayland fixes in the meantime.