Hello,

I'd like to raise this issue again. On Friday akonadi started segfaulting. It eventually causes Dr Konqui to run. It asks if I want to file a report. I click yes. It does something and I click on see details. It says no backtrace could be generated. I click next, it says it can't file a report due to no information.

Since debug symbols are not available, Dr Konqui probably doesn't work for anyone. Wouldn't it be better to disable Dr Konqui and let abrtd process the crash in the normal Fedora infrastructure so that all these crashes are not being thrown away?

Best Regards, -Steve

On Monday, February 4, 2019 11:19:13 AM EDT Steve Grubb wrote:

I was curious about something. KDE has its own crash handling system. How does this community track any metrics around code stability if upstream gets reports? Kontact has segfaulted 20 times on me today. Each time it says it cannot generate a bug report. Abrtd does not seem to pick up anything. Shouldn't it? How does this community track when a recent update suddenly starts making things crash? Kontact was fine 3 weeks ago. I updated today (3 weeks of patches) and its crashing all the time to the point its unusable. It won't generate a bug report, abrtd seems not to notice either.

-Steve _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org