Just FYI, on a systemd based system, the coredump is already automatically stored in journal and can be accessed easily by coredumpctl.
Personally I use drkonqi a lot to fix issues, it's more visible for me to notice the problem (as developer). I just wonder whether drkonqi provides some extra functionality other than bug report, e.g. restart the crashed program?. On Mon, Nov 16, 2015 at 4:38 AM, Martin Graesslin <mgraess...@kde.org> wrote: > On Monday, November 16, 2015 12:11:09 PM CET Luca Beltrame wrote: >> In data lunedì 16 novembre 2015 10:50:01 CET, Sebastian Kügler ha scritto: >> > us, and I also think that it would be cheating to just hide the drkonqi >> > window, but on the other hand, if it improves the user experience, that's >> > good, no? >> >> With my forum admin hat on: what I'm supposed to tell a user if he/she >> experiences a crash and DrKonqi is disabled? > > Possibilities: > * have DrKonqui use an SNI where it reports to > * easy way to enable DrKonqui (useful for reproducable bugs) > * show a notification on crash (not so useful with plasma restarts) > * store coredumps somewhere > * ... > > Cheers > Martin > _______________________________________________ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel > _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
