On Tue, 2006-01-24 at 21:18 +1100, Bojan Smojver wrote:
> 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.
Evo tries to connect to NetworkManager using DBus on startup (and
whenever it opens a new shell window); perhaps it's happening when it's
doing this?
>
> Anyone else noticed this? A brief look in Bugzilla didn't reveal anthing
> obvious...
I haven't seen this, FWIW
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
