Bug 221168

Summary: dbus: Can't send to audit system
Product: [Fedora] Fedora Reporter: Need Real Name <bugzilla>
Component: dbusAssignee: David Zeuthen <davidz>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: dwalsh, mclasen, reg.bugs, sgrubb
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 1.0.2-3.fc7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-04-12 19:15:07 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:    
Bug Blocks: 237289    
Attachments:
Description Flags
Start SELinux thread after setuid call. none

Description Need Real Name 2007-01-02 18:15:03 UTC 
Description of problem:
Whenever I update my 'local' policy using 'semodule -i local.pp', I get the
following error in my syslog:

dbus: Can't send to audit system: USER_AVC avc:  received policyload notice
(seqno=5) : exe="/bin/dbus-daemon" (sauid=505, hostname=?, addr=?, terminal=?)
Comment 1 Need Real Name 2007-03-18 13:26:36 UTC 
Is this going to be fixed?????
Comment 2 Need Real Name 2007-03-28 00:33:57 UTC 
Still haven't heard anything on this whether or not it is meaningful and whether
or not it will be fixed...
Comment 3 Daniel Walsh 2007-03-28 20:19:40 UTC 
This seems to be an audit problem.  Audit messages are not being allowed to be
sent if your uid is not 0.
Comment 4 Daniel Walsh 2007-04-02 17:57:28 UTC 
Created attachment 151452 [details]
Start SELinux thread after setuid call.
Comment 5 Daniel Walsh 2007-04-02 18:00:37 UTC 
Capabilities do not seem to be set cross threads. So if you setuid and retain
certain capabilities after thread creation.  The other threads will not get the
capability.  Moving the creation of the thread after the setuid/capset calls.
gives all threads the capability and the dbus code works.

This patch should be applied to RHEL5/FC6/and devel
Comment 6 Need Real Name 2007-04-11 17:11:52 UTC 
Has the patch been applied yet?
Comment 7 David Zeuthen 2007-04-12 19:15:07 UTC 
Applied.
Comment 8 Need Real Name 2007-04-13 07:53:03 UTC 
I have a fully updated FC6 system and still get the same errors when doing a
'setenforce' operation.

Is a reboot or other service restart required to fix this problem?
Comment 9 Daniel Walsh 2007-04-13 13:44:43 UTC 
You need to restart dbus for this to take effect.  The best way to do this is to
reboot, since restarting the messagebus will cause certain desktop apps to blow up.
Comment 10 Need Real Name 2007-04-15 03:44:18 UTC 
I still am getting the errors. Is this only patched in rawhide or will it be
backported to FC6?
Comment 11 Steve Grubb 2007-04-15 12:46:35 UTC 
I am pretty sure its built only for rawhide at this point. But if the problem is
also in FC6, it should be built there too. The patch is not terribly invasive.
Comment 12 Need Real Name 2007-04-18 22:40:48 UTC 
Would be great to see it fixed in FC6 since I noticed and reported this bug back
in January on my FC6 system (I am the original bug poster to this thread so I am
assuming we are talking about the same thing :)

Thanks