dbus-daemon/Evo eat CPU

Bojan Smojver bojan at rexursive.com
Tue Jan 24 10:18:54 UTC 2006

Just noticed that with today's updates, dbus-daemon and Evo eat CPU like
it's going out of fashion. Probably due to something in SELinux policy:

type=USER_AVC msg=audit(1138097250.998:651308): user pid=7040 uid=81
auid=4294967295 msg='avc:  denied  { send_msg } for msgtype=method_call
interface=org.freedesktop.DBus member=Hello dest=org.freedesktop.DBus
spid=8809 scontext=user_u:system_r:unconfined_t
tcontext=user_u:system_r:initrc_t tclass=dbus : exe="?" (sauid=81, host
name=?, addr=?, terminal=?)'

This all happens when Evo starts. If I do "setenforce 0", the CPU of
Xorg goes to 99.9% for a while and then everything returns back to
normal. Doing "setenforce 1" after that doesn't change things - it must
be something in Evo startup that triggers this.

Anyone else noticed this? A brief look in Bugzilla didn't reveal anthing


More information about the fedora-devel-list mailing list