On Sun, Oct 2, 2011 at 9:01 PM, jackson byers <byersjab@xxxxxxxxx> wrote: > mike cloaked responded: > >>The last update to chrome in f14 gave avc denials and in order to get >>chrome to run after that it was necessary to run the following >>commands (as root) before chrome would run again: > >>semanage fcontext -a -t textrel_shlib_t '/opt/google/chrome/chrome' >>restorecon -v '/opt/google/chrome/chrome' > > > mike, what worked for me, as I have already posted, > was the 2 commands (from Lancebaynes87): > >>give this out with root: >>semanage fcontext -a -s system_u -t usr_t /opt/google/chrome/chrome-sandbox >>restorecon -v /opt/google/chrome/chrome-sandbox > > that semanage command is different from yours(mike cloaked). > > Furthermore, that is all I needed to be able to run chrome again, > unlike your experience needing another pair of commands > >>grep chrome-sandbox /var/log/audit/audit.log | audit2allow -M mypol >>semodule -i mypol.pp > > My SELinux chops are pretty weak, almost nonexistent. > But I would be interested in your comments re the differences. > OK - I was not aware of the solution you found at the time I applied my fix which came from the avc suggestions.... but yours is the better solution.... -- mike c -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines