Are both drkonqi and abrt needed in the KDE Spin?

[oswald (oswald_c)]

I’m running Fedora 40 KDE, having installed it using the Everything ISO. It comes with both drkonqi (Crashed Processes Viewer) and abrt (Problem Reporting). So far, drkonqi has logged a few crashes, and abrt none (unlike when I was running Fedora 39 Workstation earlier this year).

Looking at the features of both applications, there seems to be a lot of overlap. Do I need abrt installed, or is there a category of crash that it will pick up, that drkonqi will not?

[rokejulianlockhart (Mr. Beedell, Roke Julian Lockhart (RJLB))]

@oswald, Dr. Konqi allows you to report crashes with KDE’s applications upstream, because it integrates with coredumpctl directly. gnome-abrt utilises abrt, which duplicates codreumpctl to provide more information than it does, and reports bugs downstream, to Fedora. When you file a report, if both can catch it, you should file it to both, so keep both installed.

That is, unless you utilise plasma Mobile, in which case solely gnome-abrt is of use (insofar as you know how to utilise coredumpctl debug):

Abrt setup on a minimal install

For me, the cause of abrt not working was installing the Plasma Mobile pattern on the Plasma Mobile base (I’d also not selected the KDE Workspaces pattern, which might have mattered.) The to that solution is to install Plasma Mobile pattern on the KDE Workspaces base, with the KDE Workspaces pattern also selected. How damn unintuitive. This also installs plasma-drkonqi and sealert, by default. However, drkonqi still doesn’t invoke in --dialog mode: …which is probably KDE’s fault.