Mass deduplication and reassignment of ABRT bugs

Michael Schwendt mschwendt at
Tue Mar 20 19:58:36 UTC 2012

On Fri, 16 Mar 2012 16:35:19 +0100, ML (Miroslav) wrote:

> If you find a suspicious action, please let us know at
> crash-catcher at or file a ticket at

That list requires a subscription, so my earlier message had bounced.

Here's another suspicious action:

Is anybody from the ABRT team watching these actions?
The bot closed bug 714364 (gtk2) as duplicate of bug 701926
(rhythmbox) and did  the same for the other mentioned tickets.
That only makes sense if somebody then performs the rhythmbox->gtk2
reassignment. I've done it here, but what about other tickets where
maybe nobody is pays attention?

           What    |Removed                     |Added
             Status|NEW                         |CLOSED
         Resolution|                            |DUPLICATE
        Last Closed|                            |2012-03-20 15:42:27

--- Comment #3 from abrt-bot 2012-03-20 15:42:27 EDT ---
Backtrace analysis found this bug to be similar to bug #701926, closing as

Bugs which were found to be similar to this bug: 
  clamtk: bug #785723
  qemu-launcher: bug #709824
  rhythmbox: bug #701926
  totem: bug #653083
  transmission: bug #706663

This comment is automatically generated.

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

Fedora release 17 (Beefy Miracle) - Linux 3.3.0-1.fc17.x86_64
loadavg: 0.03 0.05 0.05

More information about the devel mailing list