Bug 870313

Summary:	RFE: have abrt replace sealert
Product:	[Fedora] Fedora	Reporter:	Miroslav Grepl <mgrepl>
Component:	setroubleshoot	Assignee:	Lukas Vrabec <lvrabec>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	abrt-devel-list, crobinso, dvlasenk, dwalsh, dwmw2, iprikryl, jberan, lvrabec, mgrepl, mmilata, plautrba, rvokal, voxadam
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	870224	Environment:
Last Closed:	2017-12-06 12:15:41 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:
Bug Depends On:	870224
Bug Blocks:

Description Miroslav Grepl 2012-10-26 07:01:19 UTC

+++ This bug was initially created as a clone of Bug #870224 +++

sealert gets the job done, but it's crufty and fugly. all it really does is slap some UI over the setroubleshoot output AFAICT, so probably straightforward for an abrt addon to just supply the sealert dbus interface and go from there.

--- Additional comment from jmoskovc on 2012-10-26 02:45:26 EDT ---

We're planning to do it for F19

Comment 1 Daniel Walsh 2012-10-26 18:16:04 UTC

My concern with this is we begin to treat every AVC as if it is a bug, when a lot of them are just user problems.  The goal of setroubleshoot was to instruct the admin how to fix his system as opposed to reporting a bugzilla. 

The goal of the UI was to get the user to read the description and run restorecon or turn on a boolean, not report a bug, so we have to tell them to run restorecon or set a boolean.

Comment 2 Jiri Moskovcak 2012-10-29 07:57:08 UTC

ABRT can still show the window with with the recommendations how to fix the problem before reporting it. By integration we only mean using the same notification icon and have abrt-gui to show the AVC instead of the current avc browser.

Comment 3 Daniel Walsh 2012-10-30 20:01:51 UTC

We do not want it to be reported if it is a configuration problem.  That is the point.

Comment 4 Jiri Moskovcak 2012-10-31 07:18:57 UTC

Ok, to make it clear - we only want the AVCs to show in ABRT, so all "problems" can be found at one place, the rest of the process should stay the same - so if anyone clicks on AVC in ABRT the current setroubleshoot window will appear guiding user thru the fixing or reporting as it is now. Only the entry point (notification, gui and cli(if possible)) will be the same. It will still take user thru the path where he can find the suggested fixes or decide to report it - as it is now.

Comment 5 Daniel Walsh 2012-10-31 10:58:07 UTC

I have no problem with that.

Comment 6 Petr Lautrbach 2017-11-23 08:43:44 UTC

Is this still valid?

Comment 7 Lukas Vrabec 2017-12-06 12:07:15 UTC

No.