| Summary: | Cannot associate backtrace with existing bug | ||
|---|---|---|---|
| Product: | [Applications] drkonqi | Reporter: | Kai Uwe Broulik <kde> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | bugzilla, jan_braun, mail, walch.martin |
| Priority: | NOR | ||
| Version First Reported In: | 5.3.2 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Kai Uwe Broulik
2015-07-03 21:41:52 UTC
I tried to submit a report, Dr Konqi found what looked like a very similar report so I wished to append my info the the existing report. However when viewing the existing report and clicking on the "suggest this report is related" button it becomes highlighted in blue (i.e. it is selected) but that is it - nothing else happens. Thus it is impossible to append the report. Always reproducible when attempting to submit the same report (a crash with System Settings), though I haven't had anything else to report since upgrading to Fedora 22. I can confirm that I am unable to associate crashes with other reports. The search works, the button is there. But after requesting the association, DrKonqi immediately forgets about it. Duplicate of bug 348316 ? The description matches my experience. How or who to mark this a duplicate? (In reply to Jan-Matthias Braun from comment #4) > The description matches my experience. How or who to mark this a duplicate? I concur. It likely has the same cause even if the human visible results are not exactly the same for all. *** This bug has been marked as a duplicate of bug 354110 *** |