Bug 548871 - Unexpected behavior in ABRT when dealing with (ABRT duplicate stacktraces) versus (bugzilla duplicate bugs)
Summary: Unexpected behavior in ABRT when dealing with (ABRT duplicate stacktraces) ve...
Keywords:
Status: CLOSED DUPLICATE of bug 538783
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jiri Moskovcak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-18 22:17 UTC by Dave Malcolm
Modified: 2015-02-01 22:50 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-01-28 20:00:43 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Dave Malcolm 2009-12-18 22:17:57 UTC 
Bug 544055 was filed by ABRT, and I manually marked it as a duplicate of bug 540810.
However, since then, numerous people have added themselves to the CC on the former bug; see https://bugzilla.redhat.com/show_activity.cgi?id=544055

I asked, and according to 
https://bugzilla.redhat.com/show_bug.cgi?id=544055#c4:
"abrt claimed that this problem had not been reported before, so I filled in all
appropriate info.

I am surprised it did not create a new BZ but attached to an existing one.
Looks like a bug, indeed."

So it looks like ABRT is detecting virt-manager crashes, and somehow detecting that the crash is a duplicate of bug 544055 (perhaps via analysis of the stack trace?).

This seems surprising to me; I believe that it would be better if it detected that 544055 was marked in bugzilla as a duplicate of bug 540810 and added the user to the CC of that latter bug.
Comment 1 Christopher Beland 2010-01-28 20:00:43 UTC 
Ah, the irony...

*** This bug has been marked as a duplicate of bug 538783 ***
Note You need to log in before you can comment on or make changes to this bug.