rjvbb added a comment.
> When I click "Close" in drkonqi (there's no Cancel button), crashtest
resumes and exits, without any error message from KCrash.
On my system, without the patch:
> killall -SEGV kate
> KCrash: Application 'kate' crashing...
KCrash: Attempting to start /opt/local/lib/x86_64-linux-gnu/libexec/drkonqi
from kdeinit
sock_file=/run/user/505/kdeinit5__0
[2] + Suspended (signal) kate5
#### here I hit the close button or Escape
> QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
QSocketNotifier: Invalid socket 16 and type 'Read', disabling...
Unable to start Dr. Konqi
Re-raising signal for core dump handling.
>
>
> drkonqi Plasma/5.13 but master doesn't seem very different.
I just updated drkonqi to master/head, but the error handling is in KCrash.
Is it possible that your drkonqi exits with 0 when you quit it while mine
somehow returns a non-zero exit code?
Note: I haven't patched drkonqi to do that - I just checked :)
REPOSITORY
R285 KCrash
REVISION DETAIL
https://phabricator.kde.org/D14606
To: rjvbb, #frameworks
Cc: dfaure, kde-frameworks-devel, michaelh, ngraham, bruns
