Bug 803891
| Summary: | Crash reporter repetitively attempts report same crash despite cancel on it | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Vytas <vytautas1987> |
| Component: | kde-runtime | Assignee: | Than Ngo <than> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | jreznik, kevin, ltinkl, rdieter, rnovacek, than |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-03-15 22:35:32 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This just works as designed. DrKonqi has no way to know that the crash is the same as a previous one because it does not remember previous crashes. If you think this should be changed, please file a wishlist bug at https://bugs.kde.org/ (the upstream bug tracker), but to be honest, I doubt that this will be implemented any time soon. (In any case, this is not something we will implement downstream in Fedora.) |
Description of problem: It would be nice that crash reporter would not try to report same thing every day. Version-Release number of selected component (if applicable): All How reproducible: 100% Steps to Reproduce: while() { crash report? cancel } Actual results: endless loop of error tables while doing other routines. Expected results: one error should be enough Additional info: