Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 592010 - ABRT and searching for already open bugs.
Summary: ABRT and searching for already open bugs.
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Nikola Pajkovsky
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-13 17:01 UTC by Peter Hjalmarsson
Modified: 2014-02-02 22:14 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-06-27 16:20:24 UTC
Type: ---

Attachments (Terms of Use)

Description Peter Hjalmarsson 2010-05-13 17:01:09 UTC
Description of problem:
I really think ABRT should have a function to seek for an already open bug for something ABRT has picked up.
I would like a function or button like "see if already reported".

How this function should look or work I can leave to the implementator, but it has happen to me some times that I have placed time in anonymizing a backtrace, write a good comment and so on only to find the bug already been reported (and the time laid on the backtrace was wasted) and somebody has already made a comment like mine (and the time placed on the comment was wasted, and my comment was more or less noise in the bug), and there have even been some bugs where there has been a package posted to testing with a solution or even stable which has not yet hit my mirror (nearly everything was time wasted except the link to the bug I got after reporting). 

This would also maybe lessen some noise in bugs like #541045 where most comments are duplicates or versions of already existing comments which makes it very hard to parse (which also gave alot of mails.

As I see it a bug that has already been reported the only interesting info abrt can provide is if the version installed is not already reported to be "broken", and in that case instead advise people to go read the bug and write a comment if they think some information is missing.

Comment 1 Mads Kiilerich 2010-07-28 13:17:08 UTC
I think this is a duplicate of bug 575396 "RFE: check for duplicates before prompting for user input"

Comment 2 Bug Zapper 2011-06-02 14:04:56 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 3 Bug Zapper 2011-06-27 16:20:24 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.