Bug 437902 - setroubleshooter fires off notifications when Services Module
Summary: setroubleshooter fires off notifications when Services Module
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: rawhide
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-18 00:51 UTC by Robert Gray
Modified: 2008-04-15 13:48 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-04-15 13:48:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
setroubleshoot browser log (40.16 KB, text/plain)
2008-03-18 00:53 UTC, Robert Gray
no flags Details

Description Robert Gray 2008-03-18 00:51:14 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Robert Gray 2008-03-18 00:53:32 UTC
Created attachment 298321 [details]
setroubleshoot browser log

Comment 2 Robert Gray 2008-03-18 01:01:13 UTC
Sorry about the earlier glitches...

When I tried to view my firewall configuration (looking into the #431845
iptables-error msg during logon) by going to:

System>Administration>Services 

And noticed that the setroubleshooter browser kept firing off notifications
(some with sub-second frequency).  Most of the notifications appear to look for
GAM_Server related files.

The log's attached for your review.

###Steps to reproduce
1. System>Administration>Services
2. Log in as root
3. See the "Fireworks" (note large bright star icon) go off.

Regards,

Comment 3 Daniel Walsh 2008-03-18 12:40:34 UTC
Most of these are 
Fixed in selinux-policy-3.3.20.fc9

Comment 4 Robert Gray 2008-04-14 22:09:56 UTC
(In reply to comment #3)
> Most of these are 
> Fixed in selinux-policy-3.3.20.fc9

Yep,

Looks like its been taken care of - no selinux activation warnings - Thanks.


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