Bug 1018285

Summary:	ABRT presents confusing "reported" state
Product:	[Fedora] Fedora	Reporter:	Matthew Garrett <mjg59>
Component:	gnome-abrt	Assignee:	Jakub Filak <jfilak>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	abrt-devel-list, dvlasenk, iprikryl, jberan, jfilak, jmoskovc, mmilata, mtoman
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gnome-abrt-0.3.3-2.fc20	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-10 06:39:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matthew Garrett 2013-10-11 15:45:30 UTC

I have a bug entry in ABRT that says the following:

"Reported: yes

This problem hasn't been reported to Bugzilla yet. Our developers may need more information to fix the problem.
Please consider reporting it - you may help them. Thank you"

If "Reported: Yes" means "Reported to ABRT server" then the following language should be changed to something like:

"This problem has been reported, but a Bugzilla ticket has not been opened. Our developers may need more information to fix the problem. Please consider also reporting it to Bugzilla in order to provide that. Thank you"

Comment 1 Matthew Garrett 2013-10-11 15:46:39 UTC

In addition, the "Report" button in the top right should be "Report to Bugzilla" if "Reported: Yes".

Comment 2 Jakub Filak 2013-10-11 16:59:47 UTC

I've created a pull request which is supposed to get rid of the confusing "reported" state.

https://github.com/abrt/gnome-abrt/pull/38

Comment 3 Jakub Filak 2013-10-17 11:30:51 UTC

Upstream commit 5a2baf0baeebbb4d8bcb7a3ecab83b1eca3f2093 fixes this bug.

Comment 4 Fedora Update System 2013-10-29 04:51:52 UTC

gnome-abrt-0.3.3-1.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/gnome-abrt-0.3.3-1.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20

Comment 5 Fedora Update System 2013-10-29 18:07:59 UTC

Package gnome-abrt-0.3.3-1.fc20, abrt-2.1.9-1.fc20, libreport-2.1.9-1.fc20, satyr-0.11-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-abrt-0.3.3-1.fc20 abrt-2.1.9-1.fc20 libreport-2.1.9-1.fc20 satyr-0.11-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-20254/gnome-abrt-0.3.3-1.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2013-11-05 20:00:28 UTC

Package gnome-abrt-0.3.3-2.fc20, abrt-2.1.9-1.fc20, libreport-2.1.9-1.fc20, satyr-0.11-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-abrt-0.3.3-2.fc20 abrt-2.1.9-1.fc20 libreport-2.1.9-1.fc20 satyr-0.11-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-20254/gnome-abrt-0.3.3-2.fc20,abrt-2.1.9-1.fc20,libreport-2.1.9-1.fc20,satyr-0.11-1.fc20
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2013-11-10 06:39:27 UTC

gnome-abrt-0.3.3-2.fc20, abrt-2.1.9-1.fc20, libreport-2.1.9-1.fc20, satyr-0.11-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.