Bug 349876 - Cannot associate backtrace with existing bug
Summary: Cannot associate backtrace with existing bug
Status: RESOLVED DUPLICATE of bug 354110
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: 5.3.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-03 21:41 UTC by Kai Uwe Broulik
Modified: 2015-10-21 18:52 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Uwe Broulik 2015-07-03 21:41:52 UTC 
I wanted to report a bug and Drkonqi found a duplicate which was a very similar crash. I double clicked it and clicked the "associate with this report" button but nothing happened

Reproducible: Didn't try
Comment 1 wintonian 2015-08-12 15:14:37 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.
Comment 2 Jan-Matthias Braun 2015-08-20 11:43:05 UTC 
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.
Comment 3 Christoph Feck 2015-09-27 11:23:43 UTC 
Duplicate of bug 348316 ?
Comment 4 Jan-Matthias Braun 2015-09-27 12:04:33 UTC 
The description matches my experience. How or who to mark this a duplicate?
Comment 5 wintonian 2015-09-27 12:10:01 UTC 
(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.
Comment 6 Christoph Feck 2015-10-21 18:52:49 UTC 

*** This bug has been marked as a duplicate of bug 354110 ***