Bug 1271323 - setroubleshoot is not showing alerts
Summary: setroubleshoot is not showing alerts
Keywords:
Status: CLOSED DUPLICATE of bug 1271061
Alias: None
Product: Fedora
Classification: Fedora
Component: setroubleshoot
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Lautrbach
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-13 16:00 UTC by Julio Ordonez Viales
Modified: 2015-11-23 19:11 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-10-20 13:26:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot (23.35 KB, image/png)
2015-10-13 16:00 UTC, Julio Ordonez Viales
no flags Details

Description Julio Ordonez Viales 2015-10-13 16:00:11 UTC
Created attachment 1082500 [details]
screenshot

Description of problem:

when an selinux alert is received setroubleshoot does not show the process that caused the issue

Version-Release number of selected component (if applicable):


How reproducible:

always

Steps to Reproduce:
1.selinux alert received 
2. open selinux troubleshoot
3. no information is displayed

Actual results:

The source process: label
Attempted this access: label
On this file: label


Expected results:

to show relevant information on the process and the attempted access

Additional info:

Comment 1 Miroslav Grepl 2015-10-19 05:19:32 UTC
Could you try to reproduce it and run

# ausearch -m avc -ts recent -su setroubleshootd_t

Comment 2 Miroslav Grepl 2015-10-19 05:20:23 UTC
I see with enforcing mode

allow setroubleshootd_t tmp_t:dir write;
allow setroubleshootd_t tmpfs_t:dir write;

Comment 3 Vít Ondruch 2015-10-20 06:50:13 UTC
This looks to be duplicate of bug 1271061

Comment 4 Petr Lautrbach 2015-10-20 13:26:51 UTC
You are right.

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

Comment 5 Julio Ordonez Viales 2015-11-23 19:11:07 UTC
(In reply to Miroslav Grepl from comment #1)
> Could you try to reproduce it and run
> 
> # ausearch -m avc -ts recent -su setroubleshootd_t

Fixed, duplicated


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