It seems like every time I click on File > Quit in Kate, Dr. Konqi pops up offering to send a crash report. Anyone else experiencing this?
Which KDE Plasma version?
Please post the output of the CLI command “kinfo” …
On this system executing the newest KDE Gear release (25.12.1), I’m not seeing any Kate crashes – which doesn’t mean I’m not seeing any crashes at all but, the cause of what I’'m experiencing seems to be an issue with Qt version 6.10.1 → relief has been discussed for delivery of a future release of Qt … 
> kinfo
Operating System: openSUSE Leap 16.0
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.12.0-160000.8-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 8600G w/ Radeon 760M Graphics
Memory: 32 GiB of RAM (30.5 GiB usable)
Graphics Processor: AMD Radeon Graphics
>
- N.B.: Not the standard Leap 16.0 KDE Plasma version – it’s the version in the openSUSE KDE Gear repository …
No. But send the crash report anyways
Hi. Did you try to start Kate from terminal? And after how you think if you push X on window or choose Exit in Kate this is end for Kate. A lot of thinks have to be done and then something happen and crash. Simple.
Radek Glebicki
Output of kinfo:
Operating System: EndeavourOS
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor
Memory: 64 GiB of RAM (62.7 GiB usable)
Graphics Processor: AMD Radeon RX 6800
AFAICS, nothing strange …
What does the CLI command “coredumpctl” indicate?
- In particular the “SIG” column – “SIGSEGV” is bad – a Segmentation Fault – “SIGABRT” isn’t as bad – “Abort signal from abort(3)” …
With the CLI command “drkonqi-coredump-gui” you can pick the crash to report – here: <https://bugs.kde.org/>
Of course, the issue stopped immediately when I tried to replicate it, but I recently reported with Dr. Konqi when the issue occurred again today.