https://bugs.kde.org/show_bug.cgi?id=383861
Harald Sitter <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from Harald Sitter <[email protected]> --- That is really out of scope for drkonqi IMO. For persistent crash tracking I think one should look at system-level solutions such as coredumpd, apport or abrt. Drkonqi is, at its heart, a tool to report a crash with. Not a tool to manage crash reports and record them on disk in some directory that is safe enough, yet accessible enough, and do so in a time frame so as to not inhibit logout/shutdown whatever. And the only value we'd have from this is a **chance** at getting crash reports happening at logout or during otherwise fatal incidents (X11 deadlock or whatever). Poor return on investment if you ask me. Maybe, and that's a big maybe, drkonqi could be glued on top of an aforementioned solution, but even that seems also largely moot. Both apport and abrt already have GUIs and coredumpd is currently not really designed around having a GUI stacked on top. -- You are receiving this mail because: You are watching all bug changes.
