Bug 650639

Summary:	[RFE] Ability to enable plugins via abrt gui
Product:	Red Hat Enterprise Linux 6	Reporter:	James G. Brown III <james.brown>
Component:	abrt	Assignee:	abrt <abrt-devel-list>
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-tools-bugs
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.3	CC:	ahecox, dvlasenk, gavin, james.brown, kklic, mnowak, npajkovs, ovasik, pbatkowski, rvokal, syeghiay
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-15 08:55:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	650975, 697494
Bug Blocks:	645519

Description James G. Brown III 2010-11-07 14:53:07 UTC

Description of problem:

abrt should provide a facility in the gui to enable plugins. You can configure them, but not enable them to run on a crash.

Actual results:

To enable the Bugzilla plugin you have to manually edit the abrt.conf

Expected results:

You can enable Bugzilla plugin (or any plugin) through the abrt gui

Comment 2 James G. Brown III 2010-11-07 15:21:36 UTC

I would consider this a bug presuming that configuring the Bugzilla plugin also sets the expectation that it also be enabled. 

- James

Comment 3 Jiri Moskovcak 2011-01-04 14:34:52 UTC

This would require a lot of code changes, so it's not a good candidate for 6.1

Comment 6 Denys Vlasenko 2011-08-24 08:20:06 UTC

(In reply to comment #0)
> abrt should provide a facility in the gui to enable plugins. You can configure
> them, but not enable them to run on a crash.
> 
> Actual results:
> 
> To enable the Bugzilla plugin you have to manually edit the abrt.conf
> 
> Expected results:
> 
> You can enable Bugzilla plugin (or any plugin) through the abrt gui

The configuration mechanism in ABRT 2.x is generic, meaning that there are very many ways to, say, configure reporting to Bugzilla: it can be configured to run at crash time or only when user requests it; it can be configured to run as part of a composite reporting event; it can be run with different options.

(See https://fedorahosted.org/abrt/wiki/AbrtDeployment2 section "Configuring ABRT" for a more detailed description)

The gist of it is that adding/removing Bugzilla reporting is far from being as simple as toggling a "yes/no" checkbox in gui.

I don't see how we can implement that.

Does anyone have a proposal how this can be implemented? Otherwise I propose to close it as WONTFIX.

Comment 7 Nikola Pajkovsky 2011-08-24 12:30:52 UTC

Yes, that could be another huge program and I tend to close it as WONTFIX

Comment 8 James G. Brown III 2011-08-24 12:41:57 UTC

If the intent is to have abrt make it easy for people to report bugs having them go into modify a configuration file is counter-intuitive for the typical desktop user.

Comment 9 Jiri Moskovcak 2011-09-08 12:38:06 UTC

This actually means to write something like system-config-abrt tool which will take a lot of coding and definitely won't happen in 6.2 -> resetting the flags.

Comment 15 RHEL Program Management 2012-05-03 04:40:28 UTC

Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 17 RHEL Program Management 2012-08-15 08:55:11 UTC

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.