On Thu, 2014-07-10 at 10:34 -0400, Stephen Smalley wrote: \ > > Hmmm...but rebooting "cleared" it and now I can su without delay and no > systemd error message. > Yes , sound like the issue i hit yesterday (when i updated my e145 policy) basically i loaded the updated policy, rebooted (system was hanging), hard reset, looking at avc denials, system_t self:dbus send_msg was denied. (even though i had that rule both before and after i updated my policy. was not able to reproduce it after that, but looks like we will be seeing more from this issue soon. > Merged #next to #integration locally to try to pick up the improved > error reporting on unknown class/perms but can't reproduce it now... > > > _______________________________________________ Selinux mailing list Selinux@xxxxxxxxxxxxx To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx. To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
